Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/updating-noridocs
Use this when you have finished making code changes and you are ready to update the documentation based on those changes.
Passed 16 of 24 test cases with the skill, and 12 of 24 without it.
and 3 more in the full report
7 fixed10 passed either way6 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I've completed a major update to our caching layer in `@/src/cache` to handle distributed locks and added retry logic for cluster failures. Please update all relevant codebase documentation files to account for this update.
| Checked | Without skill | With skill |
|---|---|---|
| Dispatches the nori-change-documenter subagent. | Missed | Passed |
| Refrains from performing direct edits on docs.md files. | Passed | Passed |
The instructions your model reads when the skill loads.
Noridocs are docs.md files throughout the codebase that document each folder's purpose, architecture, and implementation. Update them after code changes using the nori-change-documenter subagent.
Core principle: Provide context → Dispatch subagent → Verify updates.
Announce at start: "I'm using the Updating Noridocs skill to update documentation."
Prepare information for the subagent:
Use Task tool with nori-change-documenter type:
Task(subagent_type: nori-change-documenter)
In the prompt, provide:
Check that documentation was updated:
test cases passed, vs 12 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.