Install any skill in seconds. Free to start, no credit card required.
Get Started Free →huangjia2019/doc-writing
Generate API documentation from a route manifest.
Passed 20 of 21 test cases with the skill, and 7 of 21 without it.
and 19 more in the full report
14 fixed7 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When documenting routes extracted from `src/controllers/inventory.js`, what is the exact relative destination path for the resulting markdown file?
| Checked | Without skill | With skill |
|---|---|---|
| The destination path is docs/inventory-api.md. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate structured API documentation from a route manifest.
You will receive a route manifest (JSON array) from the previous pipeline stage. Each entry contains: method, path, file, line, middleware, type.
For each route in the manifest, read the source file to understand:
Use the template at templates/endpoint-doc.md for each route group.
Group routes by their source file (e.g., all product routes together).
Write one markdown file per route group to the docs/ directory:
docs/products-api.mddocs/categories-api.mdReturn a manifest of generated documentation files:
{
"files_generated": ["docs/products-api.md", "docs/categories-api.md"],
"routes_documented": 8,
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.