release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/catalog/optional/content/release-announcement/SKILL.md

Quality

Content

61%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.

A well-structured, mostly lean announcement skill with strong channel templates and writing rules. Its main weaknesses are inlined heavyweight Paperclip case payloads that belong in a reference file and the absence of explicit validation/verification checkpoints in the workflow.

Suggestions

Move the three Paperclip case JSON blocks into a bundled reference file (e.g. references/paperclip-cases.md) and keep only a one-line pointer plus the API contract reference in the body, improving progressive disclosure and conciseness.

Add an explicit validation/verification step in the workflow (e.g. verify all links resolve, breaking changes appear in the upgrade guide, and internal team is notified before publish) framed as a gate before the public post goes live.

Provide at least one fully copy-paste-ready example (e.g. a completed changelog entry) to lift actionability from mostly-executable to fully executable.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes competence ("Lead with the user, not the team", "Numbers beat adjectives"), but the three large Paperclip case JSON blocks are heavyweight inline content that pads the file for readers who are not running inside Paperclip.	4 / 5
Actionability	Concrete channel templates (changelog, dev blog, in-app note, social) and a ready-to-fill markdown changelog scaffold give mostly executable guidance, but the copywriting guidance is structural rather than copy-paste ready and the Paperclip API calls are templated with placeholder tokens rather than runnable.	4 / 5
Workflow Clarity	The sequence (audience/channel first, then universal structure, then templates, then post-publish checklist) is clear, but publishing and announcement work has no validation/verification checkpoint beyond a final checklist, and the guidelines cap workflow clarity at 3 for batch/destructive-style operations lacking explicit validate->fix->retry feedback loops.	3 / 5
Progressive Disclosure	The skill is essentially a monolith: the large Paperclip case JSON blocks clearly belong in a separate reference file, and the body references `skills/paperclip/references/cases.md` (an external, non-bundled path) with no bundle files present, so content that should be split out is inlined.	2 / 5
	Total	13 / 20 Passed

Description

83%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.

A high-quality description that names concrete deliverables and compositional requirements clearly. Adding an explicit "Use when..." trigger clause and a few synonyms (e.g., release notes) would push it to a perfect score.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when shipping a version, feature, or fix that needs a writeup') to satisfy the when half of completeness.

Include the synonym 'release notes' alongside 'changelog' so users who say that phrase still surface the skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete output artifacts ("changelog, blog post, in-app note, or social post") plus specific compositional actions ("leads with user impact, names the audience, and includes upgrade/migration steps"), giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	The "what" is explicit and detailed, and the audience-plus-impact-plus-steps framing implies when to use it, but there is no explicit "Use when..." trigger clause anchoring the when, which the guidelines say should cap completeness; it is above the vague-when anchor (3) but not a full explicit when (5).	4 / 5
Trigger Term Quality	Strong natural terms ("release announcement", "changelog", "blog post", "social post", "upgrade/migration steps") that users would say, but it omits common synonyms like "release notes" and file/extension triggers that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (channel-specific release writeups with audience-targeting and migration steps) that is unlikely to fire for unrelated skills, with distinct triggers and minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: paperclipai/paperclip
Path: packages/skills-catalog/catalog/optional/content/release-announcement/SKILL.md
Commit: 890ab9a

Reviewed: about 17 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.