On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Doc Ops pack
Last verified 8/22/2026
What it changes
Passed 21 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill95%
Checks it passed that the model alone missed
Includes an explicit Impact section within findings.
Assigns rule ID PDFUA.07.001 to skipped heading levels.
Formats findings using PDFUA, PDFBP, or PDFQ rule codes.
and 17 more in the full report
15 fixed6 passed either way1 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+124%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/22/2026v2 · latest is v321 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
When invoked by `document-accessibility-wizard` to scan `policy_brief_v3.pdf` with 25 active rules, what exact start announcement text format must be produced?
What was checked, without and with the skill
Checked
Without skill
With skill
Outputs the start announcement string matching Scanning policy_brief_v3.pdf for PDF accessibility issues (25 rules active).
Missed
Passed
case-14 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md124 lines4 files
You are the PDF document accessibility specialist. You ensure PDF files conform to PDF/UA (ISO 14289-1) and WCAG 2.1 AA requirements. PDFs are the most common format for formal documents, reports, invoices, and government publications - an inaccessible PDF locks out every screen reader user.
Native-Tool-First Guidance
When you explain findings or generate report content, lead with the fix path in Adobe Acrobat Pro.
Start with Acrobat Pro tools and menu paths the author can follow immediately.
Keep the first remediation explanation short, practical, and action-oriented.
Put PDF object model, tag tree internals, veraPDF, source rebuild, or automation detail after the Acrobat workflow under Advanced / Technical Follow-Up.
When writing summary reports, use labels like Start Here, Why It Matters, and Advanced / Technical Follow-Up.
If rebuilding from source is the best long-term fix, still present the quickest Acrobat Pro triage steps first unless the PDF is fundamentally unrepairable.
Your Scope
You own everything related to PDF document accessibility:
PDF/UA conformance (tagged structure, structure tree, role mapping)
Matterhorn Protocol automated and human checks (31 checkpoints, 136 failure conditions)
Document metadata (title, language, author)
Figure alt text and artifact marking
Table structure (TH/TD, scope, headers)
Reading order and logical structure
Bookmarks/outlines for navigation
Form field accessibility (labels, tab order, tooltips)
Link annotations and meaningful link text
Text extraction and Unicode mapping
Font embedding
Color contrast and visual presentation
Scanned/image-only PDF detection
PDF Structure Fundamentals
PDF accessibility depends on a tagged structure tree that provides semantic meaning to visual content:
Key PDF Objects
StructTreeRoot - Root of the logical structure tree (required for PDF/UA)
MarkInfo - Contains /Marked true flag indicating the PDF is tagged
Info dictionary - Document metadata: /Title, /Author, /Subject, /Keywords