Api docs
Portable agent skills. Point Kit at a project, install a pack, wire Claude Code, Grok Build, and Codex.
npx -y skills add Zwin-ux/kit --skill api-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Document a library or service API with clear usage examples.
SKILL.md
0.6 KB, as published. Nobody here has run it
Instructions
- Find the public surface: exports, routes, or CLI commands.
- Document each public item with:
- Purpose
- Inputs
- Outputs or side effects
- One short example
- Prefer real examples from the codebase.
- Mark unstable or experimental APIs clearly.
- Keep docs next to the code or in the project’s established docs path.
- Do not document private helpers as public API.