CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-backends

Change or diagnose Xberg PDF extraction, native/Pdfium backend selection, PDF rendering sessions, encrypted documents, OCR fallback, or backend-specific capability gaps. Load for PDF engine work, not generic image OCR.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is a dense, well-organized reference of backend invariants that assumes competence and wastes few tokens. It would benefit from a small executable example or command sequence to lift actionability and make the verification steps more copy-paste ready.

Suggestions

Add a short code or CLI snippet showing how to select Pdfium and how a failing-without-feature error surfaces, to push actionability toward fully executable.

Render the Verification section as an explicit numbered sequence (select backend -> assert invariant -> run test-corpus -> aggregate benchmarks) so the validation workflow and feedback loop are unmistakable.

DimensionReasoningScore

Conciseness

The body is lean and codebase-specific (xberg_native_pdf, PdfRenderSession, engine lock, PDFIUM_DYNAMIC_LIB_PATH) with no generic PDF explanations; every line carries a non-obvious invariant or pointer.

5 / 5

Actionability

Concrete identifiers, file paths, Cargo feature names, and env vars make the guidance actionable for codebase work, but there are no executable code snippets or commands showing how to select or exercise a backend.

4 / 5

Workflow Clarity

Content is logically organized into Native, Pdfium, and a Verification section that supplies explicit validation criteria (XBERG_REQUIRE_PDFIUM, test-corpus, benchmark aggregation), though it is a reference rather than a strict numbered workflow with feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, the skill is self-contained and well-sectioned; the only external pointer ('test-corpus skill') is one level deep and clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

The description is specific, complete, and well-bounded, naming concrete backend capabilities and giving explicit load guidance with a clear negative boundary. Its only gap is trigger-term breadth, where synonyms and file extensions would round out coverage.

Suggestions

Add natural synonyms and the file extension (e.g. 'PDFs', '.pdf') so trigger_term_quality reaches full coverage.

Optionally surface one or two more user-facing trigger phrases ('when the user mentions encrypted PDFs or OCR fallback') to reinforce the 'when' clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Change or diagnose Xberg PDF extraction, native/Pdfium backend selection, PDF rendering sessions, encrypted documents, OCR fallback, or backend-specific capability gaps' — giving comprehensive coverage of the capability surface.

5 / 5

Completeness

Explicitly states what the skill does (the 'Change or diagnose...' action list) and when to load it via the equivalent trigger clause 'Load for PDF engine work, not generic image OCR'.

5 / 5

Trigger Term Quality

Natural terms like 'PDF extraction', 'OCR', 'encrypted documents', and 'backend' are present, but synonyms (PDFs, .pdf) and a few common variations are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A tight Xberg-PDF-backends niche with an explicit negative boundary ('not generic image OCR') keeps conflict with adjacent skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xberg-io/xberg
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.