Verify technical nonfiction manuscripts for runnable accuracy, including commands, configuration, code snippets, links, version drift, screenshots, prerequisites, security warnings, expected outputs, and reproducibility.
NewMaintained
Automatic
◆Doc Ops pack
Last verified 8/16/2026
What it changes
Passed 17 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill77%
Checks it passed that the model alone missed
Includes an Item column in the evidence table.
Includes a Verification method column in the evidence table.
Includes a dedicated section for suggested beta-reader or expert-review checks.
and 1 more in the full report
2 fixed15 passed either way3 still failing2 broke
Pass-rate lift
0 pp
Tokens
+13%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Audit this 2-page tutorial draft on setting up Redis Sentinel. Produce the full required technical manuscript verification response covering all required output sections.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes a dedicated section for items requiring current primary-source verification.
Missed
Passed
Includes a dedicated section for suggested beta-reader or expert-review checks.
Missed
Passed
case-20 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md88 linessingle file
Technical Manuscript Verification
Core Lens
Technical nonfiction must work in the reader's environment, not just in the author's memory. Verification checks whether commands run, configs are coherent, screenshots match text, links still resolve, safety boundaries are clear, and the reader has enough context to recover from failure.