SKILLEMALL.ai
GitHub ↗ RU Sign in

CD release

Cut an OpenWork release, release the app, publish a new version, rerun or recover a release tag, verify release assets. Tag-driven GitHub Actions release that makes zero commits to the repo.

different-ai/openwork Agent Skills author: different-ai NOASSERTION 1 file body ≈ 2 239 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Cut an OpenWork release, release the app, publish a new version, rerun or recover a release tag, verify release assets.

As a process D 48/100 · Unfinished process — References files that are not bundled: scripts/release/stamp-version.mjs, scripts/release/verify-tag.mjs

AnalyzerGitHubSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
D
48/100
Unfinished process
References files that are not bundled: scripts/release/stamp-version.mjs, scripts/release/verify-tag.mjs
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/release/stamp-version.mjs
  • warning missing-ref reference to a missing file: scripts/release/verify-tag.mjs

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: scripts/release/stamp-version.mjs, scripts/release/verify-tag.mjs
  • 0Tools and files. 2 referenced file(s) missing: scripts/release/stamp-version.mjs, scripts/release/verify-tag.mjs
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 36 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 100Steps. 10 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2239 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 190: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (10 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.