CtrlK
BlogDocsLog inGet started
Tessl Logo

nano-pdf

Edit PDFs with natural-language instructions using the nano-pdf CLI.

73

2.61x
Quality

66%

Does it follow best practices?

Impact

81%

2.61x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/nano-pdf/SKILL.md

The canonical home for this skill is nano-pdf in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 model of brevity with a copy-paste-ready command and a sensible sanity-check note, scoring highly on conciseness and progressive disclosure. Its main weakness is workflow clarity: a destructive edit with ambiguous page numbering and no explicit validation feedback loop keeps it capped at 3.

Suggestions

Resolve the page-number ambiguity by stating the actual default and giving a single deterministic way to confirm it (e.g., "page 1 is the first page; verify with `nano-pdf pages deck.pdf`") instead of trial-and-error.

Add an explicit validate-fix-retry loop, e.g. after editing, run a quick check and if the output is wrong, re-run with the corrected page index before declaring success.

Show the output destination or an example of confirming the edit (e.g., how to inspect the changed page) so the workflow has a concrete verification step.

DimensionReasoningScore

Conciseness

The body is extremely lean — a single one-line example plus two terse notes — with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor where every token earns its place.

5 / 5

Actionability

A concrete, executable `nano-pdf edit` command with realistic arguments is provided, but it covers only the single common case and lacks variants (e.g., multi-page, output flags), placing it at mostly-executable with minor gaps.

4 / 5

Workflow Clarity

The destructive edit workflow has a single step and a sanity-check note, but page-number ambiguity ("0-based or 1-based ... retry with the other") introduces guesswork and there is no explicit validate-fix-retry feedback loop, so the destructive-operation cap holds at 3.

3 / 5

Progressive Disclosure

This is a short single-purpose skill with no bundle files; its Quick start + Notes sections are well-organized and appropriately self-contained, so the simple-skill exception yields a 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 concise and names a concrete tool and action, but it omits an explicit "Use when..." trigger clause and broader trigger synonyms, which caps its completeness and trigger-term quality. Adding when-to-use phrasing and common PDF-related keywords would lift it toward the top anchors.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to modify, fix, or reword content in a PDF without editing the source."

Add natural synonyms and file extensions (e.g., .pdf, forms, document editing) to broaden trigger-term coverage.

Optionally list one or two more concrete capabilities (e.g., rewording text, fixing typos) to move specificity from a 3 toward a 4.

DimensionReasoningScore

Specificity

"Edit PDFs with natural-language instructions" names the PDF domain and one concrete action (editing via NL instructions), but lists no further capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

A clear "what" is stated (edit PDFs via NL CLI) but there is no "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3 for a clear what with missing/weakly-implied when.

3 / 5

Trigger Term Quality

It surfaces "PDFs", "natural-language instructions", and "nano-pdf CLI", but omits common user phrasings like forms, .pdf extension, or document extraction, leaving relevant synonyms missing as in the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

Tying edits to the specific nano-pdf CLI with natural-language instructions carves a fairly distinct niche with only minor overlap risk against generic PDF skills, fitting the mostly-distinct anchor.

4 / 5

Total

13

/

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.

Validation13 / 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
trpc-group/trpc-agent-go
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.