CtrlK
BlogDocsLog inGet started
Tessl Logo

chinese-documentation

中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用,不要根据上下文自动触发。

70

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable Chinese documentation writing guide with concrete examples, templates, and a verification checklist. Its main weaknesses are token redundancy from repeated topics and a monolithic structure that forgoes progressive disclosure via reference files.

Suggestions

Consolidate the duplicated guidance: '过度翻译' appears in both '中英混排最佳实践' and '常见问题/问题三', and '中英标点混用' appears in both '标点符号' and '常见问题/问题四' — reference one from the other instead of restating.

Tighten or remove the '概述' narration ('中文技术文档最常见的问题不是内容不够,而是读起来别扭……') since it restates context Claude already understands; lead with the rules.

Move the API 接口文档模板, README.md 中文模板, and 写作检查清单 into separate reference files (e.g. references/api-template.md, references/readme-template.md, references/checklist.md) and keep SKILL.md as a concise overview that links to them, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The ~450-line body is mostly useful concrete rules, but includes introductory narration in '概述' and redundancy — '过度翻译' and '中英标点混用' are each covered twice across sections — so it could be tightened; not a 1 because the bulk is reference material rather than concepts Claude already knows.

2 / 3

Actionability

Packed with concrete good/bad example pairs and copy-paste-ready templates (API 接口文档模板, README.md 中文模板), giving fully executable, specific guidance.

3 / 3

Workflow Clarity

Although not a multi-step workflow, the closing '写作检查清单' acts as an explicit validation checkpoint organized by 排版/术语/内容/格式, and the content is clearly structured — consistent with scoring notes allowing 3 for well-organized single-purpose skills.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a monolithic ~450-line file with no bundle files and no file-level splitting; the API/README templates and 常见问题 guide are inline content that could be factored into reference files, matching the 'content that should be separate is inline' anchor rather than a 1 (it is not poorly organized) or a 3 (nothing is split out).

2 / 3

Total

10

/

12

Passed

Description

100%

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 strong, well-scoped description: it states concrete coverage areas, provides natural trigger terms and an explicit slash-command invocation condition, and explicitly guards against auto-triggering. It cleanly answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple specific concrete coverage areas — '中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定' — rather than vague claims, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both 'what' (排版参考 covering the listed areas) and 'when' ('仅在用户显式 /chinese-documentation 时调用'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('中文文档排版', '中文文案排版') plus an explicit slash-command trigger ('/chinese-documentation'), giving good coverage of likely invocations.

3 / 3

Distinctiveness Conflict Risk

Narrow Chinese-documentation-typography niche plus the explicit '不要根据上下文自动触发' instruction make it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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: 7 missing

Warning

Total

12

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.