CD doc-generator
소스 코드로부터 포괄적이고 정확한 API 문서를 생성합니다. API 문서를 생성하거나 업데이트할 때, OpenAPI 사양을 생성할 때, 또는 사용자가 API 문서, 엔드포인트, 문서를 언급할 때 사용합니다.
Promises to generate API documentation from source code and create OpenAPI specifications. The files contain 348 tokens of code in a single instruction with no scripts. Tests show quality at 69 points against process at 43: the description works, but implementation is incomplete. No critical errors found, though the system didn't flag medium or low issues—suggesting sparse detail. Compatible with all major platforms from Claude to DeepSeek.
Worth installing if you need a foundation for API documentation automation. Expect to refine it for your standards: a C grade means it works but offers no guarantees on edge cases.
소스 코드로부터 포괄적이고 정확한 API 문서를 생성합니다.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 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
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 348 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 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.