healthcare-dataset-discovery

Discover public healthcare datasets via OpenML, HuggingFace, Kaggle, and UCI APIs.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill healthcare-dataset-discovery-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healthcare-dataset-discovery
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/external-automation/healthcare-dataset-discovery
Command: npx skills add https://github.com/yakeworld/Synthos --skill healthcare-dataset-discovery-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finding usable public medical datasets is slow and error-prone: popular sources like UCI have removed classic datasets, GitHub mirrors are dead, and APIs like OpenML, Crossref, and PubMed have non-obvious parameter quirks that silently return empty results. This Skill encodes verified knowledge of which sources are accessible, which are dead, and how to call each API correctly. ## Core Features & Use Cases - Verified Source Registry: Distinguishes accessible datasets (e.g., OpenML Cardiovascular-Disease-dataset, DID=45547, 70,000 records) from unavailable ones (UCI stroke data, dead GitHub mirrors) with concrete 404/authentication evidence. - API Quirk Handling: Documents correct endpoint patterns, such as using OpenML /api/v1/json/data/list without limit/500, distinguishing list vs. detail response structures, and using query= with quote_plus() for Crossref and + for PubMed spaces. - Golden Test Set: Ships three weighted test cases covering the normal discovery path, the dead-link failure path, and API parameter traps, requiring evidence-backed conclusions. - Use Case: A medical AI researcher needs a cardiovascular dataset; the Skill queries OpenML, filters locally, and returns a verified dataset entry with name, source, URL, size, and access type instead of a dead UCI link. ## Quick Start Ask the agent to find a public dataset for a medical domain such as cardiovascular disease and return verified sources with access details.

Frequently Asked Questions about healthcare-dataset-discovery

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

FAQPage Schema
How do I find public healthcare datasets for machine learning?

Query the OpenML API at /api/v1/json/data/list to retrieve the full dataset catalog, then filter locally by name or description. Verified accessible options include the Cardiovascular-Disease-dataset (DID=45547) with 70,000 records and 13 features.

How to search OpenML datasets using its API?

Call /api/v1/json/data/list without a limit parameter, since limit/500 returns empty results. The list endpoint returns {"data": {"dataset": [...]}} while the detail endpoint returns {"data_set_description": {...}}, so parse each structure differently.

Is the UCI stroke dataset still available for download?

No, the healthcare-dataset-stroke-data.csv file was removed from UCI and returns 404. Known GitHub mirrors (dsrscientist, codeheroku, krishnaik06) are dead, HuggingFace returns 404, and Kaggle requires authentication, so use an OpenML equivalent instead.

Why does my Crossref or PubMed API query return empty results?

Crossref requires the query= parameter rather than search=, and spaces must be encoded with quote_plus() or +. PubMed eSearch requires + for spaces instead of standard URL encoding, otherwise queries fail or return nothing.

What are the limitations of Kaggle for public dataset discovery?

Kaggle requires authentication for dataset access and many datasets sit behind paywalls or login gates. For open medical research data, OpenML is preferred because it offers a stable API with explicit metadata like dataset IDs and feature counts.