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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Highly actionable and well-sequenced content with strong validation and feedback loops for a complex multi-artifact workflow. Its main weaknesses are notable redundancy across sections and a monolithic single-file structure that underuses progressive disclosure despite the skill's length.

Suggestions

Consolidate the repeated Summary/truncate-marker and frontmatter-format guidance into a single authoritative section and reference it elsewhere to remove redundancy.

Move the bulky reusable templates (full Example 1 MDX entry, media iframe/Image snippets, sidebar JSON shape, roadmap TypeScript block) into files under references/ and link to them from the body to improve progressive disclosure.

Trim the closing 'Tips for Success' and 'Remember' sections, which restate guidance already covered in the workflow and writing-style sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and concrete, but the Summary/truncate-marker and frontmatter-format explanations repeat across Core Responsibilities #1, Step 3, Step 4, and the QA checklist, and the file is ~488 lines with redundant guidance that could be tightened.	3 / 5
Actionability	Fully executable guidance: exact file paths, complete MDX frontmatter and body templates, JSON sidebar examples, TypeScript roadmap shape, and runnable commands (grep -r, npm run build, gh issue close) cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	A clear 9-step sequence with an explicit validation checkpoint ('Always run the build to verify no errors'), error-recovery feedback loop ('If build fails, fix errors immediately'), and QA checklists for the multi-artifact batch operation.	5 / 5
Progressive Disclosure	No bundle files exist; everything lives in one ~488-line SKILL.md with well-organized headers but bulky inline content (full Example 1 entry, media HTML/iframe templates, full sidebar JSON) that would be better split into references/ files, with only one external reference signaled.	3 / 5
	Total	16 / 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 strong, concrete description that clearly states capabilities and provides explicit 'Use when' triggers covering multiple natural phrases. Minor gaps in action coverage and slight overlap risk with general docs skills keep it just below the top anchor on two dimensions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create and publish changelog announcements', 'creating detailed changelog documentation pages, 'adding sidebar announcement cards') but pads with the generic phrase 'ensuring everything follows project standards' and omits roadmap/social-media artifacts covered in the body.	4 / 5
Completeness	Explicitly answers both 'what' (create/publish changelog announcements and the complete workflow of pages and sidebar cards) and 'when' via a concrete 'Use when the user mentions...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('adding changelog entries', 'documenting new features', 'creating release notes', 'announcing product updates') are good coverage but a few common synonyms (e.g. 'shipping a release', 'version notes') are missing.	4 / 5
Distinctiveness Conflict Risk	The changelog/release-notes niche is fairly distinct with specific triggers, but 'documenting new features' has minor overlap risk with general documentation skills.	4 / 5
	Total	17 / 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: 5 suspicious	Warning

	Total	14 / 16 Passed

Repository: Agenta-AI/agenta
Path: .agents/skills/create-changelog-announcement/SKILL.md
Commit: e4008fa

Reviewed: 5 days 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.