CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pdf-accessibility-checker

Test PDF accessibility (PDF/UA conformance) - tagged-PDF structure (StructTreeRoot), alternative text on images (Alt), reading-order, language metadata (Lang), document title, heading hierarchy. Use veraPDF / PAC (PDF Accessibility Checker) / pdfix / Adobe Acrobat Pro headless; map each finding back to WCAG 2.1 PDF Techniques (PDF1 - PDF23). Use when a product ships customer-facing PDFs into a context that mandates PDF/UA - US Section 508, EU Directive 2016/2102, or a public-sector tender - and each file must be proven tagged before release.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A focused, executable CI-oriented skill: lean code-first steps with genuinely non-obvious gotcha comments, explicit validation checkpoints, and a working PDF/UA conformance gate. Organization is clear and references are one level deep with no bundle-file bloat.

DimensionReasoningScore

Conciseness

Lean, step-structured body where prose comments earn their place only for non-obvious gotchas (pikepdf returning an Object wrapper so 'is True' fails, the nested /K walk, jq -e exit-status behavior); not a 2 because it does not pad with concepts Claude already knows.

3 / 3

Actionability

Provides copy-paste-ready, executable guidance throughout: real curl/unzip/install commands, complete pikepdf test functions, and a CI YAML gate; not a 2 because the code is complete rather than pseudocode and includes specific verapdf/jq invocations.

3 / 3

Workflow Clarity

Ten numbered steps are clearly sequenced with explicit validation checkpoints (exit codes 0/1/2, 'assert failed == 0', CI gate '|| exit 1') and a failure-driven feedback loop; not a 2 because validation is explicit rather than implicit for a batch CI operation.

3 / 3

Progressive Disclosure

Well-organized into clear sections with one-level-deep reference-style links ([WCAG 2.1 spec], [pikepdf objects], [WCAG PDF1], [jq manual]) defined at the bottom and a tidy References list; not a 2 because navigation is clean with no nested/deep references, and the self-contained inline content is appropriate for a focused CI-gate skill with no bundle files.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that uses third-person voice, lists concrete accessibility checks, and pairs a clear 'what' with an explicit regulatory 'Use when' trigger. Trigger terms map naturally to how a compliance-focused user would phrase the request.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('tagged-PDF structure (StructTreeRoot), alternative text on images (Alt), reading-order, language metadata (Lang), document title, heading hierarchy'), matching the score-3 anchor; not a 2 because the actions are comprehensive and specific rather than partial.

3 / 3

Completeness

Explicitly answers what ('Test PDF accessibility (PDF/UA conformance)...') and when ('Use when a product ships customer-facing PDFs into a context that mandates PDF/UA...'), matching the score-3 anchor with an explicit 'Use when' trigger; not a 2 because the when clause is explicit rather than implied.

3 / 3

Trigger Term Quality

Covers natural terms a compliance user would say ('PDF accessibility', 'PDF/UA conformance', 'tagged-PDF', 'WCAG 2.1 PDF Techniques', 'Section 508', 'EU Directive 2016/2102'), matching the good-coverage anchor; not a 2 because it includes common variations beyond a single keyword.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (PDF/UA accessibility conformance) with distinct regulatory triggers, unlikely to fire for unrelated skills; not a 2 because the scope is narrowly bounded to PDF accessibility rather than overlapping with general PDF skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents