CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convert-pdf-to-markdown

This skill should be used when the user asks to "convert a PDF to markdown", "extract text from PDF", or mentions PDF to markdown conversion.

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

88%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 tight, well-structured instruction body for a simple skill: the command, input selection, and output contract are all concrete and unambiguous. The gaps are operational: the referenced conversion script is missing from the bundle, and there is no error-handling or sample-output guidance.

Suggestions

Ship the referenced `scripts/pdf-to-markdown.sh` in the skill bundle (or correct the path) so the sole external reference resolves to a real file.

Add a brief error-handling note: what to do when the script exits non-zero or returns an error field instead of `content`.

Include a minimal example of the returned JSON (`content` + `mimetype`) so the parsing instruction is verifiable.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and assumes Claude's competence: no explanation of what a PDF is, no library primer, no padding — just filename guidance, one command, and the response contract. Every section ("When asking for filename", "Usage", "Response Format") earns its tokens; this matches the anchor for a lean, efficient skill body.

5 / 5

Actionability

The Usage section gives a concrete, copy-paste-ready command (`${CLAUDE_PLUGIN_ROOT}/scripts/pdf-to-markdown.sh <filename.pdf>`) plus explicit filename-selection guidance, which is mostly executable. Not 5 because there is no sample JSON output, no guidance for script failure or non-JSON responses, and the referenced script file is not present in the reviewed bundle (no scripts/ directory), so the command's success cannot be verified.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (under 50 lines, one task) and the single action is unambiguous: determine which PDF to use, run the script, extract the `content` field, display it. The operation is neither destructive nor batch, so no validation checkpoint is required — the simple-skill exception applies cleanly.

5 / 5

Progressive Disclosure

The body is well organized into short, clearly-labeled sections and appropriately splits nothing that belongs elsewhere. Not 5 because the one referenced path — `${CLAUDE_PLUGIN_ROOT}/scripts/pdf-to-markdown.sh` — has no corresponding file in the bundle (the bundle contains only SKILL.md, with no scripts/ directory), leaving the single external reference unresolvable within the skill as shipped.

4 / 5

Total

18

/

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 focused, trigger-oriented description with natural user phrasing and an explicit use-when clause. Its main weakness is that the capability is only expressed through embedded trigger quotes rather than a declarative statement of what the skill does, and trigger coverage lacks synonyms and file extensions.

Suggestions

Lead with a declarative third-person capability statement (e.g., "Converts PDF documents to markdown using the AI26 backoffice conversion service.") so the 'what' is stated independently of the trigger phrases.

Add synonyms and file extensions to the trigger list (e.g., ".pdf", "PDFs", "PDF to md") to reach comprehensive natural-term coverage.

Clarify or narrow the "extract text from PDF" trigger to reduce overlap with general PDF text-extraction skills.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — "convert a PDF to markdown" and "extract text from PDF" — matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because it never independently states what the skill does or how (no mention of producing markdown output via a conversion service), only the trigger phrasing.

3 / 5

Completeness

The "when" is explicit and strong ("This skill should be used when the user asks to..." with concrete trigger phrases), and the "what" is present but only embedded inside those trigger quotes rather than stated as a declarative capability. Not 5 because a first sentence like "Converts PDF files to markdown..." stating the capability on its own terms is absent; not 3 because both what and when are effectively explicit.

4 / 5

Trigger Term Quality

Natural user phrasings are well covered: "convert a PDF to markdown", "extract text from PDF", and "PDF to markdown conversion" are all things a user would actually say. It falls short of 5 because synonyms and file extensions are missing (no ".pdf", "PDFs", or shorthand variants like "pdf to md").

4 / 5

Distinctiveness Conflict Risk

The PDF-to-markdown niche is clear with distinct triggers, but "extract text from PDF" is a broad phrase that could also fire a general PDF-extraction or document skill — a minor overlap risk with closely related skills. Not 5 due to that overlap; well above 3 since the core conversion triggers are unmistakable.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dwmkerr/ai26

Path

plugins/ai26/skills/convert-pdf-to-markdown/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.