CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biorxiv-database

Search, retrieve metadata, and download PDFs for bioRxiv preprints; use when you need to discover biology preprints by keywords/authors/date ranges and programmatically fetch their details.

Quality

73%

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/biorxiv-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 sections are genuinely useful — accurate, executable examples that match the bundled script and a well-signaled one-level-deep API reference. The score is dragged down by substantial generic boilerplate (about half the document) and a broken validation example where the --help smoke test and expected output format do not match the script's actual behavior.

Suggestions

Delete or drastically compress the generic boilerplate sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling), which contain no bioRxiv-specific information.

Fix the Quick Validation section: replace "python scripts/biorxiv_search.py --help" with a working smoke test such as "python scripts/biorxiv_search.py CRISPR 7", and remove the fabricated expected-output block that the script never produces.

Ground the workflow in concrete commands — e.g. search, verify result count and DOI fields, then download PDFs and check the files are non-empty — instead of abstract directives like "select the documented execution path".

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate — "Do not use this skill when the required source data, identifiers, files, or credentials are missing", "Keep the output safe, reproducible, and within the documented scope at all times", "Select the documented execution path and prefer the simplest supported command" — that teaches nothing specific to bioRxiv and pads the document. This matches anchor 2 ("several unnecessary explanations or padded sections"); it is not 3 because the padding is substantial rather than occasional, and not 1 because the core sections (When to Use, Example Usage, Implementation Details) are concrete and useful.

2 / 5

Actionability

The Python and CLI examples are executable and match the actual bundled script ("searcher.search_by_keywords([\"CRISPR\"], days_back=30)", "searcher.download_pdf(first[\"doi\"], out_path)", "python scripts/biorxiv_search.py \"CRISPR\" 30"), with an install command included. It stops short of 5 because the "Quick Validation" path "python scripts/biorxiv_search.py --help" is broken (the script has no argument parsing and would treat --help as a search keyword) and the "Expected output format" block ("Result file: biorxiv_database_result.md") describes output the script does not produce.

4 / 5

Workflow Clarity

A sequence is present ("Validate the request... Select the documented execution path... Produce the expected output... Run a final validation pass"), but the steps are abstract and the only concrete checkpoint (the --help smoke test) is incorrect, matching anchor 3's "sequence present but checkpoints missing or implicit". It is not 2 because the end-to-end Python example does show a concrete ordered flow (search, inspect metadata, download PDF), and not 4 because no working validation command is actually given.

3 / 5

Progressive Disclosure

Structure is good: the body is organized into clear sections, the API detail is appropriately split into a real one-level-deep reference ("See references/api_reference.md for endpoint/field details and response formats" — the file exists and contains exactly that), and the script path scripts/biorxiv_search.py is real and correctly referenced. It falls short of 5 because the overview itself is diluted by inline boilerplate sections (Output Contract, Validation and Safety Rules, Failure Handling) that add navigational noise rather than pointing to purposeful content.

4 / 5

Total

13

/

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 description that clearly and explicitly states both capabilities and trigger conditions with concrete, natural keywords for the bioRxiv domain. The main flaw is the second-person "use when you need to..." phrasing, which violates the third-person voice guideline and costs a specificity point; the trailing "programmatically fetch their details" is also slightly redundant with "retrieve metadata".

Suggestions

Rewrite in third-person/imperative voice, e.g. "use when the task requires discovering biology preprints...", to remove the second-person "you need" phrasing.

Add a few more natural trigger synonyms such as "preprints", "pre-prints", "papers", or "biorxiv.org" to broaden keyword coverage.

Tighten the tail: replace "programmatically fetch their details" (which duplicates "retrieve metadata") with a distinct capability such as "download full-text PDFs by DOI".

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Search, retrieve metadata, and download PDFs for bioRxiv preprints", "discover biology preprints by keywords/authors/date ranges"), matching the several-specific-actions level; however, the second-person phrasing "use when you need to discover... and programmatically fetch their details" triggers the voice penalty, reducing it from 4 to 3. It is above anchor 2 because the domain and actions are named specifically, not generic.

3 / 5

Completeness

It explicitly answers both "what" ("Search, retrieve metadata, and download PDFs for bioRxiv preprints") and "when" ("use when you need to discover biology preprints by keywords/authors/date ranges and programmatically fetch their details") with concrete trigger phrases, matching the anchor-5 example pattern. Anchor 4 would require the "when" clause to be less explicit or specific, which is not the case here.

5 / 5

Trigger Term Quality

Good natural keyword coverage including "bioRxiv preprints", "biology preprints", "PDFs", "keywords", "authors", and "date ranges" — terms users would naturally say. It falls short of anchor 5 because common variations like "pre-print", "papers", "biorxiv.org", or extension forms are missing, and it is clearly above anchor 3's level of missing common variations.

4 / 5

Distinctiveness Conflict Risk

"bioRxiv preprints" carves out a clear niche with distinct triggers (bioRxiv, biology preprints, PDF download by DOI), with minimal overlap risk against generic literature-search skills. It matches anchor 5's "clear niche with distinct triggers" and is well above the "somewhat specific but could still overlap" anchor 3.

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/biorxiv-database/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.