CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-notes

Draft evidence-backed release notes and changelog entries. Use this skill when PR notes, GitHub releases, or npm handoff need traceability.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./Skills/content-publishing/release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 compact and well-sectioned with a coherent six-step workflow and explicit stop conditions, but it is dragged down by a verbatim duplicate section, the absence of any output template or example for its schema-bound artifacts, and a progressive-disclosure reference that points to an archive path rather than the bundle's actual reference files. Addressing the duplication and adding a handoff/evidence example would lift the two weakest dimensions.

Suggestions

Merge the 'Anti-Patterns' section into 'Avoid' (or vice versa) to remove the verbatim three-bullet duplication and reclaim tokens.

Add a minimal concrete example of 'release-notes-handoff.v1' (fields: package, version, channel, sections, evidence, blockers) and of an evidence-list entry so outputs are copy-paste ready rather than implied.

Fix progressive disclosure: point the archived-context line at the actual bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) or move that detail into a real references/ file that the body links by its true path.

DimensionReasoningScore

Conciseness

Bullets are terse and no space is spent explaining concepts Claude already knows, but the 'Anti-Patterns' section repeats the 'Avoid' section verbatim ('Do not publish packages, mutate tags, or manage OTP' appears twice) — a fully redundant section to tighten, fitting anchor 3 over 4's 'minor instances'.

3 / 5

Actionability

Guidance names concrete fields ('package, version, channel, sections, evidence, and blockers') but provides no template or example of the 'release-notes-handoff.v1' artifact, the evidence list, or a changelog entry format — missing key details, matching anchor 3's 'some concrete guidance but incomplete'. It is above anchor 2 because steps and named fields are specific, not just high-level hints.

3 / 5

Workflow Clarity

A six-step sequence with runtime checkpoints ('Stop before publish when blockers or channel mismatches exist', 'Fail fast at the first evidence or version mismatch') fits anchor 4. Not 5: the Validation section's validate→fix→rerun loop is scoped to editing the skill itself rather than the release-notes task, leaving task-level validation implicit.

4 / 5

Progressive Disclosure

The body's only deep reference is 'Infrastructure/references/deferred-skill-context/content-publishing-release-notes/', a path absent from the bundle, while actual bundle files (references/contract.yaml, evals.yaml, task-profile.json) are never referenced or navigated — 'references present but not clearly signaled' fits anchor 3. Not 4: the mismatch between the referenced path and the real bundle structure is more than a minor organization gap; not 2 because the body itself is compact and clearly sectioned.

3 / 5

Total

13

/

20

Passed

Description

78%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 a strong two-sentence example: a concrete what paired with an explicit when clause carrying niche-specific triggers. Its main gaps are narrow capability coverage (only drafting release notes and changelog entries as stated actions) and a few missing natural synonyms such as 'what changed' or 'version bump'.

Suggestions

Widen the stated capabilities from two actions to several, e.g. 'Draft evidence-backed release notes, changelog entries, and npm release handoffs; summarize what changed between tags or PRs'.

Add natural trigger variations such as 'what changed', 'version bump', or 'CHANGELOG' to broaden keyword coverage toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain plus two concrete actions ('Draft evidence-backed release notes and changelog entries') — matches the 'domain and 1-2 concrete actions' anchor. It is not 4 because PR-notes drafting, GitHub-release drafting, and npm handoff appear only as triggers, not as listed capabilities.

3 / 5

Completeness

Explicitly answers both questions: 'Draft evidence-backed release notes and changelog entries' states the what, and 'Use this skill when PR notes, GitHub releases, or npm handoff need traceability' states the when with concrete trigger phrases — matching the anchor-5 example structure. Anchor 4's caveat of a less-explicit 'when' does not apply.

5 / 5

Trigger Term Quality

'PR notes', 'GitHub releases', 'npm handoff', and 'changelog' are natural terms a user would say, giving good keyword coverage (anchor 4). It falls short of 5 because common variations like 'what changed', 'version bump', or 'CHANGELOG file' are missing.

4 / 5

Distinctiveness Conflict Risk

The release-notes/changelog/npm-handoff niche is mostly distinct with specific triggers, but 'npm handoff' and changelog drafting sit adjacent to publish-oriented and commit-message skills, leaving minor overlap risk (anchor 4). It is more distinct than the anchor-3 'could still overlap with similar skills'.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/content-publishing/release-notes/SKILL.md

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.