CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf

PDF files: create, read, merge, fill, OCR, edit text.

Quality

83%

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

92%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.

A strong, highly operational skill body: exact commands for every operation, a pitfalls section packed with genuine failure modes, explicit verification loops, and clean reference splitting. The only meaningful bloat is the inline venv/bootstrap section in Prerequisites, which mixes environment plumbing and authoring meta-notes into the main body.

DimensionReasoningScore

Conciseness

Dense operational content throughout — Pitfalls bullets like 'NeedAppearances' and 'Rotated stamp text extraction' carry non-obvious failure modes, and the Quick Reference table is maximally token-efficient. However, the ~25-line venv bootstrap block with justification prose ('it survives container restarts, never touches the Hermes install itself') and authoring notes ('Use this exact block in every document skill') could be trimmed or moved out of the main body.

4 / 5

Actionability

Every helper has an exact, copy-paste-ready CLI line with flags ('pdf_split.py doc.pdf --pages 1-3,7 -o part.pdf [--rotate 90]'), the Quick Reference table maps each task to a command, and even external fallbacks come with full invocations (e.g. the Ghostscript 'gs -dPDFA=2 ...' command). Common cases are covered with no pseudocode.

5 / 5

Workflow Clarity

The 9-step Procedure opens with 'Inspect first' and closes with 'Verify', the Verification section gives explicit per-operation checks ('After form fill: pdf_read.py filled.pdf --fields and compare values'), and the form-design loop has a clear feedback cycle ('Iterate spec → lint → overlay until clean'). Destructive/batch operations (encrypt, flatten) all have validation steps, so no cap applies.

5 / 5

Progressive Disclosure

The body is a genuine overview with well-signaled, one-level-deep references that all exist on disk ('references/ocr-extraction.md', 'references/nano-pdf-editing.md', 'references/forms.md'), and all 15 referenced scripts/ files are present. Bulk detail for OCR, forms, and nano-pdf editing is appropriately split out of SKILL.md, and navigation via the command table and labeled sections is easy.

5 / 5

Total

19

/

20

Passed

Description

70%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.

A terse, domain-scoped description that lists six concrete PDF actions but omits any 'when to use' trigger clause and uses bare verbs without objects or synonyms (.pdf, PDFs, forms). Its clearest improvement is adding an explicit 'Use when...' clause, which is what holds completeness at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions PDFs, .pdf files, forms, or needs text/table extraction, merging, or OCR of scanned documents.'

Attach objects to the terse verbs for concreteness: 'fill forms' instead of 'fill', and 'extract text and tables' instead of 'read'.

Include natural synonyms and the file extension — 'PDFs', '.pdf', 'forms' — to broaden trigger-term coverage toward the top anchor.

DimensionReasoningScore

Specificity

Names the domain plus six concrete actions ('create, read, merge, fill, OCR, edit text'), which exceeds the several-actions anchor, but the verbs lack objects ('fill' not 'fill forms', 'read' not 'extract text and tables') and omit capabilities like encrypt, watermark, and metadata — falling between the 4 and 5 anchors rather than achieving comprehensive coverage.

4 / 5

Completeness

The 'what' is clear and concrete (six named actions on PDF files), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains good natural keywords users would actually say ('PDF files', 'OCR', 'merge', 'edit text'), matching 'good keyword coverage', but misses common variations and synonyms such as 'PDFs', the '.pdf' extension, 'forms', and 'extract text' — short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to 'PDF files' with format-specific actions (OCR, form filling, merging), giving a clear niche with minimal conflict risk against office-document or generic file skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

skills/productivity/pdf/SKILL.md

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.