Edit PDFs with natural-language instructions using the nano-pdf CLI.
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 81%
↑ 2.61xAgent success when using this skill
Validation for skill structure
Discovery
32%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 too brief and lacks explicit trigger guidance. While it identifies the domain (PDF editing) and tool (nano-pdf CLI), it fails to specify concrete capabilities or provide a 'Use when...' clause, making it difficult for Claude to know when to select this skill over alternatives.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to modify, annotate, or transform PDF files using natural language commands'
List specific editing capabilities such as 'add text, remove pages, merge documents, annotate, redact content'
Include natural trigger terms users might say: 'modify PDF', 'change PDF', 'update PDF file', '.pdf'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PDFs) and mentions a tool (nano-pdf CLI), but 'edit' is a single vague action without listing specific capabilities like extracting text, merging, filling forms, etc. | 2 / 3 |
Completeness | Describes what (edit PDFs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'PDFs' and 'edit' which are relevant, but misses common variations like '.pdf files', 'modify PDF', 'PDF editing', or specific operations users might request. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'nano-pdf CLI' adds some distinctiveness, but 'edit PDFs' is broad enough to potentially conflict with other PDF-related skills that might handle specific editing tasks. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides immediately actionable guidance. The main weakness is the vague handling of the page numbering ambiguity and the lack of a concrete validation step for checking output, which is important for document manipulation tasks.
Suggestions
Clarify the page numbering convention definitively (e.g., 'Pages are 1-based') or provide a command to check which convention is in use
Add a concrete validation step such as 'Open output.pdf and verify the title on page 1 shows Q3 Results' rather than the vague 'sanity-check'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what PDFs are or how CLI tools work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides a complete, copy-paste ready command with a realistic example showing both the syntax and the natural-language instruction format. | 3 / 3 |
Workflow Clarity | This is a simple single-command skill, but the note about page numbering ambiguity and 'sanity-check the output' are vague. A concrete validation step (e.g., 'open the PDF and verify page X') would improve this. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. Clear quick start section with notes; no need for external references given the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 8 / 11 Passed | |
Table of Contents
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.