Agent skill · Backend & API

polars-dovmed

Search the PMC Open Access literature with polars-dovmed. Author structured JSON queries directly, then use the hosted API when an API key is available or fall back to local dovmed scan over PMC, bioRxiv, or both parquet corpora.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill polars-dovmed --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 20 KB
Bundled scripts: yes
Path: skills/omics/polars-dovmed/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 135
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# polars-dovmed Search the PubMed Central Open Access subset and the bioRxiv parquet corpus with `polars-dovmed`. The preferred workflow is always: 1. decide execution mode up front 2. author a structured query JSON directly 3. inspect and refine the query JSON 4. run structured discovery first 5. fetch paper details for candidate PMC IDs or bioRxiv DOIs 6. use structured advanced scans only for final refinement when needed Search execution has two modes: - Preferred when available: hosted API over `pmc`/OpenPMC, `biorxiv`, or `both` - Fallback: local `dovmed scan` over local parquet files for `pmc`, `biorxiv`, or `both` PMC is physically materialized into clean publication-year chunks: - `pre_2010` - `2010_2020` - `2021_2023` - `2024_plus` For latest-literature discovery, prefer the hosted API helper with parallel clean chunks: `--year-bands recent_split` for `2024_plus` plus `2021_2023`. Use `--year-bands clean_split` when the user needs broad coverage across all clean PMC chunks. Use a single `--year-band` only when the question is explicitly restricted to one era. Avoid the unmaterialized `2020_2023` split. Do not skip the structured-query authoring step unless the user explici

What's inside
Steps it walks through
  1. Input Requirements
  2. Hosted API Reachability Rules
  3. Instructions
  4. Preferred Workflow
  5. Step 1: Author Query JSON Directly
  6. Query Authoring Rules
  7. Quick Templates
  8. Step 2: Create A Run Directory
  9. Step 3A: Search With Hosted API
  10. Step 3B: Search Locally With dovmed scan
  11. Search Semantics
  12. Retrieval Quality Playbook
  13. Hit Ranking Guidance
  14. Recall-First Principle
Ships with 5 files
  • agents/openai.yaml
  • fixtures/smoke_prompt.txt
  • fixtures/smoke_query.json
  • scripts/query_literature.py
  • scripts/smoke_test.py
Commands it runs
curl -sS --max-time 20 https://api.newlineages.com/
curl -sS --max-time 45 \
mkdir -p runs/klosneuvirinae-hosts
printf '%s\n' "find papers that describe hosts of Klosneuvirinae" > runs/klosneuvirinae-hosts/prompt.txt
cp queries/klosneuvirus_hosts.json runs/klosneuvirinae-hosts/query.json
python skills/polars-dovmed/scripts/query_literature.py \
python skills/polars-dovmed/scripts/smoke_test.py
skills/polars-dovmed/runs/smoke-test/
More from awesome-bio-agent-skills
All skills →
About this skill
What does the polars-dovmed skill do?

Search the PMC Open Access literature with polars-dovmed. Author structured JSON queries directly, then use the hosted API when an API key is available or fall back to local dovmed scan over PMC, bioRxiv, or both parquet corpora.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill polars-dovmed --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going