CtrlK
BlogDocsLog inGet started
Tessl Logo

msg

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

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/msg/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

91%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 skill body is lean, highly actionable, and well-structured for a simple single-purpose task, with concrete commands and a copy-paste filename-generation snippet. Its only meaningful gap is the absence of an explicit validation/feedback loop around the staging step.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: numbered steps, exact git commands, and a tight message-format spec with no padding or explanation of git concepts.

5 / 5

Actionability

It gives fully executable commands (git status --short, git diff --cached, git log --oneline -5) and a copy-paste-ready python3 snippet that produces the unique temp filename, covering the common cases concretely.

5 / 5

Workflow Clarity

The two-mode workflow is clearly sequenced with checkpoints (展示文件清单, git diff --cached --stat confirmation), but it lacks an explicit validation/feedback loop for the staging step (e.g. what to do if git add fails or staged content is empty).

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no bundle files, and the content is well-organized into clearly headed sections (铁律, 带参数模式, 生成消息步骤, 消息格式, 输出后), satisfying the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific and distinctive, clearly delineating the two invocation modes and the hard constraint of never committing. It is slightly held back by trigger-term coverage and by giving 'when' guidance as argument syntax rather than natural user-intent phrases.

Suggestions

Add an explicit natural-language trigger clause such as 'Use when the user asks for a Chinese commit message or wants to stage related changes before drafting one' to strengthen completeness and trigger quality.

Include common synonyms like '提交信息' and 'commit message' so users phrasing the request in either language surface the skill.

Trim the negative constraint ('始终不执行 git commit') into the trigger guidance or keep it concise to reduce description length without losing the safety boundary.

DimensionReasoningScore

Specificity

It names the domain (git staged content) and several concrete actions (生成中文提交消息草稿, git add to staged, not executing git commit), but the action set is narrow (draft generation + targeted staging) with minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does and gives explicit 'when' guidance via the two invocation modes (/msg with and without arguments), though the 'when to use' trigger is tied to argument syntax rather than user-intent phrases.

4 / 5

Trigger Term Quality

It contains relevant terms like '提交消息草稿', 'git 缓存区/staged', 'git add', and '/msg', but lacks common natural synonyms a user might say (e.g. 'commit message', '提交信息') and file/extension variations.

3 / 5

Distinctiveness Conflict Risk

The niche is distinct (Chinese draft-only commit messages, never committing, targeted staging only), with minor overlap risk against general git helper skills.

4 / 5

Total

15

/

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.

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.