Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-w
Passed 16 of 19 test cases with the skill, and 3 of 19 without it.
and 17 more in the full report
14 fixed4 passed either way4 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.
The fan-out panel is processing 4 different pages. How many times are the editorial-owner and oss-growth-hacker tasks spawned during this step?
| Checked | Without skill | With skill |
|---|---|---|
| States they are spawned exactly once across all drafts. | Missed | Passed |
The instructions your model reads when the skill loads.
The docs corpus drifts silently and constantly. This skill catches drift at PR-open time, classifies its impact, and orchestrates a persona panel to produce a patch-ready advisory comment.
The pattern is A1 PANEL + B1 FAN-OUT/SYNTHESIZER + A8 ALIGNMENT LOOP. The classifier is the cost gate (~70% of PRs short-circuit to no-change with ~1 LLM call). When the panel does fan out, every agent reads a bounded context (~10 KB) -- never the full corpus.
This skill is ADVISORY. It does not gate merge, apply verdict labels, or push to the contributor's fork. The orchestrator is the sole writer to the PR: exactly one comment per run (idempotent edit-in-place), plus optional label sweeps.
N/15 for observability.gh write command, post comments, or touch PR state.## Docs sync advisory. Re-runs edit-in-place using gh pr comment --edit-last.docs-sync-confirm label) open from a bot branch in the BASE repo; never pushed to the contributor's fork..apm/docs-index.yml, NOT the corpus itself. The corpus is sampled only by the localizer (which reads the specific candidate pages) and by per-page panelists (which read one page each).apm --help, grep, and python -c commands to verify doc claims, never assert from prose.| Role | Agent | Always active? |
|---|---|---|
| Classifier | doc-analyser inside docs-impact-classifier | Yes (every run) |
| Localizer | docs-impact-localizer | Only on in_place verdict |
| Architect | docs-impact-architect | Only on structural verdict |
| Writer | doc-writer | Per candidate page (fan-out) |
| Verifier | python-architect | Per candidate page (fan-out, S7) |
| Editorial | editorial-owner | Once across all redrafts |
| Growth | oss-growth-hacker | Once across all redrafts |
| Synthesizer | cdo | Once, with ALIGNMENT LOOP up to 3 redrafts |
test cases passed, vs 3 / 19 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.