CC changelog
Generate a user-facing changelog from recent commits/PRs across watched repos - write it in-repo (Keep a Changelog format) or open a cross-repo changelog PR on a docs/marketing repo.
Promises to generate changelogs from commits and PRs across multiple repos in Keep a Changelog format, writing to repo or opening cross-repo PRs. In reality, finds only one file despite claiming multi-source support—commit collection logic is either incomplete or missing. Code scores 56/100 for quality and 53/100 for process structure, both below passing.
No critical security issues found, but broken_references_missing_files flag means it references non-existent files. Not tested on actual models. Install only if you'll finish the multi-repo collection logic and fix broken links yourself—treat it as a skeleton, not a working tool.
Generate a user-facing changelog from recent commits/PRs across watched repos - write it in-repo (Keep a Changelog format) or open a cross-repo changelog PR…
As a process C 53/100 · Has gaps — References files that are not bundled: url
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5898 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - note
edit-residuethe text marks something as outdated (lines 106): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: url
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5898 tokens
- 100Steps. 55 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
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 182: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.