CtrlK
BlogDocsLog inGet started
Tessl Logo

changelog-collect

收集 ant-design 两个版本之间的 PR 信息并整理 changelog 草稿,更新到 CHANGELOG.zh-CN.md 和 CHANGELOG.en-US.md 时使用。适用于收集 changelog、生成 changelog、更新 changelog、版本对比等场景。

69

Quality

85%

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

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 content is highly actionable with a clear, well-validated multi-step workflow, but it is monolithic — large lookup tables and reference material are inlined rather than split into separate files, and some rules are redundantly restated across stages.

Suggestions

Move the emoji table, commit-type→emoji mapping, and the component-name list into a single `references/changelog-rules.md` and reference it one level deep to reduce SKILL.md size.

Deduplicate the filter/skip rules that appear in both section 1.5 and stage 2, stating them once and cross-referencing.

Trim explanatory prose around conventions Claude can infer (e.g., why PR links are added) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and examples, but filter rules and compliance guidance are restated across stages (1.5 vs stage 2) and some obvious conventions are over-explained, so it could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready guidance — `gh pr view ... --json`, `git log <from>..<to> --oneline`, `npm run lint:changelog`, plus complete changelog example blocks, a component-name list, and commit-type→emoji mapping tables.

5 / 5

Workflow Clarity

A clearly sequenced 22-step process with explicit validation checkpoint (`npm run lint:changelog` → fix → retry), interactive confirmation gates, and a batch subagent dispatch pattern, including a feedback loop for the destructive file write.

5 / 5

Progressive Disclosure

Single ~530-line SKILL.md with no bundle files and no external references; the large component-name list, emoji tables, and compliance tables are inlined where a one-level reference file would improve navigation.

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.

The description is concrete, actionable, and clearly scoped to the ant-design changelog task with explicit trigger phrases covering both what and when. It is among the stronger examples, with only minor room to broaden natural trigger variations.

DimensionReasoningScore

Specificity

Names multiple concrete actions against specific targets — '收集 PR 信息', '整理 changelog 草稿', '更新到 CHANGELOG.zh-CN.md 和 CHANGELOG.en-US.md' — covering the workflow comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (collect PR info, draft changelog, update the two CHANGELOG files) and 'when' ('适用于收集 changelog、生成 changelog、更新 changelog、版本对比等场景').

5 / 5

Trigger Term Quality

Includes natural user phrases ('收集 changelog、生成 changelog、更新 changelog、版本对比') with good synonym coverage, but lacks a few natural variations or file-type triggers.

4 / 5

Distinctiveness Conflict Risk

Scoped to the ant-design changelog workflow with named target files (CHANGELOG.zh-CN.md / CHANGELOG.en-US.md), giving it a clear niche and minimal overlap with other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (533 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
ant-design/ant-design
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.