SKILLEMALL.ai
GitHub ↗ RU Sign in

AB release-notes-writer

Convert a raw PR list, git log, or hand-written changelog into polished, audience-tuned release notes. Pick a voice preset (internal-engineering, customer-facing, marketing-blog, mobile-app-store), drop the input, and the skill clusters changes into Features / Improvements / Fixes / Breaking / Security, strips merge noise, and rewrites each line in the chosen voice. Trigger when the user says "write release notes", "draft a changelog summary", "turn this PR list into release notes", "generate release notes for", or asks to summarize a changelog for a release.

genspark Agent Skills author: Genspark 1 file body ≈ 1 783 tokens Open the sourcegenspark.ai↗ analyzed 3 d ago

As a process B 74/100 · Nearly there — weak spots: running it twice

GeneratorWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Genspark 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
74/100
Nearly there
Running it twice w 4
30
Failures and branches w 10
50
Tools and files w 18
60
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 74/100

    • 30Running it twice. 16 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (write) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 38 steps, 1 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1783 tokens
    • 100Progress reporting. Reports progress

    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 565: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 38 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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