AB chinese-api-docs
API documentation generator with API backend validation for Chinese developers (中文API文档生成器+接口验证API). Generate professional Chinese API docs from code, OpenAPI/Swagger specs, or endpoint descriptions. Features: (1) API backend for doc validation and best practices checking, (2) Executable validate.sh script for CLI validation, (3) Chinese-English terminology mapping (endpoint=接口, payload=请求体), (4) Request/response examples with realistic Chinese data, (5) Error code tables, authentication guides, rate limiting docs. ONLY skill for Chinese API documentation generation with API backend. Use when: writing API docs in Chinese, converting Swagger/OpenAPI to Chinese docs, documenting REST APIs for Chinese developers, generating 接口文档, creating API reference, REST API documentation. Triggers: API documentation generator, API文档, 接口文档生成器, 中文API文档, Swagger中文, OpenAPI文档, API reference Chinese, 接口说明, 开发文档, 技术文档, REST API文档, API文档生成, 接口文档工具, 中文技术文档, 2026 API docs, API doc validation, documentation API.
API documentation generator with API backend validation for Chinese developers (中文API文档生成器+接口验证API).
As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 34): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 72/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1464 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1002: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.