database-lookup

Retrieve reproducible records from public scientific and clinical databases.

74|5|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/dralkh/seerai --skill database-lookup-dralkh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-lookup
Source: https://github.com/dralkh/seerai/tree/main/skills/database-lookup
Command: npx skills add https://github.com/dralkh/seerai --skill database-lookup-dralkh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns broad research questions into deterministic database lookups so you can retrieve authoritative facts, not vague summaries, from public scientific, clinical, environmental, financial, and demographic sources.

Core Features & Use Cases

  • Reproducible retrieval: Chooses the right source, uses explicit identifiers, and returns auditable results with endpoints, parameters, and access dates.
  • Coverage across domains: Supports compounds, genes, proteins, pathways, variants, clinical trials, patents, weather, astronomy, economics, and population data.
  • Completeness and provenance: Handles pagination, count reconciliation, rate limits, identifier conversion, and source-specific quirks so downstream analysis stays trustworthy.

Quick Start

Ask the database-lookup skill to find the authoritative record, retrieve it with explicit filters, and return a concise provenance-backed result table.

Frequently Asked Questions about database-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve reproducible records from public scientific databases using REST APIs?

Reproducible database lookup requires explicit identifiers, API-specific filters, and pagination to fetch authoritative records from scientific databases. It returns auditable results with endpoints, parameters, and access dates so downstream analysis stays verifiable.

What is identifier resolution and how does it work for clinical trials and gene variants?

Identifier resolution maps explicit identifiers to authoritative records across clinical trials, genes, and variants. It handles source-specific quirks and identifier conversion to ensure accurate, reproducible retrieval from public scientific databases.

How do I handle pagination and rate limits when querying environmental and financial databases?

Handling pagination and rate limits involves using API-specific filters and count reconciliation when querying environmental and financial databases. This ensures exhaustive searches return complete datasets while respecting source constraints for trustworthy results.

Can I use database lookup tools to search compounds, proteins, and pathways without knowing the exact source?

Yes, database lookup selects the right source automatically based on your query domain, covering compounds, proteins, and pathways. It requires explicit identifiers but manages source selection so you do not need to specify the exact database.

Why does my API database lookup return incomplete results for economic indicators and demographic data?

Incomplete results often occur when pagination and count reconciliation are not applied during database lookup for economic indicators and demographic data. Proper identifier resolution and rate-limit awareness ensure exhaustive searches return full datasets.

What's the best way to ensure provenance and reproducibility when retrieving astronomy or weather data via REST APIs?

The best way to ensure provenance during database lookup is to retrieve records with explicit identifiers and return auditable results including endpoints, parameters, and access dates. This guarantees astronomy and weather data retrieval remains fully reproducible.