CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

your-skill-name

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

Quality

36%

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

The canonical home for this skill is your-skill-name in ooooooooooooooooooop/agent-tools

SKILL.md
Quality
Evals
Security

Quality

Content

43%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 body is a clean, well-organized skeleton with excellent brevity and structure, but it is entirely unfilled — every section holds placeholder text rather than concrete instructions, and the workflow steps and validation section carry no executable content.

Suggestions

Replace each placeholder section with concrete, executable guidance — specific commands, code, or unambiguous instructions instead of "说明..." directives.

Flesh out the 工作流程 steps with real, sequenced actions and add an actual validation command or check in the 验证 section (especially any feedback loop if operations are destructive or batch).

Define a concrete 输出契约 with an explicit example of the expected output format.

DimensionReasoningScore

Conciseness

The body is extremely lean with zero over-explanation of concepts Claude already knows, so it sits above the midpoint. It falls short of a 5 because the placeholder tokens ("第一步", "说明预期的输出格式") convey no instructions and thus do not fully earn their place.

4 / 5

Actionability

Every section is placeholder direction ("说明何时应该触发这个 Skill", "说明预期的输出格式") with no code, commands, or executable guidance — it describes what should be written rather than instructing, matching the lowest anchor.

1 / 5

Workflow Clarity

A numbered sequence structure exists (1. 第一步 / 2. 第二步 / 3. 第三步) so steps are not entirely missing, but the steps are literal placeholders, poorly defined, and the 验证 section contains no actual validation checkpoint — matching 'Rough sequence present but many gaps; validation absent'.

2 / 5

Progressive Disclosure

The skill is well under 50 lines with clearly organized sections (使用场景, 工作流程, 输出契约, 验证), no inlined content that belongs in separate files, and no external references needed — the references/ and scripts/ directories are empty and the body references no other files, so the simple-skill exception applies fully.

5 / 5

Total

12

/

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 field is an unfilled template placeholder: it instructs the skill author what to write instead of describing what the skill does or when to trigger it. It fails all four dimensions at the lowest anchor.

Suggestions

Replace the placeholder description with concrete capability statements in third person (e.g., 'Processes X files to produce Y. Use when the user mentions X, Z, or .ext files').

Add an explicit 'Use when...' clause naming concrete trigger phrases, synonyms, and file extensions users would naturally say.

Replace the placeholder triggers entries ("触发短语 1", "触发短语 2") with real trigger phrases drawn from the skill's actual use cases.

DimensionReasoningScore

Specificity

The description is a template instruction ("用一句中文说明这个 Skill 能做什么,以及何时应该触发它") rather than a statement of any capability; it names no domain and no concrete actions, matching the 'Entirely vague; no concrete actions; pure abstract language' anchor.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered — the field instructs the author on what to write instead of describing anything. The 'missing Use when... clause caps completeness at 3' guideline is not even approached here, as there is no 'what' either.

1 / 5

Trigger Term Quality

The text contains no natural keywords users would say — it is meta-instructional placeholder text, and the triggers field holds literal placeholders ("触发短语 1", "触发短语 2"). This matches the 'No natural keywords' anchor and cannot score 2 since even generic domain keywords are absent.

1 / 5

Distinctiveness Conflict Risk

The description conveys nothing distinctive — it is a generic template instruction that describes no niche, so it cannot be distinguished from any other skill and carries total conflict risk.

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.

Validation — 15 / 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/personal-ai

Path

_template/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.