CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-skills

当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用

Quality

59%

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 ./skills/writing-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A rich, highly actionable guide with concrete examples, explicit validation loops, and well-signaled structure. Its main weaknesses are significant verbosity relative to its own token-efficiency rules, duplicated example sections, a broken numbered list in the discovery workflow, and references to files that are not shipped alongside it.

Suggestions

Cut the body to honor its own token budget: merge the two repeated good/bad YAML example blocks in the 技能发现优化 section into one, and deduplicate the 铁律/合理化借口/红线 material against the deployment checklist.

Fix the '发现工作流' numbered list, which skips step 2 (1, 3, 4, 5, 6).

Ship the referenced files (testing-skills-with-subagents.md, persuasion-principles.md, anthropic-best-practices.md, render-graphs.js) in references/ or scripts/ — or inline the essential parts — so the one-level-deep links resolve from this bundle.

DimensionReasoningScore

Conciseness

The ~670-line body is noticeably verbose and self-contradictory: it prescribes '<500 词' for skills while far exceeding that, repeats the good/bad description guidance across two full YAML example blocks in the SDO section, and restates the anti-rationalization rules in the 铁律, 合理化借口表, and checklist sections. Several sections are padded rather than earning their tokens, fitting the 'noticeably verbose' anchor rather than the 'mostly efficient' one.

2 / 5

Actionability

Guidance is highly concrete and executable — good/bad YAML pairs for descriptions, runnable commands ('wc -w skills/path/SKILL.md', 'node ./render-graphs.js ../some-skill'), a 5-step micro-test protocol with repetition counts, and a per-phase checklist. It falls short of fully copy-paste-ready coverage because the complete testing methodology is delegated to 'testing-skills-with-subagents.md', which is not part of this bundle.

4 / 5

Workflow Clarity

The red-green-refactor sequence is clearly laid out with explicit validation checkpoints (run baseline, record verbatim, re-run until '无懈可击') plus TodoWrite-driven checklists. A minor defect keeps it below the top anchor: the '发现工作流' numbered list runs 1, 3, 4, 5, 6 — skipping step 2 — which breaks an otherwise explicit sequence.

4 / 5

Progressive Disclosure

Section structure is clear with headers, tables, and one-level-deep file references, but none of the referenced files (anthropic-best-practices.md, persuasion-principles.md, testing-skills-with-subagents.md, render-graphs.js, graphviz-conventions.dot) exist in this bundle — references/, scripts/, and assets/ are all absent — leaving navigation unresolvable. Additionally, 100+ line deep-dives (the SDO section, the testing methodology) are inlined, which the skill's own separation rules say belong in separate files; this fits the 'some structure, references present but content that should be separate is inline' anchor rather than the well-placed anchor of 4.

3 / 5

Total

13

/

20

Passed

Description

52%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 a well-formed, trigger-focused 'Use when...' clause with three concrete, naturally phrased scenarios and low conflict risk. Its main weakness is that it entirely omits what the skill does (applying TDD to skill documentation), which caps completeness and specificity.

Suggestions

Prepend a brief third-person capability statement (e.g. what the skill provides — applying test-driven development to writing and validating skill documentation) before the '当…时使用' trigger clause, so both 'what' and 'when' are explicit.

Add natural search terms users and agents would use, such as '编写技能', 'SKILL.md', 'frontmatter', or '技能文档', to broaden keyword coverage.

Include concrete failure symptoms that indicate this skill applies (e.g. an agent skipping tests for a skill edit, or shipping an unvalidated SKILL.md) to sharpen triggering.

DimensionReasoningScore

Specificity

The description names the domain and three concrete trigger actions ("创建新技能、编辑现有技能或在部署前验证技能是否有效" — creating, editing, and pre-deploy validation of skills), but states no capability at all, matching the anchor for domain plus concrete actions without comprehensive coverage rather than the level above, which expects several specific capability actions.

3 / 5

Completeness

Only the 'when' is present ("当…时使用" = 'Use when...') with no statement of what the skill does; this matches the anchor 'only when is present without what' and sits below the level-3 anchor, which requires a clear 'what'. The explicit 'Use when' clause is present, so the missing-trigger cap of 3 is not the binding constraint here.

2 / 5

Trigger Term Quality

Phrases like "创建新技能", "编辑现有技能", and "部署前验证" are exactly what a user would say when needing this skill, giving good keyword coverage; a few natural variations are missing (e.g. "编写技能", "SKILL.md", "技能文档"), so it does not reach the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

Skill authoring/editing/validation is a clear, specific niche that would rarely trigger the wrong skill, though there is minor overlap risk with general TDD or testing-skills skills — the 'mostly distinct' anchor rather than the minimal-conflict anchor of 5.

4 / 5

Total

13

/

20

Passed

Validation

62%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (682 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

10

/

16

Passed

Repository

jnMetaCode/superpowers-zh

Path

skills/writing-skills/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.