single-cell-foundation-model-geneformer
Skill1.1k starsChanged 8 months agoMITView on GitHub
Use this skill when a task involves Geneformer workflows, especially TranscriptomeTokenizer input preparation, tokenized `.dataset` generation, cell or gene classification with `Classifier`, embedding extraction with `EmbExtractor`, and in silico perturbation analysis with `InSilicoPerturber`.
Trending
Quiet this year.thin dataabout the whole repository
Who's talking about PharMolix/OpenBioMed
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
In this repository45 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- admet-predictionSkill
- antibody-design-iggmSkill
- antibody-structure-prediction-tfoldSkill
- binding-affinity-prediction-prodigySkill
- biomedical-literature-searchSkill
- biomed-skill-creatorSkill
- biomed-skill-routerSkill
- cellxgene-census-querySkill
- chembl-querySkill
- disease-drug-intelligenceSkill
- drug-candidate-discoverySkill
- drug-drug-interaction-analysisSkill
- drug-lead-analysisSkill
- functional-protein-designSkill
- iupac-name-identification-biot5Skill
- kegg-querySkill
- molecule-biochemical-significance-query-biot5Skill
- mutation-design-aavSkill
- mutation-design-gfpSkill
- ppi-string-querySkill
- protein-function-predictionSkill
- protein-ligand-binding-analysis-plipSkill
- protein-mutation-analysisSkill
- protein-structure-design-boltzgenSkill
- protein-subcellular-localization-prediction-biot5Skill
- pubchem-querySkill
- retrosynthesis-planningSkill
- similar-protein-retrievalSkill
- single-cell-atac-seq-peak-calling-annotaionSkill
- single-cell-atac-seq-qc-processingSkill
- single-cell-foundation-model-langcellSkill
- single-cell-foundation-model-scgptSkill
- single-cell-multi-omics-analysis-scviSkill
- single-cell-multi-omics-data-harmonizationSkill
- single-cell-proteomics-data-processingSkill
- single-cell-proteomics-peptide-identificationSkill
- single-cell-scrna-seq-analysis-scanpySkill
- single-cell-foundation-model-stofmSkill
- spatial-transcriptomics-spatial-data-ioSkill
- structure-prediction-boltz-2Skill
- target-based-lead-designSkill
- target-drug-reportSkill
- text-based-molecule-editingSkill
- uniprot-querySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this skill when the task involves official Geneformer workflows such as:
- Very specific: line 29
Check that ensembl_id and n_counts are available.
- Very specific: line 37
Use TranscriptomeTokenizer first for almost every Geneformer workflow.
- Very specific: line 60
Use EmbExtractor when the task is to:
- Very specific: line 68
Use InSilicoPerturber for zero-shot or model-based perturbation analyses such as:
- Distinctive: line 79
Do not pass feature-selected matrices into the tokenizer.
- Very specific: line 80
Do not use gene symbols where the tokenizer expects ensembl_id.
- Very specific: line 81
Do not confuse tokenized .dataset files with AnnData objects.
- Distinctive: line 82
Do not skip tokenization and jump directly to classifiers or perturbation APIs.
≈ “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
Geneformer
Use This Skill When
Use this skill when the task involves official Geneformer workflows such as:
- converting raw scRNA-seq data into Geneformer tokenized datasets
- fine-tuning Geneformer for cell or gene classification
- extracting cell or gene embeddings
- generating state embeddings for downstream perturbation analysis
- running in silico perturbation or in silico treatment style analyses
- distinguishing pretrained zero-shot usage from fine-tuned classifier usage
This skill is for Geneformer-specific workflows, not generic single-cell model use.
Start Here
- Confirm the input is raw-count scRNA-seq data and still suitable for tokenization.
- Check that
ensembl_idandn_countsare available. - Tokenize first unless the user already has a Geneformer
.dataset. - Decide whether the task is classification, embedding extraction, or in silico perturbation.
Choose A Path
Tokenization
Use TranscriptomeTokenizer first for almost every Geneformer workflow.
This step converts raw-count .loom or .h5ad data into tokenized datasets
used by the downstream APIs.
Geneformer expects:
- row attribute
ensembl_id - cell attribute
n_counts
Optional metadata can be passed through during tokenization.
Classification
Use Classifier for:
- cell state classification
- cell type annotation
- gene classification tasks
The input is a tokenized Geneformer .dataset object, not raw AnnData.
Embedding extraction
Use EmbExtractor when the task is to:
- extract CLS, cell, or gene embeddings
- plot or inspect cell embeddings
- generate state embeddings for later perturbation analysis
In silico perturbation
Use InSilicoPerturber for zero-shot or model-based perturbation analyses such as:
- deleting or shifting genes
- modeling start and goal cell states
- ranking perturbations by movement toward a desired cell state
This is one of Geneformer's defining workflows and should be treated as more than ordinary classifier inference.
Guardrails
- Do not pass feature-selected matrices into the tokenizer; the docs expect raw counts without feature selection.
- Do not use gene symbols where the tokenizer expects
ensembl_id. - Do not confuse tokenized
.datasetfiles with AnnData objects. - Do not skip tokenization and jump directly to classifiers or perturbation APIs.
- For perturbation tasks, be explicit about model type, embedding mode, and target cell states.
Official Workflow Surface
| Component | Use |
TranscriptomeTokenizer | create tokenized datasets |
Classifier | fine-tune cell or gene classifiers |
MTLClassifier | multitask cell classification |
EmbExtractor | extract and summarize embeddings |
InSilicoPerturber | simulate perturbations / treatment directions |
Read More Only If Needed
- For operational usage and required input fields, read
references/workflows.md. - For official source locations and model-specific notes, read
references/sources-and-notes.md.
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.

