release-changelog

Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/release-changelog/SKILL.md

Quality

Content

88%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 a highly actionable, well-sequenced workflow with concrete commands, templates, and validation loops, and it appropriately points to an external cases.md reference. It is somewhat long and could offload more of the inline HTTP request detail to the referenced file.

Suggestions

Move the full POST/PUT case request bodies into skills/paperclip/references/cases.md, keeping only the key fields and the upsert/PUT summary inline.

Consolidate the repeated calver version-derivation rules into a single canonical statement to trim duplication.

Dimension	Reasoning	Score
Conciseness	Dense and command-driven with no padding of concepts Claude already knows, though the version-derivation rules are restated across a few sections and the body is long overall.	4 / 5
Actionability	Provides fully executable git/gh/npm commands, concrete HTTP request bodies, and an exact changelog template that cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	Steps are clearly sequenced (Step 0–6) with explicit validation checkpoints (idempotency check, review checklist) and feedback loops (409 stale_base_revision refetch-merge-retry).	5 / 5
Progressive Disclosure	Well-organized into headed sections with a clearly signaled one-level reference (skills/paperclip/references/cases.md), though substantial API request bodies remain inlined rather than split out.	4 / 5
	Total	18 / 20 Passed

Description

58%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 specific and actionable, naming concrete inputs and an output artifact, but lacks an explicit "Use when..." trigger clause and natural synonym coverage. It is distinct and unlikely to misfire for the wrong skill.

Suggestions

Add an explicit 'Use when ...' clause stating when to invoke this skill (e.g. 'Use when preparing the stable Paperclip release changelog or when the user asks for release notes').

Include natural synonyms users would say, such as 'release notes', alongside 'release changelog'.

Dimension	Reasoning	Score
Specificity	Names the domain (stable Paperclip release changelog) plus several concrete actions — "reading commits, changesets, and merged PR context" — and a specific output path, with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does, but there is no explicit "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant terms like "release changelog", "commits", "changesets", and "merged PR" but omits common natural synonyms (e.g. "release notes") and has no file-extension coverage.	3 / 5
Distinctiveness Conflict Risk	Targets a narrow niche (the stable Paperclip release changelog) with distinct triggers, leaving only minor overlap risk with adjacent release-notes skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: paperclipai/paperclip
Path: .agents/skills/release-changelog/SKILL.md
Commit: 6d358e6

Reviewed: ~16 hours ago

Table of Contents

Discovery Implementation Validation

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.