bioproject-search — скилл для Claude Code: что делает и как установить
Скилл bioproject-search для Claude Code выгружает метаданные проектов NCBI BioProject через E-utilities API. Сохраняет названия, организмы и даты релизов в CSV или JSON.
MIT ★ 77 обновлён 2026-10-27
npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a claude-codeЧто делает bioproject-search
Скрипт scripts/search_bioprojects.py запрашивает метаданные NCBI BioProject через официальный E-utilities API вместо веб-скрейпинга. По списку идентификаторов PRJNA или PRJEB инструмент вызывает esearch, переводит номера во внутренние UID базы и параллельно опрашивает эндпоинты esummary и efetch. Так он извлекает таксономию, организацию, дату публикации и полный текст описания, после чего нормализует даты к формату YYYY-MM-DD.
Результаты сохраняются в файлы bioproject_data.csv и bioproject_data.json. Параметр --filter отбирает проекты с заданным ключевым словом, а --drop-noisy удаляет навигационный мусор из описаний.
Для работы нужен Python 3.9+ и библиотека requests. Правила NCBI требуют обязательный контактный email: его передают аргументом --email или переменной окружения BIOPIPE_EMAIL. Ключ API опционален и поднимает лимит запросов с 3 до 10 в секунду.
Какие задачи решает
- выгрузить метаданные проектов BioProject по номерам PRJNA или PRJEB
- отфильтровать проекты секвенирования по ключевому слову в описании
- сохранить названия, организмы и даты релизов проектов в CSV или JSON
- собрать сводный каталог датасетов для научной статьи или раздела методов
Примеры запросов агенту
- Собери метаданные BioProject для PRJNA172563 и PRJNA212358 в папку results/
- Выгрузи информацию по проектам из prj_ids.txt и отфильтруй записи по слову CRISPR
Как установить bioproject-search
1Через Skills CLI (Vercel)
npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a claude-code2Вручную: положить файлы
~/.claude/skills/bioproject-search/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/bioproject-search/
1Через Skills CLI (Vercel)
npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a codex2Вручную: положить файлы
.agents/skills/bioproject-search/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a cursor2Вручную: положить файлы
.cursor/skills/bioproject-search/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install ssinder/bioinformatics-agent-skills skills/bioproject-search2Вручную: положить файлы
.github/skills/bioproject-search/SKILL.md1Через Skills CLI (Vercel)
npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a gemini-cli2Командой платформы
gemini skills install https://github.com/ssinder/bioinformatics-agent-skills --path skills/bioproject-searchВручную: положить файлы
.devin/skills/bioproject-search/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о bioproject-search
Как установить bioproject-search в Claude Code?
Для установки выполните команду npx skills add ssinder/bioinformatics-agent-skills --skill bioproject-search -a claude-code.
Что делает bioproject-search?
Скилл пакетно запрашивает метаданные BioProject через NCBI E-utilities API по списку номеров проектов. Он объединяет данные из esummary и efetch и экспортирует их в CSV и JSON.
Что нужно для работы bioproject-search?
Требуются Python 3.9+, пакет requests и контактный адрес электронной почты, переданный в переменной BIOPIPE_EMAIL или аргументе --email. Для ускорения запросов можно указать ключ NCBI API.
Исходный текст
SKILL.md · MIT
--- name: bioproject-search description: >- Retrieves NCBI BioProject metadata — title, description, organism, submitter and release dates — for a batch of BioProject accessions, using the official NCBI E-utilities API rather than scraping the BioProject web pages. Supports keyword filtering over titles and descriptions, CSV/JSON export, and requires a contact email as the NCBI usage policy mandates. This skill should be used when looking up what a BioProject or PRJNA/PRD accession contains, retrieving sequencing project descriptions, or collecting BioProject metadata in bulk is requested. license: MIT compatibility: Python 3.9+; needs requests for network access; standard library only otherwise metadata: version: "1.0" last-reviewed: "2026-10-26" skill-author: sinder --- # BioProject Metadata Retrieval ## Overview This skill retrieves NCBI BioProject records through the official **E-utilities** API and exports them as CSV/JSON. The alternative — scraping the BioProject web pages — is fragile in a way that is easy to underestimate. Page-scraping code ends up with selectors like `div:nth-child(5)` that encode the *current* number of wrapper elements in the page. When NCBI adjusts its layout, the selector silently stops matching and the description column comes back empty, which is indistinguishable from "this project has no description". E-utilities returns structured XML with stable field names. The same query that works today keeps working after a website redesign. The skill also follows NCBI's usage policy properly: a **contact email is required** (via `--email` or the `BIOPIPE_EMAIL` environment variable). NCBI uses the email to identify callers and to contact them when problems occur; fabricating placeholder addresses defeats that purpose and can get your IP rate-limited. ## When to Use This Skill - Finding out what a specific BioProject / PRJNA / PRJEB accession contains - Collecting titles, descriptions and organisms for a list of projects - Screening projects by keyword before deciding which ones to download - Building a project catalogue for a methods or dataset section - Looking up submitter and release dates for citation purposes ## Quick Start ```bash export PYTHONPATH="$PWD/packages" export BIOPIPE_EMAIL="[email protected]" # 从文件读取 accession python scripts/search_bioprojects.py --ids prj_ids.txt --output-dir results/ # 直接给 accession python scripts/search_bioprojects.py --ids PRJNA172563 PRJNA212358 --output-dir results/ # 只保留描述里提到 CRISPR 的项目 python scripts/search_bioprojects.py --ids prj_ids.txt --output-dir results/ --filter CRISPR # 有 NCBI API key 时可提高限速(10 req/s) python scripts/search_bioprojects.py --ids prj_ids.txt --output-dir results/ --api-key $NCBI_API_KEY ``` ## Workflow 1. **Collect accessions** — `--ids` accepts accession strings or paths to text files (one per line, `#` for comments). Entries that do not look like BioProject accessions are reported and skipped rather than silently dropped. 2. **Resolve to UIDs** — `esearch` translates accessions into NCBI's internal UIDs. The query uses the `[Project Accession]` field qualifier, without which an accession string can match unrelated records. 3. **Fetch details from two endpoints** — `esummary` and `efetch` are called together and their results merged. This is not redundancy: **no single endpoint carries every field**. `esummary` is the only source for the structured organism name, taxonomy ID, project type and submitter organisation; `efetch` is the only source for the release date and the full description text. Calling only one of them silently drops about half the metadata without raising an error. 4. **Parse** — the merged records carry accession, title, name, description, organism, taxonomy ID, project type, submitter, registration date, release date and last-update date. All three NCBI date formats are normalised to `YYYY-MM-DD`. 5. **Filter (optional)** — `--filter` keeps records whose title, name or description contains the keyword (case-insensitive). `--drop-noisy` removes descriptions that look like page navigation rather than content. 6. **Export** — `bioproject_data.csv` and `bioproject_data.json` are written to the output directory. ## Parameters | Parameter | Default | Description | |---|---|---| | `--ids` | required | Accession list or path(s) to text files containing accessions | | `--output-dir` | `bioproject_results` | Output directory for the CSV/JSON results | | `--email` | `$BIOPIPE_EMAIL` | Contact email (required by NCBI's usage policy) | | `--api-key` | `$BIOPIPE_API_KEY` | NCBI API key; raises the rate limit from 3 to 10 req/s | | `--filter` | none | Keep only records whose title/name/description contains this keyword | | `--drop-noisy` | off | Drop descriptions that look like page navigation | | `--timeout` | `60` | Per-request timeout in seconds | ## Outputs | File | Content | |---|---| | `bioproject_data.csv` | One row per project: accession, title, name, description, organism, taxid, study type, submitter, registration date, release date, last-update date, UID | | `bioproject_data.json` | Same content as nested JSON | ## Validation - **A description should be a paragraph, not a sentence fragment.** Empty or one-word descriptions usually mean the project record genuinely lacks one — some submitters provide only a title. Cross-check with the linked BioSample or SRA records. - **The accession prefix indicates the archive** — `PRJNA` (NCBI), `PRJEB` (EBI/ENA), `PRJDB` (DDBJ). A project submitted to ENA may be reachable through ENA's own portal rather than NCBI's. - **Organism names come from the submitter** and are not normalised. A project may list several organisms, in which case the field contains a comma-separated list rather than a single taxon — do not treat it as a single taxid. The `organism` field always holds a *name*; the numeric identifier belongs in `taxid`. - **An empty date means "not recorded", not "zero".** NCBI uses the placeholder `1/01/01 00:00` for "date unknown"; it is deliberately not converted into a real date, so the field stays empty. Do not interpret an empty `registration_date` as a bug — check whether the project is dbGaP-backed (those records have their submitter details stripped). - **Release date may be in the future or absent** for embargoed projects. An embargoed project returns its metadata to authorised submitters only; the public record will be sparse. - **Search term semantics** — `[Project Accession]` matches the accession field exactly. To search descriptions by keyword across *all* projects rather than a known list, use NCBI Entrez directly with `bioproject[Filter]` and a keyword term. - **Search term semantics** — `[Project Accession]` matches the accession field exactly. To search descriptions by keyword across *all* projects rather than a known list, use NCBI Entrez directly with `bioproject[Filter]` and a keyword term. ## References - `references/methodology.md` — E-utilities protocol, field semantics, rate limits - `references/troubleshooting.md` — common failures and how to diagnose them - NCBI E-utilities documentation: <https://www.ncbi.nlm.nih.gov/books/NBK25501/> - BioProject: <https://www.ncbi.nlm.nih.gov/bioproject/>
© ssinder · MIT · ssinder/bioinformatics-agent-skills