CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf-extract-experimental-materials

Extract experimental materials and instrument information from PDFs (or PDF-derived text/Markdown) into three CSV tables; use when a paper/report contains sections like Materials and Methods, Key Resources Table, Reagents, Antibodies, Consumables, Software, Equipment, Instruments, or Reagent Preparation.

Quality

73%

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 ./scientific-skills/Evidence Insight/pdf-extract-experimental-materials/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 domain-specific core (extraction rules, CSV schemas, table-first detection order, dedup/spot-check quality checks) is solid and specific, but it is wrapped in ~60 lines of generic filler, a broken primary script reference, and contradictory duplicate validation instructions. The skill reads as a good extraction spec diluted by template boilerplate.

Suggestions

Delete the generic boilerplate sections ('Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Deterministic Output Rules', 'Completion Checklist', 'When Not to Use') — they restate what Claude already knows and consume roughly a third of the body.

Fix the primary execution path: 'd:\SKILL\project\pdf-extract\scripts\extract_pdf.py' is not in the bundle; either ship the script under scripts/ with a relative path or replace the command with a concrete pdfplumber/OCR snippet, since pdfplumber is already a declared dependency with no example code.

Reconcile the contradictory validation guidance — 'Validation Shortcut' says to run scripts/validate_skill.py while 'Quick Validation' states 'No local script validation step is required for this skill'. Keep one validation step and turn the item spot check into a fix-and-retry loop (re-extract mismatched rows, then re-verify).

DimensionReasoningScore

Conciseness

Roughly a third of the body is generic boilerplate Claude already knows — 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Deterministic Output Rules', 'Completion Checklist' (e.g., 'Validate required inputs before execution and stop early when mandatory fields or files are missing', 'Return a structured deliverable that is directly usable without reformatting'). Several padded, skill-agnostic sections make this noticeably verbose rather than 'mostly efficient', so it sits at anchor 2 rather than 3.

2 / 5

Actionability

Genuinely concrete parts exist (exact CSV schemas, field mapping rules like 'catalog_number = version/release (if explicitly stated)', dedup and spot-check rules), but the primary execution step is broken: 'python d:\SKILL\project\pdf-extract\scripts\extract_pdf.py -i input.pdf -o out.md' references a script absent from the bundle via a hardcoded absolute Windows path, and no executable pdfplumber/OCR code is provided despite listing them as dependencies. This is concrete-but-incomplete guidance with missing key details, matching anchor 3 rather than 4's 'minor gaps'.

3 / 5

Workflow Clarity

The operational sequence is clear: convert PDF to Markdown → table-first region detection → field extraction per rules → write three exact-schema CSVs → deduplicate → 'Perform a spot check of at least three items against the PDF source'. An explicit validation checkpoint exists, so the batch-operation cap at 3 does not apply. It falls short of 5 because there is no fix-and-retry loop after the spot check, and the two validation sections contradict each other ('Run this minimal command first... python scripts/validate_skill.py --help' vs 'No local script validation step is required for this skill').

4 / 5

Progressive Disclosure

Section headers are present and the one real bundle file (scripts/validate_skill.py) is clearly signaled and exists, but the other referenced script (extract_pdf.py) does not exist in the bundle and is reached via a buried absolute path, failing navigation. The trivial stub script plus the contradictory duplicate validation guidance ('Validation Shortcut' vs 'Quick Validation') leaves the structure redundant and harder to navigate than the 'references mostly clear' bar of anchor 4.

3 / 5

Total

12

/

20

Passed

Description

87%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 strong description: third-person, concrete about inputs and outputs, with an explicit 'use when' clause rich in natural domain trigger terms. Its only weaknesses are not enumerating the three output tables and omitting a few synonyms/file extensions.

DimensionReasoningScore

Specificity

Concrete actions are stated ('Extract experimental materials and instrument information... into three CSV tables'), naming inputs (PDFs, PDF-derived text/Markdown) and the deliverable format. It stops short of anchor 5 because the three tables are not enumerated (reagents, instruments, reagent preparation), leaving a gap in coverage of what is actually produced.

4 / 5

Completeness

Explicitly answers both what ('Extract experimental materials and instrument information from PDFs... into three CSV tables') and when ('use when a paper/report contains sections like...') with concrete trigger phrases, matching the anchor-5 pattern. Third person voice is used throughout, so no voice penalty applies.

5 / 5

Trigger Term Quality

Strong natural domain keywords: 'Materials and Methods, Key Resources Table, Reagents, Antibodies, Consumables, Software, Equipment, Instruments, or Reagent Preparation' — phrases a biomedical user would genuinely say. Not anchor 5 because common synonyms and extensions are missing (e.g., '.pdf', 'protocols', 'reagent inventory', 'materials list').

4 / 5

Distinctiveness Conflict Risk

The trigger set is tightly scoped to experimental-materials sections of papers (Key Resources Table, Reagents, Antibodies), a clear niche that a generic PDF-extraction or document skill would not claim. Minor theoretical overlap with generic PDF skills exists, but the 'use when' clause is content-based, not file-type-based, keeping conflict risk minimal.

5 / 5

Total

18

/

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.

Validation — 15 / 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

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/pdf-extract-experimental-materials/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.