CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biorxiv-database

Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.

Quality

74%

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

Quality

Content

50%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 content is highly actionable for the common cases, with concrete CLI examples, a documented output schema, and a Python API section, but it is roughly twice as long as needed due to duplicated example sections and an inlined test-output dump. Batch workflows lack validation loops, and the promised reference file is absent from the bundle while reference-worthy material is inlined in SKILL.md.

Suggestions

Move the test-suite expected output, the full JSON output schema, and the category list into references/ files, keeping SKILL.md focused on quick-start usage and the Python API.

Cut the duplicated CLI examples in 'Common Usage Patterns' and 'Advanced Features' — keep one representative example per search mode and consolidate the rest behind the reference file.

Add validation to the batch download workflows: check the return value of download_pdf and result_count, skip-and-report failures, and verify outputs before proceeding.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: the Testing section inlines ~50 lines of decorative expected output ("🧪 Test 1: Initialization ... Results: 7/7 tests passed (100%)"), and "Common Usage Patterns" plus "Advanced Features" repeat CLI invocations already demonstrated in "Core Search Capabilities". It is above level 1 because the writing is command-focused rather than explaining concepts Claude already knows, but the padded and duplicated sections go beyond the 'some unnecessary explanation' of level 3.

2 / 5

Actionability

Most guidance is copy-paste ready ("python scripts/biorxiv_search.py --keywords 'CRISPR' ... --output results.json" plus a documented output schema and Python API), but several blocks are not executable: the Author Tracking example places shell commands inside a Python for-loop, the Custom Date Range block mixes `python scripts/...` lines into Python without f-strings, and imports are inconsistent (`from biorxiv_search import` vs `from scripts.biorxiv_search import`). These are more than trivial gaps, keeping it below level 5, but the majority of guidance is concrete and executable, above level 3.

4 / 5

Workflow Clarity

The Literature Review Workflow provides a clear numbered sequence (search → extract/review → download), but batch PDF downloads have no validation checkpoints — the loops never check download_pdf's return value or handle failures — and the Trend Analysis workflow ends vaguely with "Then analyze the temporal distribution in the results." Per the rubric's cap, batch operations without validation cannot score above 3; it stays at 3 rather than 2 because sequences are present and mostly well defined.

3 / 5

Progressive Disclosure

The body clearly signals a single one-level-deep reference ("references/api_reference.md - Complete bioRxiv API documentation"), but no references/ or scripts/ directories exist in the bundle, and substantial content that belongs in reference files is inlined — the full JSON output schema, the 27-item category list, and the ~50-line test expected output. Good section structure and clear signaling keep it above level 2; the inlined reference material and unresolvable referenced paths keep it below level 4.

3 / 5

Total

12

/

20

Passed

Description

88%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 concrete capabilities in third person, includes an explicit "Use this skill when..." trigger clause with concrete conditions, and occupies a distinct bioRxiv-preprints niche. The only improvement space is broader synonym coverage (papers, articles, .pdf) and narrowing the broad "literature reviews" trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs" — covering the tool's capabilities comprehensively. It exceeds the level-4 anchor (which allows minor coverage gaps) because every operational mode of the tool is named with its search dimensions.

5 / 5

Completeness

It explicitly answers both questions: the what is "Efficient database search tool for bioRxiv preprint server" and the when is an explicit trigger clause "Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories..." with concrete trigger phrases. This matches the level-5 anchor example structure; level 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural trigger terms are present and varied: "bioRxiv", "preprints", "life sciences preprints", "PDFs", "literature reviews", "keywords", "authors". It falls short of the level-5 anchor because common synonyms and variations (e.g. "papers", "scientific articles", ".pdf") are missing, but is well above level 3 since multiple natural phrases users would actually say are included.

4 / 5

Distinctiveness Conflict Risk

"bioRxiv preprint server" and "life sciences preprints" pin a clear, distinct niche with minimal overlap risk against generic search skills. It is not level 5 because the trigger "conducting literature reviews" is broad and could fire for general literature-search requests better served by other tools; it is well above level 3 because the bioRxiv/preprint triggers are highly specific.

4 / 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

referenced_paths_exist

Referenced path issues: 17 missing

Warning

Total

15

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/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.