CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pmc-official-download

Download PubMed/PMC literature using officially permitted PMC methods. Whenever the user wants to download PMC full text, batch-retrieve PMC Open Access Subset articles, save full text corresponding to PMID/PMCID locally, or needs to determine whether a PubMed article can be l...

Quality

77%

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/Evidence Insight/pmc-official-download/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, permitted-channel policy, pitfalls, and command-line guidance are concrete and actionable, with real executable scripts and sensible validation checkpoints. The main weaknesses are a substantial tail of generic boilerplate sections, a duplicated 'Failure Handling' heading, and one orphaned bundled script that the body never mentions.

Suggestions

Delete or heavily condense the generic boilerplate tail (When to Use / When Not to Use / Required Inputs / Output Contract / User Checkpoints / Input Validation / Quick Validation), keeping only skill-specific guidance — and merge the two 'Failure Handling' sections into one.

Document download_pmc.py's actual flags (--pmcid, --identifier, and any others) so the unified entry point is fully usable from the doc alone, and mention or remove the orphaned scripts/download_selected_pmc_pdfs.py.

Move the per-channel selection detail (E-utilities, OAI-PMH, FTP, Cloud Service usage) into a references/ file with example API calls, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The domain-specific sections (workflow, permitted channels, pitfalls, command usage) are lean, but roughly the last quarter of the file is generic template boilerplate ('When to Use', 'When Not to Use', 'Required Inputs', 'Input Validation', 'Quick Validation') with circular filler like 'Use this skill when the user explicitly needs to perform the core task of pmc-official-download', plus a duplicated 'Failure Handling' section. Mostly efficient with unnecessary padding that could be trimmed — the 3 anchor, not the 2 anchor, since there is no concept-explanation padding and the core content is tight.

3 / 5

Actionability

Provides concrete, executable commands referencing real bundled scripts ('python scripts/download_pmc.py --pmcid PMC13011518 --pmcid PMC11656652', 'python scripts/download_pmc_bioc.py') plus verifiable checks (e.g., 'check if the file header starts with %PDF'). Minor gaps: E-utilities, OAI-PMH, and FTP guidance is prose-only with no example calls, and download_pmc.py's flags are shown only via examples rather than documented.

4 / 5

Workflow Clarity

A clear 4-step workflow (confirm needs → determine legality → select method → save with audit trail) with validation checkpoints for batch operations (user confirmation before batch, %PDF header verification, OA Web Service legality check) and an ordered troubleshooting sequence — the batch-validation cap does not apply since checkpoints are present. Not the 5 anchor because validation steps are scattered across 'Practical Pitfalls'/'User Checkpoints' rather than embedded in the workflow, and the duplicated 'Failure Handling' sections create mild ambiguity.

4 / 5

Progressive Disclosure

Well-sectioned body with clear headers and valid one-level-deep script references (both scripts/download_pmc.py and scripts/download_pmc_bioc.py exist and behave as described). Minor gaps: the third bundled script (scripts/download_selected_pmc_pdfs.py) is never mentioned or linked, and all channel-selection detail is inline in a ~230-line file where a channel reference file could offload content — good structure but short of the clean overview-plus-references pattern at 5.

4 / 5

Total

15

/

20

Passed

Description

78%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 good natural trigger phrases and a clear niche, undermined by a hard truncation mid-sentence that cuts off the final trigger scenario. Fixing the truncated text would likely raise specificity and completeness.

Suggestions

Complete the truncated description — the frontmatter ends mid-word at 'whether a PubMed article can be l...'; restore the full final trigger (e.g., 'legally downloaded from PMC') so no trigger phrase is lost.

Add a few natural synonyms users would say, such as 'PDF', 'get the full text', or 'download the article', to broaden trigger coverage.

Consider adding 'full-text XML/JSON' format terms since format preference is a key decision point in the skill's workflow.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('download PMC full text, batch-retrieve PMC Open Access Subset articles, save full text corresponding to PMID/PMCID locally') but the final action is truncated mid-word ('whether a PubMed article can be l...'), leaving a minor coverage gap. It is well above the 3 anchor (more than 1-2 actions) but the truncation prevents comprehensive coverage at 5.

4 / 5

Completeness

It clearly answers 'what' ('Download PubMed/PMC literature using officially permitted PMC methods') and has an explicit 'when' clause ('Whenever the user wants to download PMC full text...'). However, the when-clause is cut off mid-sentence, so the trigger guidance is incomplete rather than fully explicit — between the 4 and 5 anchors, and the truncation holds it to 4.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'download PMC full text', 'batch-retrieve PMC Open Access Subset', 'PMID/PMCID', 'PubMed article' — phrases users would naturally say. Missing common synonyms and format terms like 'PDF', 'get the paper', or '.xml/.json', so it does not reach the comprehensive synonym/extension coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (officially permitted PMC download channels) with distinct triggers (PMC full text, Open Access Subset, PMID/PMCID) and minimal overlap risk with generic search or document skills. This matches the 5 anchor's clear-niche example; the truncation does not affect distinctiveness.

5 / 5

Total

17

/

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/pmc-official-download/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.