vimalinx/bio-agent / .claude/skills/efilter
efilter
UnverifiedUse when filtering Entrez search results by date, organism, publication type, sequence features, or other database-specific criteria in bioinformatics pipelines.
efilter
Quick Start
- Command:
efilter - Local executable:
/home/vimalinx/miniforge3/envs/bio/bin/efilter - Full reference: See
references/help.md
When To Use This Tool
- Narrow an existing Entrez result set by date, organism, publication type, sequence feature, SNP class, or assembly status.
- Add database-specific shortcuts after
esearchorelinkwithout rewriting the whole query string. - Prototype filters interactively before folding them back into a single
esearchcommand.
Common Patterns
# 1) Keep only recent PubMed hits from a pipeline
esearch -db pubmed -query "opsin gene conversion" \
| efilter -mindate 2015 \
| efetch -format docsum
# 2) Restrict sequence results to mammalian RefSeq entries
esearch -db protein -query hemoglobin \
| efilter -organism mammals -source refseq
# 3) Keep only latest assemblies
esearch -db assembly -query "Escherichia coli" \
| efilter -status latest
Recommended Workflow
- Start with an
esearchorelinkpipeline that already identifies the right Entrez database. - Apply only the shortcut family that matches that database category, such as
-pubfor PubMed or-organismfor sequence databases. - Inspect counts or summaries if the filter logic is non-obvious.
- Fetch full records only after the filter stage is stable.
Guardrails
- The local executable is just a wrapper around
esearch -filter, so it depends on valid Entrez pipeline state and is not an offline post-processor. - Shortcut families are database-specific; mixing incompatible groups produces confusing or empty results.
- Many
efiltershortcuts can also be expressed directly inesearch, which is often cleaner once you know the final query. - In this local install, help output can still emit network-version-check noise from EDirect before printing the real usage text.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |