changelog-update

Update CHANGELOG.md following TalkPipe conventions. Use after implementing a feature, fixing a bug, or making any user-facing change. Ensures correct "update vs add" logic and entry format.

0.93x

Quality

86%

Does it follow best practices?

Impact

70%

0.93x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

An efficient, actionable instruction-only skill with concrete examples and clear decision logic. The only gap is a minor verification feedback loop in the workflow, which keeps workflow clarity just below the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no padding about what a changelog is; every section (When to Use, Decision Flow, Format Rules, Examples, Checklist) earns its place and assumes Claude's competence.	5 / 5
Actionability	Copy-paste ready markdown bullet examples cover the common cases (new feature, minor update, bug fix, multiple related changes) alongside concrete format and placement rules.	5 / 5
Workflow Clarity	A clear two-step Decision Flow and a closing Checklist provide sequencing and validation, but there is no explicit verify-the-result feedback loop for the written entry.	4 / 5
Progressive Disclosure	This single-purpose skill has no bundle files and no need for external references; its well-organized sections satisfy the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 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.

A strong description that clearly states both the skill's purpose and its trigger conditions in third person. It is specific to a distinct niche with natural trigger phrasing, with only minor room to expand concrete action coverage and synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain ('CHANGELOG.md', 'TalkPipe conventions') and 1-2 concrete actions ('update vs add logic', 'entry format') but is not comprehensive on the mechanics involved.	3 / 5
Completeness	Explicitly answers both what ('Update CHANGELOG.md following TalkPipe conventions... Ensures correct update vs add logic and entry format') and when ('Use after implementing a feature, fixing a bug, or making any user-facing change') with concrete triggers.	5 / 5
Trigger Term Quality	'implementing a feature, fixing a bug, or making any user-facing change' are natural phrases users say, with good keyword coverage, though synonyms like 'release notes' are absent.	4 / 5
Distinctiveness Conflict Risk	The changelog-update niche is mostly distinct with clear triggers, with only minor overlap risk against closely related commit-message or release-notes skills.	4 / 5
	Total	16 / 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: sandialabs/talkpipe
Path: .cursor/skills/changelog-update/SKILL.md
Commit: 14049ad

Reviewed: 2 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.