SKILLEMALL.ai
GitHub ↗ RU Sign in

AB changelog

Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".

entireio/cli Agent Skills author: entireio MIT 1 file body ≈ 747 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks…

As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice

GeneratorGitHubWriting and documentstype 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
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 20 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 747 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 223: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 20 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)

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