Skip to content
Research Agent Skillsby Kalaris Labs
Install
Scientific Databasesv1.0AdaptedMIT

ncats-arax

Queries the NCATS Translator ARAX production API for bounded, typed, provenance-rich one-hop and endpoint-pinned two-hop biomedical knowledge-graph relationships. Use for Biolink-constrained RTX-KG2 lookup, explicit selected-provider ARAX federation, separate entity normalization, qualifier-aware graph traversal, and inspection of TRAPI edge bindings, publications, and knowledge-source provenance. Do not use for inference, ranking, open-ended pathfinding, clinical guidance, or sensitive queries.

Install this skill

Works with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, and 70+ other harnesses.

skills.sh CLI (Recommended)
npx skills add KalarisLabs/research-agent-skills --skill ncats-arax
uvx (Python tool runner)
uvx research-agent-skills install ncats-arax

Documentation & Instructions

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

Agent operating procedure

  1. Check the environment. Confirm network access, API keys (if required) and the database's current API documentation and rate limits.
  2. Pin down the inputs. Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.
  3. Run a small version first. Fetch a single known record and check the response format before bulk queries.
  4. Execute the full task using the instructions and references above.
  5. Validate the result. Identifiers resolve, record counts are reported, and the database version or access date is recorded.
  6. Report. State what was run (versions, commands, parameters), what was checked, and what is still uncertain.
If this happens Do this
HTTP 429 or 5xx errors Respect rate limits with backoff, batch requests, and report partial results honestly.
A function, flag or endpoint in these instructions is missing in the installed version Check the installed version's own documentation (help(), --help, official docs), adapt, and tell the user. Never invent an API.
A required input, identifier or parameter is ambiguous Ask the user, or state the assumption explicitly before running.

Integrity rules

  • Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.
  • Never invent accession numbers, IDs or records; report 'not found' instead.
  • Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.
  • Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.

Trigger Prompts & Evaluation Corpus

These evaluation prompts test that the agent correctly selects ncats-arax for relevant tasks and leaves it out for near misses.

Should trigger (3)

  • should trigger

    “Use ARAX to find what genes are connected to imatinib. Just one hop, keep it small.”

    expects Normalizes imatinib separately and reports the proposed CURIE and category for review, then runs a typed one-hop default RTX-KG2 lookup with a bounded result limit (default 20). Reports results as unscored response order and notes the paths are candidates needing outside verification.

  • should trigger

    “I'm putting together a figure for our review on cystic fibrosis. I have MONDO:0009061 and NCBIGene:1080 (CFTR) saved in ids.txt. Can you query ARAX for a path Disease -> ? -> Gene through one intermediate node, with both ends pinned? Write the output to ./arax_cf_run1, and then show me which sources (primary and aggregator) each edge came from and whether publications were returned.”

    expects Runs an exactly two-hop endpoint-pinned query with a typed, unpinned intermediate node, using default right-first expansion and a new output directory. Inspects summary.json and response.json for query-edge bindings, all knowledge-source provenance fields, and publications. Treats publication_availability not_returned as missing metadata, and acknowledges that the query is public and nonsensitive.

  • should trigger

    “I want to see what the Translator ARAX service and a couple of specific providers, say RTX-KG2 and one other that I'll pick, each say about relationships of a known gene, side by side, without it guessing for me. How should we do that?”

    expects Explains explicit selected-provider federation with two to five named providers (not all providers), asks the user to name the second provider and confirm the CURIE and type before running. Notes the 50-result default, that provider errors can produce partial results (exit 7), and that provider selection must not be silently changed after a failure.

Near misses (2)

  • near miss

    “Here's our unpublished lead compound series and our proprietary target hypothesis. Use ARAX to predict which other targets it might hit and rank the likely off-target proteins for us.”

    expects Declines to use ARAX for this: the data is confidential or proprietary and could be exposed through ARAX status facilities, and the skill excludes inference, ranking and link prediction. Suggests appropriate in-house or offline methods instead, and does not run any query.

  • near miss

    “Search PubMed for recent papers on CFTR modulators and summarize the top 10 abstracts with citations.”

    expects Recognizes this as a literature search and summarization task rather than a knowledge-graph lookup. It uses a literature or PubMed search approach, not ARAX, and cites only retrieved records.