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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with abundant executable examples, but the body is verbose and monolithic, and its multi-step/batch workflows lack validation checkpoints. Referenced bundle files (api_reference.md, biorxiv_search.py) are not present.

Suggestions

Tighten the body: collapse the repetitive near-identical CLI examples into a single parameterized reference and remove the full mock test-output block, keeping only how to run the tests.

Add validation/feedback loops to the batch PDF-download and multi-author workflows (e.g., check each download succeeded and retry/skip on failure before proceeding).

Move the full output-format schema, category list, and API details into the referenced `references/api_reference.md` and ship that file alongside `scripts/biorxiv_search.py` so referenced paths resolve.

Dimension	Reasoning	Score
Conciseness	Mostly useful but padded: many near-identical CLI invocations are repeated, and the full mock test-output block and tangential best-practices/pandas prose add tokens Claude does not need. Not 3 because it is not lean; not 1 because it avoids explaining basic concepts Claude already knows.	2 / 3
Actionability	Provides concrete, executable commands and copy-paste-ready Python throughout (real CLI flags, the BioRxivSearcher API, output schema). Not 2 because there is no pseudocode and the guidance is largely complete despite minor import-path inconsistencies.	3 / 3
Workflow Clarity	Numbered multi-step workflows exist (Literature Review, Author Tracking) but lack validation checkpoints or error-feedback loops, and batch PDF downloads have no per-item verification — capping this at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	Has section structure but is a monolithic ~470-line file with inline content (full output schema, category list, mock test output) that should be split out, and it references `references/api_reference.md` which does not exist in the bundle. Not 1 because organization is reasonable; not 3 because referenced files are absent and content is not appropriately split.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, third-person description that states concrete capabilities and pairs them with an explicit "Use this skill when" trigger scoped to bioRxiv. It is concise, distinctive, and uses natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers what ("Efficient database search tool for bioRxiv preprint server") and when ("Use this skill when searching for...") with an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered ("preprints", "keywords", "authors", "date ranges", "categories", "PDFs", "literature reviews", "bioRxiv"), not jargon. Not scored 2 because common variations are present rather than partially missing.	3 / 3
Distinctiveness Conflict Risk	Scoped to the bioRxiv preprint server with distinct triggers, giving it a clear niche unlikely to conflict with other skills; not generic enough to score 2.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 17 missing	Warning

	Total	14 / 16 Passed

Repository: wu-yc/LabClaw
Path: skills/literature/biorxiv-database/SKILL.md
Commit: df37802

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.