extract-from-pdfs

This skill should be used when extracting structured data from scientific PDFs for systematic reviews, meta-analyses, or database creation. Use when working with collections of research papers that need to be converted into analyzable datasets with validation metrics.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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 highly actionable, well-sequenced skill body with executable commands and a complete validation workflow. The chief weakness is conciseness, with several sections duplicating content already conveyed elsewhere in the document.

Suggestions

Remove or consolidate the 'Available Scripts' and 'Assets' sections, which restate the scripts and files already introduced in the Workflow Execution and Customization sections.

Move the cost tables and recommended sample sizes in 'Cost Optimization' and 'Quality Assurance' into references/api_reference.md or references/workflow_guide.md to keep SKILL.md lean.

Tighten the 'Core capabilities' bullet list, which overlaps with the 'When to Use This Skill' section, to reduce token redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but includes redundant sections (Available Scripts, Assets, Cost Optimization, Quality Assurance) that restate information already presented in the Workflow and Customization sections, fitting anchor 3.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands with concrete flags for all nine pipeline steps plus setup, with specific file paths and options covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Clearly sequenced six-step pipeline with explicit validation steps (JSON repair, precision/recall metrics) and a seven-step iterative-improvement feedback loop, satisfying the batch-operation validation requirement and matching anchor 5.	5 / 5
Progressive Disclosure	Well-structured overview with clearly signaled one-level-deep references to real files (setup_guide.md, workflow_guide.md, validation_guide.md, api_reference.md), but several sections inline detail (cost tables, sample sizes, script/asset listings) that could be split out, fitting anchor 4.	4 / 5
	Total	17 / 20 Passed

Description

82%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, specific description with explicit 'what' and 'when' guidance and a well-defined niche. The main weakness is second-person voice, which reduces the specificity score per the rubric's voice rule.

Dimension	Reasoning	Score
Specificity	Names the domain plus concrete actions (extract structured data, build analyzable datasets, validation metrics), but uses second-person voice ('This skill should be used', 'Use when working with'), triggering the required 1-point specificity reduction from anchor 4 to 3.	3 / 5
Completeness	Explicitly answers both what (extract structured data, database creation, validation metrics) and when ('Use when working with collections of research papers that need to be converted into analyzable datasets') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('scientific PDFs', 'systematic reviews', 'meta-analyses', 'research papers', 'datasets') that users would plausibly say, aligning with anchor 4 though missing some synonym and file-extension variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, distinct niche (structured data extraction from scientific PDFs for systematic reviews/meta-analyses with validation metrics) with minimal overlap risk against other skills, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: brunoasm/my_claude_skills
Path: extract_from_pdfs/SKILL.md
Commit: 5bdff99

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.