database-lookup

Map user queries to public databases and fetch raw JSON/XML data.

22|4|Updated May 25, 2026
One-click install
npx skills add https://github.com/crazymsn/academic-skills --skill database-lookup-crazymsn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-lookup
Source: https://github.com/crazymsn/academic-skills/tree/main/academic-skills/database-lookup
Command: npx skills add https://github.com/crazymsn/academic-skills --skill database-lookup-crazymsn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Retrieve and integrate data from 78 public databases quickly, without manually visiting multiple sources.

Core Features & Use Cases

  • Public-database discovery: identify relevant databases for a given query and fetch data via REST endpoints.
  • Cross-database lookup: resolve identifiers across domains (genes, chemicals, diseases, patents) and consolidate results.
  • Provenance & raw data: surface raw JSON/XML from each database with source metadata for auditability.
  • Use case: you need all publications related to TP53 across multiple databases in a single view to support a literature review.

Quick Start

Query a gene symbol (e.g., TP53) and retrieve basic records from multiple public databases.

Frequently Asked Questions about database-lookup

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

FAQPage Schema
How do I query multiple public databases for the same gene or chemical identifier at once?

Cross-database lookup resolves identifiers across biology, chemistry, and economics domains by mapping your query to relevant public databases, fetching raw JSON/XML via REST APIs, and consolidating results with source provenance into a single view.

What is the best way to retrieve raw JSON data and provenance from public REST APIs for a literature review?

Querying public REST APIs via database lookup retrieves raw JSON/XML data and surfaces source metadata for auditability, allowing you to collect all records related to a topic like TP53 across 78 public databases for literature review support.

Can I resolve biological identifiers like gene symbols across different databases without visiting each source manually?

Yes, identifier normalization handles mapping biological identifiers like gene symbols to appropriate endpoints across 78 public databases, automatically parameterizing requests and fetching consolidated results with database references without manual source visits.

Does cross-database lookup work with economics and chemistry data, or is it limited to biology?

Cross-database lookup operates across biology, chemistry, and economics domains to retrieve data and provenance, resolving identifiers for chemicals, diseases, and patents in addition to biological entities like genes.

What are the limitations of using REST API database lookup for cross-database identifier resolution?

This approach returns raw JSON/XML data from 78 public databases, which may require subsequent parsing and integration, and relies on the availability and parameterization rules of each external REST endpoint for successful data retrieval.