CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-pdf-reformat-pipeline

Modernize a legacy PDF: structural extraction → natural-language rewrite of problem pages → audit summary → re-merge into the final PDF.

56

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/exp/meta-pdf-reformat-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is lean and well-structured for a meta-skill, but its fallback guidance stays at a high level (named skills without executable steps) and the workflow lacks explicit pass/fail validation checkpoints for the destructive re-merge step.

Suggestions

Add concrete invocation detail for the fallback (e.g. example task strings or parameters for each sub-skill) so Claude can execute it without inferring the steps.

Insert an explicit validation gate after the audit step — e.g. 'Only proceed to merge once the reviewer confirms the audit summary' — with a fix-and-retry loop.

Tighten the minor redundancy between the intro step list and the fallback step list, or differentiate them more clearly (e.g. fallback = manual invocation commands).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept padding, but the fallback re-lists the extract→rewrite→audit→merge sequence already stated in the intro, a minor redundancy that could be trimmed — fitting anchor 4 rather than a clean 5.

4 / 5

Actionability

The fallback names the concrete skill chain (pdf-toolkit → nano-pdf → summarize → pdf-toolkit) in order, but provides no executable commands, parameters, or per-step invocation detail — matching anchor 3's 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The four-step sequence is clearly ordered and an audit/diff-summary checkpoint is named ('before the merge is finalized'), but validation is a soft human-review summary rather than an explicit pass/fail gate with error-recovery feedback loops, capping this at anchor 3 for a destructive re-merge operation.

3 / 5

Progressive Disclosure

At well under 50 lines with no external references needed and no bundle files present, the body's organized sections (title + Fallback heading) satisfy the simple-skill exception that allows progressive disclosure to score 5.

5 / 5

Total

15

/

20

Passed

Description

63%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 and outlines a comprehensive four-step pipeline, but it lacks an explicit 'Use when...' trigger clause and broader keyword coverage, which together cap completeness and trigger-term quality at 3.

Suggestions

Append a 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when modernizing legacy PDFs, scanned manuals, or legal documents, or when the user asks to reformat/rewrite a PDF').

Add common synonyms and the file extension ("reformat", "convert", ".pdf") to broaden natural keyword coverage.

Keep the concrete four-action list as-is; it already anchors specificity and distinctiveness well.

DimensionReasoningScore

Specificity

Lists four concrete pipeline actions — "structural extraction", "natural-language rewrite of problem pages", "audit summary", "re-merge into the final PDF" — giving comprehensive coverage of the full modernization workflow, matching the anchor-5 example of multiple specific concrete actions.

5 / 5

Completeness

Clearly answers 'what' (the four-stage pipeline) but offers no explicit 'Use when...' trigger guidance — 'when' is only weakly implied via 'legacy PDF'/'modernize', which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some natural terms ("Modernize a legacy PDF", "rewrite") but misses common variations/synonyms and file extensions (no "reformat", "convert", or ".pdf"), fitting the anchor-3 'some relevant keywords but missing variations' rather than anchor-4's broad coverage.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (legacy-PDF modernization via extract→rewrite→audit→merge) that is mostly distinct, but without an explicit trigger clause it carries minor overlap risk with general PDF skills, landing at anchor 4 rather than 5.

4 / 5

Total

15

/

20

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
TokenRhythm/opensquilla
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.