CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

87%

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%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 workflow is exceptionally clear and actionable, with strong validation and feedback loops throughout. The main weaknesses are repetition of the same rules across multiple sections and the absence of any progressive disclosure — a long single file where reference material could be split out.

Suggestions

Split the Chinese wording style guide (step 6) and the curation gates (step 4) into reference files (e.g. references/chinese-style.md, references/curation.md), keeping SKILL.md as a lean overview with one-level-deep, clearly signaled links.

Deduplicate the Rules, Common Mistakes, and Stop Signals sections — many rows restate workflow rules verbatim; consolidate to a single authoritative statement plus a short pointer for the rare cases not covered in the workflow.

Trim the long prose paragraphs in step 4 (the channel test and Bug Fixes rationale) to their operative rules; the extended justification consumes tokens without changing what the executor does.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no explaining of known concepts), but the same rules are restated two to three times across the Workflow, the Rules list, the 35-row Common Mistakes table, and Stop Signals (e.g. the Thanks-credit removal, never-edit-upstream, and 10-entry threshold rules each appear three or more times). This repetition is noticeable padding that could be tightened without losing clarity.

3 / 5

Actionability

Guidance is fully executable: exact git/npm/rg/pnpm commands, the branch-naming pattern, the exact catch-all and Chinese strings to use, a complete PR body template, and concrete bad/better translation examples. Everything is copy-paste ready.

5 / 5

Workflow Clarity

Ten clearly numbered steps with preconditions, a verify step (git diff plus the docs build), an explicit human-review checkpoint with a feedback loop (edits trigger re-running step 7 and returning to the checkpoint), and stop signals for failure recovery.

5 / 5

Progressive Disclosure

There are no bundle files at all; the skill is a ~490-line monolith. Section headers are strong and make the file navigable, but substantial self-contained material (the Chinese wording style guide, the curation gates in step 4, and the PR template) clearly belongs in separate reference files, so content that should be separate is inline.

3 / 5

Total

16

/

20

Passed

Description

92%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: it states the exact files involved, the concrete actions (sync, translate implied by the zh target, PR on a dedicated branch), and an explicit 'Use after' trigger tied to release completion. Only minor synonym coverage is missing.

DimensionReasoningScore

Specificity

The description names exact source and target paths ("sync apps/kimi-code/CHANGELOG.md into docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md") and concrete actions including "then open a PR on a dedicated branch", covering the full task comprehensively rather than just 1-2 actions.

5 / 5

Completeness

It explicitly answers both what (sync the CLI changelog into the two docs changelog files and open a PR) and when ("Use after a release succeeds, when maintainers need to...") with a concrete trigger condition.

5 / 5

Trigger Term Quality

Natural terms users would say are present ("after a release", "changelog", "sync", "open a PR"), but coverage stops short of synonyms like "release notes" or "translate" that a user might naturally use for this task.

4 / 5

Distinctiveness Conflict Risk

A clear niche (post-release changelog sync for a specific package) with distinct file-path triggers; it is unlikely to fire for any other skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 11 suspicious

Warning

Total

15

/

16

Passed

Repository
MoonshotAI/kimi-code
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.