CtrlK
BlogDocsLog inGet started
Tessl Logo

create-changelog-announcement

Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A thorough, highly actionable changelog workflow with clear sequencing and a build verification loop. Its main weakness is conciseness and progressive disclosure: significant internal repetition and a large monolithic body that would benefit from offloading templates/examples into reference files.

Suggestions

Consolidate the <Summary>/truncate structure rule into a single canonical explanation instead of restating it in Core Responsibilities, Step 4, Output Format, and the checklist.

Move the large MDX frontmatter/template blocks, sidebar JSON schema, and roadmap TypeScript snippet into files under references/ and link to them, reducing the monolithic SKILL.md body.

Trim motivational filler such as 'You're creating user-facing documentation that represents a new feature to thousands of developers' to respect the token budget.

DimensionReasoningScore

Conciseness

The core guidance is efficient, but the <Summary>/truncate structure and the 'no em dashes' rule are restated across Core Responsibilities, Step 4, Output Format, the checklist, and the build section, adding redundant tokens.

2 / 3

Actionability

Provides concrete, copy-paste-ready artifacts: exact MDX frontmatter, <Summary>/truncate markup, sidebar JSON schema, roadmap TypeScript snippet, gh CLI command, and build command.

3 / 3

Workflow Clarity

A clearly sequenced 9-step workflow with an explicit build/verify checkpoint and a 'fix errors immediately' feedback loop including error-recovery guidance.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent); the one external reference (.claude/skills/write-social-announcement/SKILL.md) is one level deep and clearly signaled, but the SKILL.md itself is a ~490-line monolith with large inline templates and examples that could be split into reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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, complete, and trigger-rich, clearly defining both the workflow and the conditions for use. The 'Use when...' phrasing follows the rubric's own good-example convention rather than second-person capability description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards.'

3 / 3

Completeness

Explicitly states both what the skill does (create/publish changelog announcements via a defined workflow) and when to use it, with an explicit 'Use when the user mentions...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasings: 'adding changelog entries, documenting new features, creating release notes, or announcing product updates.'

3 / 3

Distinctiveness Conflict Risk

A clearly bounded niche (changelog announcements) with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 5 suspicious

Warning

Total

14

/

16

Passed

Repository
Agenta-AI/agenta
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.