SKILLEMALL.ai
GitHub ↗ RU Sign in

AC release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

skytiger6724/qwen-skills Agent Skills author: skytiger6724 1 file body ≈ 562 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Generate user-facing release notes from tickets, PRDs, or changelogs.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Qwen Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: release-notes (Lord1Egypt/RA-Skills)

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 53/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 65Failures and branches. 3 branches
    • 100Steps. 21 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 562 tokens
    • 100Running it twice. No mutating operations

    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 272: enough signal without eating the budget
    • +4Structure: 3 headings
    • +3Step-by-step instructions: 21 items
    • +4Has examples (1 code blocks)

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