New to Claude Skills? Learn how to install them →

k-dense-ai on GitHub

NCATS ARAX

Free

Access biomedical knowledge-graph relationships efficiently.

Get this skill

Free · Opens the source repo

What NCATS ARAX does

The NCATS ARAX skill enables users to query the NCATS Translator ARAX production API for biomedical knowledge-graph relationships. It supports one-hop and two-hop queries, ensuring that the results are bounded, typed, and rich in provenance. This skill is particularly useful for researchers and developers working in the biomedical field who need to access structured data about relationships between entities like diseases, genes, and small molecules. By using this skill, users can perform precise lookups while adhering to the constraints of the Biolink model, which helps maintain data integrity and relevance.

To use the NCATS ARAX skill effectively, users must first normalize their queries by reviewing and reporting the proposed CURIEs and categories. The skill supports explicit one-hop and two-hop queries, allowing users to pin endpoints and specify the types of entities involved. This ensures that the results are directly relevant to the user's research questions. The skill also provides capabilities for inspecting query-edge bindings and provenance, which is crucial for verifying the accuracy of the results and understanding the source of the data.

It is important to note that the NCATS ARAX skill is designed for public, nonsensitive research questions only. Users should avoid submitting patient information or proprietary hypotheses, as the skill is not intended for clinical guidance or sensitive queries. The workflow includes steps for verifying results outside of ARAX, which emphasizes the need for independent validation of scientifically important paths. This skill is ideal for those who require a structured approach to querying biomedical data without the risks associated with sensitive information.

When to use it

Use this skill when you need to perform structured queries on biomedical knowledge graphs for research purposes.

When not to use it

Avoid using this skill for clinical guidance, sensitive queries, or open-ended pathfinding, as it is not designed for those scenarios.

What you can build with it

Researching Drug-Disease Relationships

Use the one-hop query feature to explore how specific drugs affect particular diseases, providing insights for further research.

Validating Biomedical Hypotheses

Leverage the two-hop query functionality to validate hypotheses about gene interactions and their implications in disease contexts.

Exploring Entity Relationships

Utilize the normalization feature to understand the relationships between various biomedical entities before conducting deeper queries.

How to install NCATS ARAX

View source

1. Install with the skills CLI

npx skills add k-dense-ai/scientific-agent-skills/ncats-arax --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by k-dense-ai

NCATS ARAX

Use ARAX as a constrained knowledge-graph lookup service. Submit reviewed CURIEs and explicit Biolink types, preserve the exact TRAPI exchange, inspect query-edge bindings and provenance, and treat every returned path as a candidate for subsequent verification.

Read query-contract.md before constructing a query. Read output-schema.md when interpreting saved artifacts, warnings, provenance, or partial results.

Safety boundary

  • Use only public, nonsensitive research questions. ARAX status facilities may expose query and caller metadata even when store=false is requested.
  • Do not submit patient information, confidential research questions, unpublished compound programs, or proprietary target hypotheses.
  • Do not present a returned path as a validated mechanism or clinical recommendation.
  • Report a zero as "not returned under these constraints," never as evidence that no relationship exists.
  • Describe position as unscored response order, never rank.
  • Verify important candidates with literature and authoritative databases separately.

Workflow

  1. Normalize free text separately, then review and report the proposed CURIE and category.
  2. Choose a typed one-hop query or an exactly two-hop query with both endpoints pinned.
  3. Use default RTX-KG2 lookup unless the user explicitly names two to five providers.
  4. Acknowledge that the biomedical query is public and choose a new or empty output directory.
  5. Run the client once. Do not silently change provider selection or expansion order after a failure or empty result.
  6. Inspect summary.json for bounded bindings and provenance and response.json for the exact TRAPI payload.
  7. Verify scientifically important paths outside ARAX.

Preflight

Check the production OpenAPI without making a biomedical query:

python skills/ncats-arax/scripts/arax_client.py preflight

The client verifies that the service identifies itself as ARAX, exposes /query, and reports a supported TRAPI version. A nonproduction endpoint or untested TRAPI series requires an explicit override; neither override changes the fixed query shapes or operations.

Normalize an entity

Normalization is review-only and never triggers a graph query:

