CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-skills

创建或修改 Clowder AI skill / MCP tool description 的元技能(含质量标准、范本、发布)。 Use when: 写新 skill、修改现有 skill、写/改 MCP tool description、验证 skill 质量; 或者功能实现中产出了 SKILL.md / cat-cafe-skills/ 新目录 / manifest.yaml skill 条目。 Not for: 使用 skill(直接触发对应 skill)。 Output: 新/更新的 SKILL.md + manifest 条目 + symlinks。 GOTCHA: 软硬同重——skill/MCP 质量 = 代码质量;不要写模型已知的通用教程,先过价值门禁。

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually high-signal meta-skill: nearly every section encodes house-specific know-how (gates, exemplars, templates, exact pnpm commands, provider adapter contracts) rather than generic tutorials, and publishing is gated by explicit checks. Its main costs are duplicated value-gate content that re-treads the same table, and two dead "(internal reference removed)" pointers that break the otherwise clean on-demand reading structure.

Suggestions

Merge the opening 价值门禁 table with the T0-0 载体选择 table into a single gate section — they cover the same decision and currently force the reader through it twice.

Resolve or remove the two '*(internal reference removed)*' citations (T0-1 进场门票机制 and the 知识工程完整方法论 row in 深入学习) so every reference in the reading tables navigates to a real file.

Add one numbered end-to-end authoring workflow (gate → exemplar → draft from template → publish checks → next) so the sequenced pieces currently spread across sections read as a single path with validation checkpoints.

DimensionReasoningScore

Conciseness

The body is largely dense, house-specific tables, but the value-gate material is stated twice ("写 skill 前先判定:它是不是在给聪明 agent 复述训练集里已经很强的通用知识?" with a 5-row table at the top, then again as "T0-0:Skill 价值门禁" with a second overlapping table), and sections like "T0-1" re-explain Claude-visible mechanisms (the three-layer loading model) that border on general knowledge. This matches the 3 anchor ("mostly efficient but includes some unnecessary explanation or could be tightened") — below 4 because the duplication and re-teaching are more than minor, above 2 because there is no padding of the "what is a PDF" variety.

3 / 5

Actionability

Quotes: the copy-paste "## SKILL.md 结构模板" markdown skeleton; exact commands "pnpm sync:skills(不要手动 ln -s)", "pnpm check:skills、pnpm check:skills:references、pnpm check:skills:surfaces 全绿"; and concrete config fields "SKILL.md frontmatter 写 disable-model-invocation: true" / "agents/openai.yaml 写 policy.allow_implicit_invocation: false". Per the code-vs-instruction note, this instruction-only skill's guidance is fully concrete and covers the common cases, matching the 5 anchor rather than 4 ("minor gaps").

5 / 5

Workflow Clarity

The publishing path is a clear 5-step sequence with an explicit validation checkpoint ("4. 验证:pnpm check:skills ... 全绿;... 再跑该 claim 对应的定向 checker/test" plus conditional gate escalation), and "下一步" chains onward. However, the authoring workflow itself (value gate → read exemplar → write → publish) is distributed across separate sections rather than given as one sequenced path with checkpoints, so it matches the 4 anchor ("clear sequence with most checkpoints present; minor validation gaps") — not 5, since the RED-scenario/validation guidance for the writing phase is referenced only obliquely ("先看 agent 在无 skill 时怎么失败").

4 / 5

Progressive Disclosure

The "深入学习(按需阅读)" table signals one-level-deep references with purpose notes ("writing-skills/cat-cafe-skill-quality-principles.md" — 废话 skill 判定; "../.cat-cafe-shared-refs/mcp-tool-description-standard.md" — 好/差对比), and the exemplar table plays the same role, so heavy material is correctly offloaded. It falls short of the 5 anchor because two citations are literally "*(internal reference removed)*" (in T0-1 and the 深入学习 table) — references that navigate nowhere — and the remaining referenced paths sit outside the bundle and cannot be verified, matching 4's "references mostly clear; minor organization gaps".

4 / 5

Total

16

/

20

Passed

Description

95%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 model three-part routing description: explicit what/when/not-for/output with concrete artifact-name triggers and a GOTCHA that encodes the skill's core stance. The only weakness is that some capabilities (quality standards, exemplars, publishing) are gestured at in parentheses rather than enumerated, which slightly limits specificity.

DimensionReasoningScore

Specificity

Quotes: "创建或修改 Clowder AI skill / MCP tool description 的元技能(含质量标准、范本、发布)" and "Output: 新/更新的 SKILL.md + manifest 条目 + symlinks" — it names the domain and several concrete actions and artifacts (create, modify, write/revise MCP tool description, verify skill quality, produce SKILL.md + manifest entry + symlinks). It falls just below the 5 anchor because several actions are compressed into parentheticals ("含质量标准、范本、发布") without being individually spelled out, leaving minor coverage gaps.

4 / 5

Completeness

Quotes: "创建或修改 Clowder AI skill / MCP tool description 的元技能" (explicit what), "Use when: 写新 skill、修改现有 skill、写/改 MCP tool description、验证 skill 质量;或者功能实现中产出了 SKILL.md / cat-cafe-skills/ 新目录 / manifest.yaml skill 条目" (explicit when with concrete triggers), plus "Not for" and "Output:" clauses. Both what and when are explicitly and concretely answered — the 5 anchor — not merely present-with-room-to-improve as at 4.

5 / 5

Trigger Term Quality

Quotes: "写新 skill、修改现有 skill", "写/改 MCP tool description", and the trigger list "SKILL.md", "cat-cafe-skills/", "manifest.yaml skill", "写 MCP", "MCP description", "tool description" — comprehensive natural-phrase coverage including the exact file names and directory strings a user or agent would emit when needing this skill. It clearly matches the 5 anchor ("comprehensive coverage of natural terms including synonyms and file extensions") rather than 4, which would require notable missing natural terms.

5 / 5

Distinctiveness Conflict Risk

Quotes: "Not for: 使用 skill(直接触发对应 skill)" and triggers anchored to unique artifacts ("SKILL.md", "cat-cafe-skills/", "manifest.yaml skill 条目") give it a clear niche with minimal overlap against generic documentation or coding skills. The negative example explicitly fences off the nearest confusion (invoking vs. authoring skills), matching the 5 anchor rather than 4's "minor overlap risk with closely related skills".

5 / 5

Total

19

/

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
zts212653/clowder-ai
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.