CtrlK
BlogDocsLog inGet started
Tessl Logo

changelog-scan

Scan recent merges/PRs/commits for release note content. Structured output for drafter.

48

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./starters/changelog-drafter/.claude/skills/changelog-scan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is admirably brief but underspecified: it never shows what a 'per-item block' or 'Scan Summary' looks like, so Claude lacks the concrete output template needed to execute reliably.

Suggestions

Add a concrete output template or example showing the exact shape of a 'per-item block' and the 'Scan Summary'.

Replace or explain the 'Same contract as the Grok version' reference, which depends on context not present in the bundle.

Split the prose into labeled sections ('## Output format', '## Rules') so the structure is scannable.

DimensionReasoningScore

Conciseness

The body is extremely lean with no concept over-explanation, but the opaque reference to 'the Grok version' is a token that does not earn its place for a reader lacking that external context.

4 / 5

Actionability

It gives high-level hints ('Produce the per-item blocks + Scan Summary', 'cite PR numbers') but never defines the block/summary format with a concrete template or example, leaving Claude without the specifics to execute.

2 / 5

Workflow Clarity

Only a vague output description is present with no real sequence, and the undefined 'per-item blocks' make the single action ambiguous rather than unambiguous.

2 / 5

Progressive Disclosure

No bundle files exist and the skill is short, so no external references are needed, but the body lacks organized sections (e.g. separate '## Output format' and '## Rules') that would qualify it higher.

3 / 5

Total

11

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a clear, distinct niche with decent trigger terms, but it lacks an explicit 'Use when' trigger clause and only loosely describes the structured output, capping completeness and specificity at the midpoint.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when drafting release notes or a changelog from recent git activity.'

Specify what the structured output contains (e.g. per-item blocks with PR number, type, and summary) rather than just 'Structured output for drafter'.

Include the synonym 'changelog' alongside 'release note' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("merges/PRs/commits") and two concrete actions ("Scan ... for release note content", "Structured output for drafter"), but coverage is not comprehensive — no detail on what the structured output contains.

3 / 5

Completeness

Has a clear 'what' (scan git activity for release-note content, produce structured output) but no explicit 'Use when...' trigger clause, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Covers several natural terms a user would say ("merges", "PRs", "commits", "release note content"), though common synonyms like "changelog" are missing.

4 / 5

Distinctiveness Conflict Risk

The release-note/changelog niche is fairly distinct from general git skills, with minor overlap risk against broad commit-summarization skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
cobusgreyling/loop-engineering
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.