SKILLEMALL.ai
GitHub ↗ RU Sign in

CD release

Propose and push the next SemVer release tag, then watch the release workflow.

The skillemall take

Proposes the next SemVer tag and triggers the release workflow. One file in the folder, no scripts. Quality score sits at 55, process score at 35. No critical issues, but broken references signal missing files.

For an agent handling versioning and CI/CD, this is bare minimum. Platform support is wide—Claude through DeepSeek. Low process score hints at incomplete automation or documentation gaps. Worth installing if your release pipeline already exists; risky as a foundation from scratch.

NexaAI/nexa-sdk Claude Code author: NexaAI 1 file body ≈ 328 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Propose and push the next SemVer release tag, then watch the release workflow.

As a process D 35/100 · Unfinished process — References files that are not bundled: ../../../notes/release.md

ProcedureSoftware developmenttype 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
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
D
35/100
Unfinished process
References files that are not bundled: ../../../notes/release.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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: ../../../notes/release.md

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: ../../../notes/release.md
  • 0Tools and files. 1 referenced file(s) missing: ../../../notes/release.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 328 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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)
  • +3Description length 78: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Step-by-step instructions: 5 items

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