Use this skill to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code. Activate when you have specific pages to check for factual accuracy -- not when sweeping a whole corpus (use docs-corpus-audit for that) and not when triaging a PR diff (use docs-sync for that). Trigger nouns: "is this doc accurate", "verify the page against the code", "fact-check this section", "any claims that drifted from source", "fact-checking", "grounding audit", "drift hunt",
SkillScore50Maintained
Automatic
◆Doc Ops pack
Last verified 7/27/2026
What it changes
Passed 9 of 17 test cases with the skill, and 0 of 17 without it.
Without skill0%
With skill50%
11 fixed0 passed either way11 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+28%
Agent turns
0%
Response time
-67%
Model gemini-3.6-flashMeasured 7/27/2026v111 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md165 lines5 filesincludes scripts
docs-grounding-verifier
CLAIM-LEVEL grounding verification. Adapts the RAGAS faithfulness-eval
pattern (proven in RAG literature) to docs/code instead of generated-
answers/retrieved-context. Source code is the ground truth; docs
paragraphs are the candidate text under audit.
python-architect personadoc-writer persona
Sibling contract
This skill is a SIBLING of docs-corpus-audit and docs-sync. The
boundary is load-bearing:
Skill
Trigger
Scope
Granularity
docs-sync
PR opened/synchronized
PR diff only
Page-level
docs-corpus-audit
Maintainer asks for whole-corpus pass
Entire corpus
Page-level
docs-grounding-verifier
Verify specific pages factually
1..N pages
CLAIM-level
docs-corpus-audit invokes this skill in its VERIFY phase on the
highest-risk pages of each wave. docs-sync can invoke it on the
specific pages in a PR diff. The skill is also runnable standalone.
When to activate
Maintainer says "verify against the code".
An audit wave wants per-claim grounding scores for its highest-risk pages.
A PR review wants to confirm that prose changes are not just plausible
but actually consistent with the implementation.
A "fact-check" or "grounding" or "drift hunt" request.
When NOT to activate
Whole-corpus sweep with no specific page list -> use docs-corpus-audit.
PR review with mixed code+docs diff -> use docs-sync.
Editorial / tone review -> use editorial-owner persona directly.