chinese-documentation

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/chinese-documentation/SKILL.md

Quality

Content

71%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 thorough, highly actionable Chinese-typography reference with concrete examples, templates, and a checklist. Its weaknesses are length/verbosity and a monolithic single-file structure that does not leverage progressive disclosure via separate reference files.

Suggestions

Move the full README.md and API-document templates into separate files under references/ (e.g. references/readme-template.md, references/api-doc-template.md) and link to them from SKILL.md to reduce the inline footprint and enable one-level-deep progressive disclosure.

Trim overlap between the 中文排版规范 rules and the 常见问题与避坑指南 section, consolidating the 机翻味/标点混用 examples so each rule appears once.

Tighten or remove content restating basic conventions Claude already knows (e.g., elementary spacing rules) and keep only team-specific or non-obvious guidance to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete good/bad pairs, but at ~450 lines it repeats some material across the 规范 and 常见问题 sections and includes long full templates that could be tightened; assumes only some of Claude's prior knowledge of basic CJK typography.	3 / 5
Actionability	Highly actionable throughout: concrete do/don't code-fenced examples for spacing, punctuation, numbers, and terms, plus copy-paste-ready README and API-document templates and a pre-publish checklist covering common cases.	5 / 5
Workflow Clarity	As a reference/style skill it has no multi-step process, but the closing 写作检查清单 ('在发布文档前，逐项检查') acts as an explicit validation checkpoint; not a 5 because there is no sequenced workflow or error-recovery loop.	4 / 5
Progressive Disclosure	No bundle files exist and the entire reference is a single monolithic ~450-line document; section headers give decent navigation, but substantial template content (README, API doc) that could live in separate reference files is inlined with no one-level-deep references.	3 / 5
	Total	15 / 20 Passed

Description

87%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 strong description that clearly states a niche domain, lists concrete coverage areas, and provides an explicit, exclusive trigger. It is slightly limited on trigger-term synonym coverage but otherwise well-scoped and unambiguous.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete sub-domains (中英文空格, 全半角标点, 术语保留, 链接格式, 中文文案排版指北约定) rather than vague abstractions, though framed as topics rather than performed actions; minor gaps keep it below a 5.	4 / 5
Completeness	It explicitly answers both 'what' (中文文档排版参考 with listed conventions) and 'when' (仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发) with a concrete trigger phrase.	5 / 5
Trigger Term Quality	It names natural terms a user would say when writing Chinese docs (中文文档, 排版, 中英文空格) plus an explicit /chinese-documentation trigger, but omits several common synonyms and variations that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	The narrow Chinese-typography niche combined with an explicit slash-command trigger and an explicit instruction not to auto-trigger from context yields minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

75%

Warnings & errors only

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

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/chinese-documentation/SKILL.md
Commit: c68725b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.