Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/docs-corpus-audit
Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified
Passed 18 of 21 test cases with the skill, and 10 of 21 without it.
and 9 more in the full report
9 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Once all waves and alignment loops finish, which persona is responsible for synthesizing the overall findings into the final PR summary comment?
| Checked | Without skill | With skill |
|---|---|---|
| assigns the PR summary synthesis to the cdo persona | Missed | Passed |
The instructions your model reads when the skill loads.
The docs corpus drifts silently between releases. docs-sync catches
drift introduced by individual PRs at PR-open time. This skill catches
the accumulated drift that slips past per-PR review -- stale flag
names, dead nav links from past IA reshuffles, deprecation banners
that outlived their version targets, factual claims whose source-side
truth has moved.
The pattern is A1 PANEL + WAVE EXECUTION + S7 DETERMINISTIC TOOL BRIDGE + A8 ALIGNMENT LOOP + A9 SUPERVISED EXECUTION. The corpus is split into disjoint page scopes; one verifier subagent owns each scope; agents extract factual claims, S7-verify against source, apply surgical fixes inline. The orchestrator then runs an alignment-loop pass to re-verify that applied edits actually ground out true.
This skill is ADVISORY but ACTIONABLE: agents apply edits inline on a working branch. The orchestrator is the sole writer to git -- stages, commits, pushes. Maintainer reviews the resulting PR.
These two skills share substrate. Be explicit:
| Shared resource | Owner | Both use |
|---|---|---|
.apm/docs-index.yml (corpus map) | docs-sync | yes |
| doc-writer persona | shared | yes (per-page edits) |
| python-architect persona | shared | yes (S7 verification) |
| editorial-owner persona | shared | optional (voice pass at scale) |
| cdo persona | shared | yes (final synthesis) |
assets/panelist-return-schema.json | docs-sync (mirrored) | yes |
Trigger boundary (avoid DISPATCH COLLISION):
docs-sync triggers on a PR event ("PR opened/synchronized",
source-diff-driven).docs-corpus-audit triggers on a maintainer ask for a
WHOLE-CORPUS pass ("audit the corpus", "reground", "pre-release
sweep") -- no PR required, no diff required, the whole corpustest cases passed, vs 10 / 21 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.