Skip to content
Skills Library
Science & research · Tool integration

biodbnet-api

/biodbnet-api

Access bioDBnet REST services for biological identifier conversion, pathway retrieval, and ortholog mapping. Use when you need to convert gene/protein IDs, find pathways, or retrieve biological annotations via bioDBnet.

Licence
MIT
Last repository change
17.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
1
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 17.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/biodbnet_client.py

What it does and when to use it

Access bioDBnet REST services for biological identifier conversion, pathway retrieval, and ortholog mapping. Use when you need to convert gene/protein IDs, find pathways, or retrieve biological annotations via bioDBnet.

Original author description

Access bioDBnet REST services for biological identifier conversion, pathway retrieval, and ortholog mapping. Use when you need to convert gene/protein IDs, find pathways, or retrieve biological annotations via bioDBnet.

How it works

  1. When to Use
  2. Key Features
  3. Dependencies
  4. Example Usage
  5. Implementation Details
  6. Usage
  7. Commands
  8. When Not to Use
  9. Required Inputs
  10. Recommended Workflow
Original SKILL.md headings · 124 lines, 798 words
SKILL.md preview
---
name: biodbnet-api
description: Access bioDBnet REST services for biological identifier conversion, pathway retrieval, and ortholog mapping. Use when you need to convert gene/protein IDs, find pathways, or retrieve biological annotations via bioDBnet.
license: MIT
author: AIPOCH
---
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)

# bioDBnet API Skill

This skill provides access to bioDBnet (biological Database network) REST web services. It allows for integrating biological data from multiple databases, converting identifiers, and retrieving pathway or ortholog information.

## When to Use

- Use this skill when the request matches its documented task boundary.
- Use it when the user can provide the required inputs and expects a structured deliverable.
- Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming.

## Key Features

- Scope-focused workflow aligned to: Access bioDBnet REST services for biological identifier conversion, pathway retrieval, and ortholog mapping. Use when you need to convert gene/protein IDs, find pathways, or retrieve biological annotations via bioDBnet.
- Packaged executable path(s): `scripts/biodbnet_client.py`.
- Reference material available in `references/` for task-specific guidance.
- Structured execution path designed to keep outputs consistent and reviewable.

## Dependencies

- `Python`: `3.10+`. Repository baseline for current packaged skills.
- `Third-party packages`: `not explicitly version-pinned in this skill package`. Add pinned versions if this skill needs stricter environment control.

## Example Usage

See `## Usage` above for related details.

```bash
cd "20260316/scientific-skills/Others/biodbnet-api"
python -m py_compile scripts/biodbnet_client.py
python scripts/biodbnet_client.py --help
```

Example run plan:
1. Confirm the user input, output path, and any required config values.
2. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.
3. Run `python scripts/biodbnet_client.py` with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.

## Implementation Details

- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
- Primary implementation surface: `scripts/biodbnet_client.py`.
- Reference guidance: `references/` contains supporting rules, prompts, or checklists.
- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.

## Usage

The core functionality is provided by the `scripts/biodbnet_client.py` script. This script handles the HTTP requests to the bioDBnet API.

### Common Operations

1.  **ID Conversion (db2db)**: Convert identifiers (e.g., Gene Symbol to Affy ID).
2.  **Pathway Retrieval (getPathways)**: Get signaling pathways for a taxon.
3.  **Orthologs (dbOrtho)**: Find orthologs between species.
4.  **Annotations (dbAnnot)**: Retrieve annotations for genes/proteins.

## Commands

To use the API, execute the python script with the appropriate method and parameters.

```bash
python scripts/biodbnet_client.py --method <method_name> --params <json_params>
```

See `references/api_methods.md` for a complete list of supported methods and their parameters.

## When Not to Use

- Do not use this skill when the required source data, identifiers, files, or credentials are missing.
- Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
- Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.

## Required Inputs

- A clearly specified task goal aligned with the documented scope.
- All required files, identifiers, parameters, or environment variables before execution.
- Any domain constraints, formatting requirements, and expected output destination if applicable.

## Recommended Workflow

1. Validate the request against the skill boundary and confirm all required inputs are present.
2. Select the documented execution path and prefer the simplest supported command or procedure.
3. Produce the expected output using the documented file format, schema, or narrative structure.
4. Run a final validation pass for completeness, consistency, and safety before returning the result.

## Output Contract

- Return a structured deliverable that is directly usable without reformatting.
- If a file is produced, prefer a deterministic output name such as `biodbnet_api_result.md` unless the skill documentation defines a better convention.
- Include a short validation summary describing what was checked, what assumptions were made, and any remaining limitations.

## Validation and Safety Rules

- Validate required inputs before execution and stop early when mandatory fields or files are missing.
- Do not fabricate measurements, references, findings, or conclusions that are not supported by the provided source material.
- Emit a clear warning when credentials, privacy constraints, safety boundaries, or unsupported requests affect the result.
- Keep the output safe, reproducible, and within the documented scope at all times.

## Failure Handling

- If validation fails, explain the exact missing field, file, or parameter and show the minimum fix required.
- If an external dependency or script fails, surface the command path, likely cause, and the next recovery step.
- If partial output is returned, label it clearly and identify which checks could not be completed.

## Quick Validation

Run this minimal verification path before full execution when possible:

```bash
python scripts/biodbnet_client.py --help
```

Expected output format:

```text
Result file: biodbnet_api_result.md
Validation summary: PASS/FAIL with brief notes
Assumptions: explicit list if any
```
Files in this package (4)
  • SKILL.md 6 KB
  • biodbnet-api_audit_result_v2.json 12 KB
  • references/api_methods.md 2 KB
  • scripts/biodbnet_client.py 2 KB

Versions

The database has no other skills named biodbnet-api.

Database snapshot: 13.11.2026 · package version 5e3b56038665 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100uniprot-database
    Direct REST API access to UniProt for protein search, entry retrieval, and identifier mapping; use when you need programmatic UniProtKB queries or cross-database ID conversion.
  • 90bioinformatics
    Performs bioinformatics analyses including pathway enrichment, gene ontology analysis, protein-protein interaction networks, multi-omics integration, and biological sequence database querying; trigger when users discuss gene sets, biological pathways, functional annotation, or…
  • 100alterlab-reactome
    Query the Reactome REST API for pathway analysis, over-representation/enrichment, gene-to-pathway mapping, disease pathways, molecular interactions, and expression analysis. Use when running pathway enrichment on a gene list, mapping genes to curated biological pathways, or…
  • 100ensembl-database
    Access Ensembl REST API for vertebrate genomic data; use when you need gene/ID lookups, sequence retrieval, variant effect prediction (VEP), or homology/assembly coordinate mapping.
  • 90bio-database-evidence
    Unified biological database evidence owner. Use for gene annotation, variant clinical significance, cancer mutation evidence, GWAS trait associations, pathway mapping, target-disease evidence, protein structures, protein interaction networks, reference single-cell census…
  • 100kegg-database
    Direct REST API access to KEGG (academic use only). Pathway analysis, gene-pathway mapping, metabolic pathways, drug interactions, ID conversion. For Python workflows with multiple databases, prefer bioservices. Use this for direct HTTP/REST work or KEGG-specific control.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.