CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pre-changelog

Use before merging a kimi-code release PR to preview the user-facing CLI changelog in Chinese. Reads the changelog that changesets pre-generated in the release PR, then reuses sync-changelog's strip / classify / translate logic to render a Chinese preview. Writes no files.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, highly actionable read-only workflow: every command, output string, and failure stop-condition is concrete, and detail is properly delegated to the sibling sync-changelog skill. The weaknesses are minor — some redundant restatement of the read-only rule and the GitHub link caveat, and one overlong collapse-rules paragraph that hurts scannability.

Suggestions

State the read-only constraint once (e.g., in Rules) and remove the repetitions in the intro and step 4; likewise explain the GitHub-link-target caveat only in step 4 where the link is emitted.

Break the 'Collapse low-signal entries' bullet into short sub-bullets (reader-action test / channel test / section density / catch-all wording / pointer sentence) or move the shared folding rules into the sync-changelog reference so both skills cite one source.

DimensionReasoningScore

Conciseness

The body is almost entirely task-specific policy with no concept explanations or padding, but 'Read-only / writes no files' is stated three times (intro, step 4, Rules) and the note that the GitHub link target 'does not yet contain this version's block' is explained twice nearly verbatim. The ~450-word single 'Collapse low-signal entries' bullet also needs tightening rather than trimming of whole concepts.

4 / 5

Actionability

Copy-paste-ready 'gh pr list' and 'gh api' commands with exact --jq filters, verbatim Chinese catch-all strings, a concrete output template, and an exact URL-rewrite mapping with a worked example. The strip/classify/translate detail is delegated but with precise numbered-step references to sync-changelog.

5 / 5

Workflow Clarity

Four numbered steps with explicit stop conditions at every failure mode ('If none is open, nothing to preview — stop', 'not in the diff … stop and tell the user', 'not in English, flag it and stop'), a PR disambiguation rule (headRefName: changeset-release/main), and CI-status reporting. The skill is read-only, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist; the sibling-skill reference ('Read sync-changelog first') is well-signaled and one level deep, and sections are clearly organized. However, the collapse-rules bullet in step 3 is a dense wall of text (~450 words in one bullet) that should be split out or broken up, leaving a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

88%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: concrete, third-person, covers what/when/read-only-scope explicitly and sits in a clearly distinct niche. The only improvements are broader natural-synonym coverage (e.g., 'release notes') and sharper differentiation from the sibling sync-changelog skill it builds on.

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the full scope — 'Reads the changelog that changesets pre-generated in the release PR', 'reuses sync-changelog's strip / classify / translate logic', 'render a Chinese preview', 'Writes no files' — with no coverage gaps, matching the comprehensive-actions anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

Explicitly answers both: what ('preview the user-facing CLI changelog in Chinese … render a Chinese preview') and when ('Use before merging a kimi-code release PR') — a concrete, specific trigger clause, not the weakly-implied 'when' of the 3-4 anchors.

5 / 5

Trigger Term Quality

Natural terms users would say are present ('release PR', 'changelog', 'preview', 'merge', 'Chinese'), but common synonyms such as 'release notes' are missing, so it falls short of the comprehensive-synonyms anchor at 5 while clearly exceeding 'some relevant keywords' at 3.

4 / 5

Distinctiveness Conflict Risk

A clear niche (pre-merge Chinese preview of a kimi-code release PR) with distinct 'before merging / preview' triggers, but it explicitly shares logic with the closely related sync-changelog skill, so changelog-related requests carry minor overlap risk with that sibling — matching the 4 anchor rather than minimal-conflict 5.

4 / 5

Total

18

/

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: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

MoonshotAI/kimi-code

Path

.agents/skills/pre-changelog/SKILL.md

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.