sync-changelog

Use after a release succeeds, when maintainers need to sync apps/kimi-code/CHANGELOG.md into docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md, then open a PR on a dedicated branch.

Quality

86%

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

85%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 content is highly actionable with a clearly sequenced, validated workflow and concrete commands and templates. Its weak point is progressive disclosure: a large, reference-heavy body lives entirely in one file with no bundle files to offload detail.

Suggestions

Move the elaborate curation gates (reader-action test, channel test, density defaults) and the Common Mistakes table into a separate reference file (e.g. references/curation-guide.md) referenced one level deep from step 4, keeping SKILL.md an overview.

Dedupe the Common Mistakes table against the Rules section, or consolidate them into one location to remove the repetition that inflates token cost.

Tighten the philosophical prose in step 4 to the operational rule in each bullet, preserving the decision criteria without the extended argumentation.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earns its tokens with concrete rules and no elementary concept padding, but the elaborate curation rationale in step 4 and the Common Mistakes table that duplicates the Rules section offer minor trimming opportunities.	4 / 5
Actionability	Fully executable throughout: exact git/npm/gh/pnpm commands, copy-paste commit and PR-message templates, exact section-heading mappings, and verbatim catch-all wording with Chinese variants cover the common cases.	5 / 5
Workflow Clarity	Ten numbered steps are clearly sequenced with an explicit validation checkpoint (step 7 Verify with git diff + pnpm build), a human-review checkpoint, and a stated feedback loop that re-runs verification before returning to review.	5 / 5
Progressive Disclosure	Sectioning and navigation are good, but no bundle files are provided and substantial reference-grade content (the dense two-gate curation philosophy and the large Common Mistakes table) is inlined in a ~488-line single file rather than split into one-level-deep references.	3 / 5
	Total	17 / 20 Passed

Description

87%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, well-triggered, and clearly distinct, explicitly answering both what it does and when to use it. Its only weakness is that it omits the English-to-Chinese translation action, which is a core part of the workflow.

Suggestions

Mention the English-to-Chinese translation step in the description, e.g. '...sync apps/kimi-code/CHANGELOG.md into the English docs changelog, translate the new entries into Chinese, then open a PR on a dedicated branch.'

Add standalone synonyms a maintainer might say ('changelog', 'release notes') alongside the file paths to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names concrete source/target files and two actions (sync changelog into EN+ZH docs, open a PR on a dedicated branch), but omits the central English-to-Chinese translation step, so it is several specific actions with a minor coverage gap rather than comprehensive.	4 / 5
Completeness	Explicitly answers both 'what' (sync into the two named docs files, open a PR) and 'when' ('Use after a release succeeds, when maintainers need to sync ...'), with concrete trigger phrases, fitting the top anchor.	5 / 5
Trigger Term Quality	Includes a clear natural trigger ('Use after a release succeeds') and maintainer phrases ('sync ... CHANGELOG.md', 'open a PR') with .md extensions, but is missing common synonyms like 'changelog'/'release notes' as standalone terms.	4 / 5
Distinctiveness Conflict Risk	Names exact repo paths, post-release timing, and a dedicated-branch constraint, carving a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 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: 11 suspicious	Warning

	Total	15 / 16 Passed

Repository: MoonshotAI/kimi-code
Path: .agents/skills/sync-changelog/SKILL.md
Commit: d4e0ad4

Reviewed: 1 day 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.