CtrlK
BlogDocsLog inGet started
Tessl Logo

msg

根据 git 缓存区(staged)内容生成中文提交消息草稿。无参数时只看缓存区、不执行 git add;带参数 `/msg X` 时先把与 X 相关的改动 `git add` 到缓存区,再生成消息草稿。始终不执行 git commit。

74

Quality

91%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable, well-sequenced skill that respects Claude's intelligence and provides copy-paste-ready commands with verification checkpoints.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it never explains what git, staging, or commit messages are; every section (铁律, 执行步骤, 消息格式, 输出后) earns its place.

3 / 3

Actionability

Fully executable guidance: concrete git commands (git status --short, git add <paths>, git diff --cached, git log --oneline -5) and a copy-paste python/bash snippet for deterministic temp-file naming.

3 / 3

Workflow Clarity

Clear, sequenced flows for both /msg X and the shared message-generation steps, with explicit checkpoints (show file list before add, 'git diff --cached --stat 确认缓存区内容'); the deliberately non-destructive design avoids the destructive-ops validation cap.

3 / 3

Progressive Disclosure

A single-purpose, ~70-line skill with well-organized sections and no nested or deeply-referenced files; nothing here warrants splitting into separate references, so well-organized inline sections suffice.

3 / 3

Total

12

/

12

Passed

Description

82%

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 specific, action-oriented, and distinct, but it omits an explicit 'Use when' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for help writing a commit message, wants to draft 提交消息, or invokes /msg.'

Include a couple of natural user phrasings (e.g. '写提交消息', '生成 commit message') to broaden trigger-term coverage beyond the /msg invocation.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — '生成中文提交消息草稿', 'git add 到缓存区', '不执行 git commit' — with no first/second person voice, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does (generate Chinese commit drafts, handle /msg X, never commit) but provides no explicit 'Use when...' trigger guidance, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Good natural-term coverage for the domain: '提交消息', 'git commit', 'git add', '缓存区/staged', and the '/msg X' invocation — terms a user would naturally say when asking for a commit message.

3 / 3

Distinctiveness Conflict Risk

A clear niche — Chinese commit-message drafting gated behind the '/msg' trigger — that is unlikely to fire for or conflict with unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
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.