search-geo
Skill4 starsChanged 12 days agoMITView on GitHub
Search NCBI Gene Expression Omnibus (GEO) for expression datasets, series, samples, and platforms using E-utilities or the GEO query API.
In this repository56 other files it gives its agents.
- bioinformatics-env-setupSkill
- design-thermostable-mutationsSkill
- download-gdcSkill
- download-geoSkill
- download-sraSkill
- source-summarizerSkill
- genome-alignment-qcSkill
- genome-read-alignmentSkill
- genome-variant-annotationSkill
- genome-variant-callingSkill
- genome-variant-filteringSkill
- metagenome-assemblySkill
- metagenome-binningSkill
- metagenome-functional-profilingSkill
- metagenome-host-removalSkill
- metagenome-taxonomic-profilingSkill
- ncbi-eutilities-assistantSkill
- ngs-quality-controlSkill
- ngs-read-preprocessingSkill
- paper-to-briefSkill
- predict-protein-heat-stabilitySkill
- researchSkill
- rnaseq-alignment-qcSkill
- rnaseq-differential-expressionSkill
- rnaseq-functional-enrichmentSkill
- rnaseq-read-alignmentSkill
- rnaseq-read-countingSkill
- rnaseq-transcript-quantificationSkill
- rpsblast-assistantSkill
- scrnaseq-cellranger-countSkill
- scrnaseq-cell-type-annotationSkill
- scrnaseq-clusteringSkill
- scrnaseq-differential-expressionSkill
- scrnaseq-integrationSkill
- scrnaseq-quality-controlSkill
- scrnaseq-trajectory-analysisSkill
- search-enaSkill
- search-gsaSkill
- search-ncbi-datasetsSkill
- search-sraSkill
- stat-analyze-distributionSkill
- stat-assess-data-qualitySkill
- stat-bayesian-estimationSkill
- stat-cluster-samplesSkill
- stat-compare-multiple-groupsSkill
- stat-compare-two-groupsSkill
- stat-fit-glmSkill
- stat-fit-linear-modelSkill
- stat-learn-bayesian-networkSkill
- stat-logistic-regressionSkill
- stat-nonlinear-embeddingSkill
- stat-pairwise-correlationSkill
- stat-pcaSkill
- stat-survival-analysisSkill
- structured-intelligence-skill-creatorSkill
- <skill-id>Skill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
Run esearch -db gds -query "<term>" | esummary -format json to retrieve series metadata.
- Distinctive: line 54
Search query used (exact E-utilities command or API URL)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Search GEO
Use When
- A user wants to find expression datasets, RNA-seq series, microarray experiments, or epigenomics datasets in NCBI GEO.
- A user needs to look up GEO accessions: GSE (series), GSM (sample), GPL (platform), or GDS (curated dataset).
- A user wants to search GEO by organism, tissue, disease, treatment, assay type, or free-text keyword.
- A user wants to retrieve series metadata: number of samples, associated publication (PMID), submission date, platform.
- A user wants a list of GSM sample accessions for a given GSE series.
- A user wants to find GEO datasets suitable for a specific analysis (e.g., bulk RNA-seq of a specific cell type).
Inputs
- Required:
- one of: free-text search query, GEO accession (GSE/GSM/GPL/GDS), organism name, or PubMed ID
- Optional:
- GEO entity type:
series(GSE),sample(GSM),platform(GPL), ordataset(GDS) - organism filter (e.g.,
"Homo sapiens"[Organism]) - experiment type filter (e.g.,
"Expression profiling by high throughput sequencing"[DataSet Type]) - date range:
mindate/maxdateinYYYY/MM/DD - maximum results (
retmax, default 20) - output format:
json,xml, orsoft - output directory
- GEO entity type:
Workflow
- Determine the NCBI database:
GSE,GSM,GPL→geo(useesearch -db geo)GDS→gds(useesearch -db gds)- For most keyword searches, use
gdswhich indexes curated datasets and series.
- Build the query string with field tags when helpful:
- organism:
"Homo sapiens"[Organism] - data type:
"Expression profiling by high throughput sequencing"[DataSet Type] - platform:
GPL570[Platform] - publication:
<PMID>[PubMed ID]
- organism:
- Run
esearch -db gds -query "<term>" | esummary -format jsonto retrieve series metadata. - For a known GSE accession, fetch metadata via the GEO accession API:
https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=<GSE>&targ=self&form=text&view=brief - To enumerate all samples in a series:
esearch -db gds -query "GSE12345[Accession]" | elink -target geosamples | esummary- Or fetch the series matrix from
ftp://ftp.ncbi.nlm.nih.gov/geo/series/
- Parse metadata to extract: accession, title, organism, type, sample count, platform, publication PMID, submission date, supplementary file URLs.
- Report a summary table and, if requested, supplementary download links.
Output Contract
- Search query used (exact E-utilities command or API URL)
- Number of hits found
- Summary table with columns: Accession (GSE), Title, Organism, Type, Samples (#), Platform, PMID, Date
- List of GSM sample accessions for a queried series
- FTP/HTTPS links to raw data (supplementary files, series matrix) when available
- Saved output files when an output directory is provided:
esearch.jsonesummary.jsonsamples.txt(one GSM per line, for series-level queries)
Limits
- This skill depends on live access to
https://eutils.ncbi.nlm.nih.gov/entrez/eutils/andhttps://www.ncbi.nlm.nih.gov/geo/. - NCBI rate limit: 3 requests/second without API key, 10/second with API key.
- GEO
gdsdatabase indexes curated GEO DataSets; not every GSE series becomes a GDS entry. - Supplementary raw data may be large; this skill returns metadata and links, not the data itself.
- Controlled-access GEO datasets (e.g., human genotype data) require dbGaP authorization.
- The
SOFTformat is the canonical GEO text format; XML and JSON are available via E-utilities summary. - Common failure cases:
- querying the
geodatabase instead ofgdsfor series-level searches (usegdsfor keyword search) - confusing GSE (series) with GDS (curated dataset) — not all GSEs have a GDS entry
- expecting
retmode=jsonforefetchon GEO (onlySOFTand XML are supported byefetch) - missing sample-level detail because only the series summary was fetched
- querying the
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

