CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-pr

在 kimi-code 仓库里创建或更新 PR 时使用:如何写出让 reviewer 只读描述就能从逻辑和架构上理解改动的 PR 描述,包括核心思路与结构图、"行为变化与受影响人群"表、可视化大纲,以及 UI/UX 变化的截图和录屏。

Quality

88%

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

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

Highly actionable, lean, and well-sequenced content that earns its length with repo-specific conventions Claude cannot infer. The main weakness is structure: everything lives in one long file, and the visualization catalog and media-upload procedure are natural candidates for one-level-deep reference files.

Suggestions

Move the visualization outline catalog (the diff/mermaid/ts example blocks and their rules) into a references/ file, keeping SKILL.md as a short overview that links to it — this would raise both progressive_disclosure and conciseness.

Split the asset-upload procedure (the pr-assets bash script, link format, and safety rules) into its own reference file, signaled from the workflow step where it is needed.

Add a brief error-recovery note to the publish and upload steps (e.g., what to do if 'gh pr edit --body-file' fails or the pr-assets push is rejected) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and repo-specific with no padding over concepts Claude already knows, but a few example blocks (the sequenceDiagram and TypeScript interface samples) restate patterns the surrounding rules already establish and could be trimmed.

4 / 5

Actionability

Guidance is fully executable throughout: exact gh/git commands ('gh pr view --json url,number,title,state', 'git diff main...HEAD', '--body-file'), a copy-paste-ready bash script for the pr-assets branch, and the exact asset-link format to emit.

5 / 5

Workflow Clarity

A clear five-step workflow with real checkpoints (check for an existing PR first, confirm the update succeeded, list media files for confirmation before pushing), but there is no error-recovery guidance if gh pr edit or the asset push fails.

4 / 5

Progressive Disclosure

In-document structure and cross-referencing are good (workflow steps point to named sections; external pointers like .agents/skills/review-pr/surfaces.md are clearly signaled), but with no bundle files the ~80-line visualization catalog and the asset-upload procedure are inlined in a 215-line SKILL.md instead of being split into reference files.

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: explicit when-clause, concrete artifact list, and a repo-scoped niche make it highly specific and low-conflict. The only gap is minor missing natural variations of the core trigger terms.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables — '核心思路与结构图'、'行为变化与受影响人群'表、可视化大纲、截图和录屏 — giving comprehensive, specific coverage of what the skill produces rather than vague capability claims.

5 / 5

Completeness

It opens with an explicit trigger clause ('在 kimi-code 仓库里创建或更新 PR 时使用…') and follows with a concrete 'what' listing the specific artifacts the description covers, explicitly answering both what and when.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present ('创建或更新 PR', 'PR 描述', 'reviewer', '截图和录屏'), but common variations like 'pull request', 'draft PR', or 'PR body' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The scope is tightly pinned to writing PR descriptions in the kimi-code repository, a clear niche with distinct triggers and minimal overlap risk against generic git/commit skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MoonshotAI/kimi-code

Path

.agents/skills/write-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.