Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yaacovcorcos/software-development-documentation
Create source-backed software documentation for codebases, architecture, setup, testing, debugging, deployment, APIs, security, and operations.
Passed 8 of 17 test cases with the skill, and 5 of 17 without it.
and 5 more in the full report
6 fixed4 passed either way10 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Generate the metadata file for our newly created project wiki at `repo-wiki/.wiki-meta.json` after running a full doc generation pass on commit `a1b2c3d` of branch `main`.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the commitHash key in .wiki-meta.json. | Missed | Passed |
| Includes the generatedAt timestamp key in .wiki-meta.json. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the user wants to create, update, audit, or organize documentation for a software project: repository wiki, architecture docs, setup guide, contributor guide, testing docs, debugging guide, deployment runbook, API overview, security notes, operational docs, or developer onboarding.
This skill is for software development documentation. For company handbooks, policies, people operations, team rituals, or non-code operating knowledge, prefer a company documentation skill.
Write docs that help a developer or agent safely understand, change, run, test, and operate the system.
Do not turn the work into template theater. Use the structure below as a map, not a cage. Skip sections that are not supported by source evidence. Add sections when the repo makes them necessary.
Ask questions only when a missing answer changes the output location, audience, privacy boundary, or write permission. Otherwise, inspect the repository, make reasonable assumptions, and label uncertainty.
Before writing, inspect the repository enough to understand:
test cases passed, vs 5 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.