python skills/ncats-arax/scripts/arax_client.py normalize "primary myelofibrosis" \
  --expected-category biolink:Disease \
  --max-synonyms 10 \
  --acknowledge-public-query \
  --output-dir outputs/normalize-myelofibrosis

Review the canonical identifier, name, category, and synonym preview before using a CURIE. Report all CURIEs and categories regardless of query outcome. A category warning or zero result is a reason to curate the identifier, not to chain automatically to /query.

One-hop lookup

Pin at least one endpoint and type both nodes:

python skills/ncats-arax/scripts/arax_client.py one-hop \
  --subject-id CHEBI:31690 \
  --subject-category biolink:SmallMolecule \
  --predicate biolink:affects \
  --object-id NCBIGene:25 \
  --object-category biolink:Gene \
  --qualifier biolink:object_aspect_qualifier=activity_or_abundance \
  --qualifier biolink:object_direction_qualifier=decreased \
  --acknowledge-public-query \
  --output-dir outputs/imatinib-abl1

Lookup mode is the default and fixes expansion to infores:rtx-kg2. It defaults to 20 results. Use --result-limit N to request 1-50 results; 50 is the hard cap in either mode.

Endpoint-pinned two-hop lookup

Use exactly one typed, unpinned intermediate node:

python skills/ncats-arax/scripts/arax_client.py two-hop \
  --subject-id CHEBI:66901 \
  --subject-category biolink:SmallMolecule \
  --predicate-1 biolink:affects \
  --intermediate-category biolink:Gene \
  --predicate-2 biolink:associated_with \
  --object-id MONDO:0009061 \
  --object-category biolink:Disease \
  --qualifier-1 biolink:object_aspect_qualifier=activity_or_abundance \
  --qualifier-1 biolink:object_direction_qualifier=increased \
  --expand-order right-first \
  --acknowledge-public-query \
  --output-dir outputs/ivacaftor-cystic-fibrosis

Right-first expansion is the default. If an empty result merits another attempt, run a new query explicitly with --expand-order left-first and keep the runs separate.

Selected-provider federation

Federation is explicit and accepts two to five named providers:

python skills/ncats-arax/scripts/arax_client.py one-hop \
  --subject-id CHEBI:31690 \
  --subject-category biolink:SmallMolecule \
  --predicate biolink:affects \
  --object-id NCBIGene:25 \
  --object-category biolink:Gene \
  --mode federated \
  --kp infores:rtx-kg2 \
  --kp infores:molepro \
  --acknowledge-public-query \
  --output-dir outputs/federated-imatinib-abl1

Federation defaults to the hard maximum of 50 results. Provider errors may coexist with useful results; such a run exits 7 after retaining its artifacts and is marked partial.

Inspect saved provenance

Rebuild a bounded summary without network access:

python skills/ncats-arax/scripts/arax_client.py summarize \
  --request outputs/ivacaftor-cystic-fibrosis/request.json \
  --response outputs/ivacaftor-cystic-fibrosis/response.json \
  --format text

The inspector accepts only the same constrained request shapes and fixed operations that the live commands generate. Use --format json for the normalized view on standard output.

Interpret results

  • Follow each analysis's query-edge bindings; do not summarize every knowledge-graph edge.
  • Preserve the physical edge subject, predicate, object, and qualifier values returned by ARAX. Returned predicates or qualifier aspects may be more specific than the query constraint.
  • Inspect all source objects, including primary, aggregator, supporting-data, upstream-resource, and source-record URL fields.
  • Treat publication_availability: not_returned as missing metadata, not evidence that no publications exist.
  • Treat missing auxiliary-graph references and provider failures as explicit warnings.
  • Consult the raw response whenever the bounded summary omits detail or the service response is partial, unfamiliar, or scientifically surprising.

Deliberate exclusions

The client has no raw-query, workflow, operation, overlay, ranking, inference, link-prediction, Pathfinder, ARS, batch, all-provider, three-hop, cache, daemon, SDK, MCP, or natural-language-to-TRAPI surface. Do not work around those limits with direct HTTP calls under this skill.

Official references

Frequently asked questions about NCATS ARAX

Similar skills