Menu

Individual skill

database-lookup

0upvotes

Queries documented public database APIs with explicit endpoints, filters, pagination, and provenance. Used when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly from a named source rather than inferred from general knowledge.

skills/database-lookup/SKILL.md

Read pinned source

Source commit 2d2065fb4520fa3f3f2bcf61cff26ec8b7eba4b5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56,660
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Database Lookup

This skill catalogs 80 databases with public, registered, or licensed access patterns. Your job is to turn the user's intent into a reproducible retrieval: select the authoritative database(s), make bounded and rate-limited API calls, verify counts when completeness matters, and return results with enough provenance that another agent or human can repeat the lookup.

For complex biomedical retrievals, assume small filtering differences can change downstream conclusions. Prefer deterministic APIs, explicit identifiers, exhaustive pagination, and auditable logs over broad searching or plausible summaries.

## Core Workflow

1. **Define the retrieval contract** — Identify the target entity, accepted identifiers, organism/taxon/build/date constraints, filters, expected output fields, and whether the user needs an exhaustive dataset or a targeted lookup. If a required scientific constraint is missing and affects correctness, ask a clarifying question rather than guessing.

2. **Select authoritative database(s)** — Use the database selection guide below. Prefer the primary database for the user's intent, then add cross-check databases only for identifier resolution, validation, or known coverage gaps. Do not fan out across many APIs just because they are available.

3. **Read the reference file and retrieval contract** — Each database has a reference file in `references/` with endpoint details, query formats, and example calls. Read the relevant file(s) and `references/retrieval-contract.md` before making API calls.
Back to top