CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-paper-downloader

Download academic papers from open-access sources when the user provides a DOI/arXiv ID or requests a keyword-based paper search, and return the saved PDF path.

Quality

79%

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/research-paper-downloader/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is well structured with executable CLI guidance and a well-documented fallback architecture that matches the shipped script. Its main flaws are a large tail of generic template boilerplate, a Python example whose keyword arguments don't match the actual function signatures, and an orphaned references/apis.md file that is never navigated to from SKILL.md.

Suggestions

Delete or heavily trim the generic boilerplate sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling) — they add ~50 lines of padding that Claude already knows.

Fix the Python example to match the real signatures (download_by_doi(doi, output), search_download(query, max_results, output)) so it is copy-paste ready, and replace the fabricated --help expected output with the actual usage text.

Link references/apis.md from SKILL.md (e.g., under Dependencies or Implementation Details) and move the inline API host details there instead of duplicating them.

DimensionReasoningScore

Conciseness

The core sections (When to Use, Example Usage, Implementation Details) are lean and specific, but roughly 50 of 180 lines are generic template boilerplate ("When Not to Use", "Required Inputs", "Recommended Workflow", "Output Contract", "Validation and Safety Rules", "Failure Handling") that restates what Claude already knows. Mostly efficient, but the padding is more than trimmable trivia, keeping it out of anchor 2's 'noticeably verbose' and below anchor 4.

3 / 5

Actionability

CLI examples use flags that actually exist in scripts/download.py (--doi, --arxiv, --search, --max-results, --output) and the documented functions (download_by_doi, download_by_arxiv, search_download) exist in the script. Not a 5: the Python example passes output_dir= while the real signatures use output=, so it is not copy-paste ready, and the Quick Validation expected output does not match the script's actual --help behavior.

4 / 5

Workflow Clarity

A clear source-priority fallback chain (Semantic Scholar → OpenAlex → Unpaywall → arXiv → PubMed → Crossref) with explicit error-handling expectations (retry per max_retries, then fall back to the next source, then report failures) provides most checkpoints. Minor gaps: the validation section's expected output is fabricated rather than tied to a real check, and the 'Recommended Workflow' section is generic filler rather than skill-specific steps.

4 / 5

Progressive Disclosure

scripts/download.py is clearly and repeatedly signaled, but the bundle's references/apis.md (API endpoints, rate limits, error codes) is never linked from SKILL.md, and its content is partially re-inlined in the Dependencies and Implementation Details sections. This matches the anchor for references present but not clearly signaled; better signaling would earn a 4.

3 / 5

Total

14

/

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: it states what the skill does, when to use it with concrete user-facing triggers (DOI, arXiv ID, keyword search), and the concrete deliverable (saved PDF path) in third person without padding. The only weakness is modest synonym coverage (no "preprint", "article", or "research paper" variants), which slightly limits recall.

DimensionReasoningScore

Specificity

Enumerates several concrete actions — "Download academic papers from open-access sources", "when the user provides a DOI/arXiv ID or requests a keyword-based paper search", and "return the saved PDF path" — matching the anchor for several specific actions with minor gaps. It falls short of a 5, which requires comprehensive multi-action coverage, and exceeds a 3, which covers only 1-2 actions.

4 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: the "what" ("Download academic papers from open-access sources... and return the saved PDF path") and the "when" ("when the user provides a DOI/arXiv ID or requests a keyword-based paper search"). This matches the top anchor better than a 4, where the "when" clause would be less explicit.

5 / 5

Trigger Term Quality

Natural trigger terms users would actually say are present: "DOI", "arXiv ID", "keyword-based paper search", "academic papers", "PDF". A few natural synonyms ("preprint", "article", "research paper") are missing, keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche — open-access academic paper retrieval — with distinct triggers (DOI, arXiv ID, keyword paper search) that are unlikely to fire for unrelated download or search skills, matching the minimal-conflict anchor.

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/research-paper-downloader/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.