CtrlK
BlogDocsLog inGet started
Tessl Logo

your-skill-name

用一句中文说明这个 Skill 能做什么,以及何时应该触发它

28

Quality

20%

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

Fix and improve this skill with Tessl

tessl review fix ./_template/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is an unfilled skill skeleton: structurally clean but content-empty. Conciseness and organization are sound, but actionability and workflow clarity collapse because every step and validation check is a placeholder with no executable guidance. It needs concrete steps, code/commands, and real validation before it can function as a skill.

Suggestions

Replace each placeholder step with concrete, executable instructions (specific commands or copy-paste-ready code) covering the common cases.

Flesh out the 验证 section with an actual validation command or checkpoint that proves the skill honors its output contract, especially if any step is destructive or batch-oriented.

Populate the 输出契约 section with the concrete expected output format so Claude can verify results, and use the empty references/ or scripts/ directories only if detail genuinely needs to be split out.

DimensionReasoningScore

Conciseness

The body is lean with short section headers and single-line placeholders and does not pad with concepts Claude already knows; it is not a 5 only because the placeholder lines are author-facing meta-text rather than skill content that fully earns its place.

4 / 5

Actionability

Every step is a placeholder ("第一步", "第二步", "第三步") with no concrete code, commands, or specific guidance, matching the 'entirely vague or abstract; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

A numbered sequence (1–3) is present but the steps are undefined placeholders, and the 验证 section offers no actual validation command or checkpoint, matching 'rough sequence present but many gaps; validation absent'.

2 / 5

Progressive Disclosure

The body is short and organized into clearly labeled sections with no nested references; it is not a 5 because the bundle directories (references/, scripts/) are empty and the section bodies are placeholders rather than real overview content.

4 / 5

Total

11

/

20

Passed

Description

0%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 an unfilled template instruction rather than a real capability statement, so it scores the minimum across every dimension: no domain, no actions, no triggers, and no niche. It must be replaced with concrete third-person capabilities and explicit 'Use when...' trigger guidance.

Suggestions

Replace the placeholder with a concrete third-person description naming the skill's domain and 2–4 specific actions (e.g., 'Extracts…, fills…, merges…').

Add an explicit 'Use when…' clause listing natural trigger phrases a user would actually say, including synonyms and file extensions.

Make the description distinctive enough to avoid overlapping with sibling skills by naming the specific artifact types or operations it handles.

DimensionReasoningScore

Specificity

The description is a placeholder instruction ("用一句中文说明这个 Skill 能做什么") that names no domain and no concrete actions, matching the 'entirely vague; no concrete actions' anchor; it cannot score higher since nothing actionable is stated.

1 / 5

Completeness

It answers neither 'what does this do' nor 'when should Claude use it' — it is a prompt to the author to write those, matching the 'missing both what and when' anchor; the missing 'Use when...' clause also caps completeness at 3, and this is well below that.

1 / 5

Trigger Term Quality

No natural user keywords appear; the phrase "何时应该触发它" only describes the concept of triggering without supplying any actual trigger terms, matching the 'no natural keywords' anchor.

1 / 5

Distinctiveness Conflict Risk

A generic template instruction with no niche would conflict with virtually any skill, matching the 'entirely generic' anchor; nothing distinguishes it from other skills.

1 / 5

Total

4

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ooooooooooooooooooop/agent-tools
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.