CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

用于撰写 PR 正文。适用于用户要求起草、改写或改进 PR 正文,或希望 PR 更便于审阅时。

Quality

84%

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

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.

A highly actionable, well-structured template skill: the copy-paste PR body template plus per-section guidance leaves no ambiguity about the output, and it does not waste tokens explaining known concepts. Its weaknesses are structural: all eight example formats are inlined in SKILL.md rather than split into a reference file, and it points to a GLOSSARY.md that is absent from the bundle.

Suggestions

Move the visualization example catalog (pseudocode/call tree/component tree/file tree/Mermaid/diff examples) to a reference file such as references/visualizations.md, keeping the template and one-line selection guidance in SKILL.md.

Remove the "使用 GLOSSARY.md 中用户所在领域的语言" instruction or actually bundle a GLOSSARY.md — as written it points to a file that does not exist in the skill.

Consolidate the four diff examples into fewer, since each demonstrates the same format with a different subject.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it never explains what a PR, Mermaid, or a diff is, and guidance like "跳过所有开场白,保持文字简短" mirrors its own economy. However, the catalog of eight visualization examples (including four full diff variants and a full code-block example) has minor trim opportunities, so it sits at 'efficient; minor instances that could be trimmed' rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The PR body template is copy-paste ready with exact section headers (## Summary, ## Evidence, ## Merge Danger) and defined placeholders, and the worked examples (pseudocode, call tree, component tree, file tree, Mermaid, diff, full code) cover the common output cases. For an instruction-only skill this is fully actionable with no gaps.

5 / 5

Workflow Clarity

This is a single-task skill (write the PR body per the template) and the single action is unambiguous: the template fixes the output sequence (Summary → Evidence → Merge Danger) and each section's guidance states exactly what to fill in, including evidence tiers ("截图是 S-tier", "执行结果是 A-tier"). No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

Headers are clear, but the ~140-line visualization example catalog is content that could live in a separate reference file while SKILL.md keeps the template and selection guidance, matching anchor 3's 'content that should be separate is inline'. Additionally, the body's sole external reference — "使用 GLOSSARY.md 中用户所在领域的语言" — is dangling: no GLOSSARY.md exists anywhere in the skill bundle.

3 / 5

Total

17

/

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 well-formed description that explicitly states both what it does and when to use it, with natural trigger phrasing in Chinese. Its main weakness is thin capability coverage: it names only the single action of writing the PR body without distinguishing sub-capabilities.

Suggestions

List 1-2 more concrete, distinct capabilities beyond '撰写 PR 正文' (e.g., producing a Summary diagram, before/after Evidence, and a Merge Danger risk assessment) to raise specificity.

Add common trigger variations such as 'pull request 说明/description' or '撰写 PR' to broaden keyword coverage.

DimensionReasoningScore

Specificity

"用于撰写 PR 正文" names the domain (PR body) and one concrete action (writing), and the trigger clause only restates that action with synonyms ("起草、改写或改进 PR 正文"). This matches 'names domain and 1-2 concrete actions, but not comprehensive' — it does not list several distinct capabilities such as evidence gathering or risk assessment that would merit a 4.

3 / 5

Completeness

It explicitly answers what ("用于撰写 PR 正文") and when, with concrete trigger phrases ("适用于用户要求起草、改写或改进 PR 正文,或希望 PR 更便于审阅时"). The 'when' clause is fully explicit and specific, so this fits anchor 5 rather than anchor 4 where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Natural user phrasings are present: "起草、改写或改进 PR 正文" (draft, rewrite, or improve PR body) and "希望 PR 更便于审阅" (want the PR easier to review). A few natural terms are missing (e.g., 'pull request' spelled out, 'PR description/说明'), so it falls short of anchor 5's synonym/extension-level coverage but is clearly above anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

PR body drafting is a clear niche with distinct triggers, but "希望 PR 更便于审阅" (want the PR easier to review) creates minor overlap risk with PR-review skills — 'mostly distinct; minor overlap risk', not the minimal conflict risk of anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

vinvcn/mattpocock-skills-zh-CN

Path

skills/engineering/pr/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.