CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-screening-fulltext

Screen full-text papers against inclusion/exclusion criteria, with optional PubMed metadata check using PMID. Use when the user needs to evaluate a paper for a meta-analysis.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/meta-screening-fulltext/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 core Workflow and Quality Rules sections are genuinely useful — clear sequencing, scenario branching, a defined JSON output schema, and standard exclusion terminology. However, the file is padded with multiple boilerplate sections, and every referenced bundle file (both scripts and the screening prompts) is missing from the package, so the skill cannot be executed as written and its navigation structure is broken.

Suggestions

Remove the auto-generated filler sections ('When to Use' bullets beyond the first, 'Key Features', 'Implementation Details', and the redundant 'Input Validation' block), keeping only the Workflow, Quality Rules, Helper Scripts, and Error Handling sections to roughly halve token cost.

Ship the referenced bundle files (scripts/extract_pdf.py, scripts/query_pubmed.py, references/screening_prompts.md) or delete every mention of them; as written, Claude will attempt to run nonexistent scripts at step 2 and fail.

Fix the dangling 'Helper Scripts' section (a colon leading to nothing) by giving the actual extract_pdf.py usage command and folding PDF extraction into the numbered Workflow as an explicit pre-screening step, and replace the time-stamped 'Example Usage' path ('20260316/scientific-skills/...') with a portable one.

DimensionReasoningScore

Conciseness

Several sections are auto-generated boilerplate padding: the 'When to Use' list includes generic filler like 'Use this skill when a data analytics task needs a packaged method instead of a generic answer' and a lowercased near-duplicate of the description; 'Key Features' restates the description; 'Implementation Details' offers vague filler like 'Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable'; and 'Input Validation' duplicates 'Error Handling'. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than anchor 3's 'some unnecessary explanation', since the padding spans multiple whole sections.

2 / 5

Actionability

There is concrete guidance — a runnable-style command ('python scripts/query_pubmed.py "<input_pmid>"'), named inputs, two explicit screening scenarios, and a defined JSON output schema with enumerated exclusion categories — but it is incomplete: it depends on scripts/extract_pdf.py, scripts/query_pubmed.py, and references/screening_prompts.md, none of which exist in the bundle, and the 'Helper Scripts' section for extract_pdf.py dangles with a colon and no usage. This lands on anchor 3 ('some concrete guidance but incomplete; missing key details'), not anchor 4, because key execution details cannot actually be run as written.

3 / 5

Workflow Clarity

The '## Workflow' section gives a clear 1-4 sequence (analyze inputs → optional PubMed check → screen under two explicit scenarios → format output) with an output-format checkpoint ('Ensure the output is a JSON object...') and a substantive Error Handling section covering missing inputs, out-of-scope requests, and execution failure. It stays at anchor 4 rather than 5 because there is no explicit verify-and-retry loop (e.g., confirming retrieved PubMed metadata actually matches the paper) and the PDF-extraction step is orphaned in a broken separate section instead of being sequenced into the workflow.

4 / 5

Progressive Disclosure

The bundle contains no references/, scripts/, or assets/ directories at all, yet the body repeatedly directs Claude to 'scripts/extract_pdf.py', 'scripts/query_pubmed.py', 'references/screening_prompts.md', and claims 'Reference material available in references/' — every external navigation path is broken. Combined with inlined boilerplate that should not be in SKILL.md at all, this matches anchor 2 ('minimal structure; references are buried/broken') rather than anchor 3, where references are at least present and usable.

2 / 5

Total

11

/

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 solid, concise description that explicitly states both what the skill does and when to use it, with good domain-specific trigger terms. Its main gaps are limited action coverage (only two actions listed) and a single, narrow use-when trigger that omits adjacent phrasings like 'systematic review'.

DimensionReasoningScore

Specificity

The description names the domain (paper screening for meta-analysis) and exactly two concrete actions — 'Screen full-text papers against inclusion/exclusion criteria' and 'optional PubMed metadata check using PMID'. It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'): other capabilities documented in the body (PDF text extraction, structured JSON output with standard exclusion categories) are absent, so it does not reach anchor 4's 'several specific actions'.

3 / 5

Completeness

Both parts are explicitly present: 'what' ('Screen full-text papers against inclusion/exclusion criteria, with optional PubMed metadata check using PMID') and 'when' ('Use when the user needs to evaluate a paper for a meta-analysis'). The 'when' clause is a single narrow trigger, less expansive than anchor 5's multiple concrete trigger phrases, so it sits at anchor 4 ('both present; when could be more explicit or specific').

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'full-text papers', 'inclusion/exclusion criteria', 'PubMed', 'PMID', 'meta-analysis', 'evaluate a paper' — phrases a systematic-review researcher would actually say. It misses common variations like 'systematic review', 'literature screening', or 'study eligibility', which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The PMID/PubMed + meta-analysis framing carves a fairly clear niche with distinct triggers, but there is minor overlap risk with closely related skills such as literature-search, abstract-screening, or general paper-analysis skills, matching anchor 4 ('mostly distinct; minor overlap risk').

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/meta-screening-fulltext/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.