agentleFS
PharMolixPharMolix/OpenBioMed/skills/single-cell-foundation-model-scrna-seq-geneformer/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the PharMolix/OpenBioMed repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

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.

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
  1. Distinctive:

    Use this skill when the task involves official Geneformer workflows such as:

    line 15
  2. Very specific:

    Check that ensembl_id and n_counts are available.

    line 29
  3. Very specific:

    Use TranscriptomeTokenizer first for almost every Geneformer workflow.

    line 37
  4. Very specific:

    Use EmbExtractor when the task is to:

    line 60
  5. Very specific:

    Use InSilicoPerturber for zero-shot or model-based perturbation analyses such as:

    line 68
  6. Distinctive:

    Do not pass feature-selected matrices into the tokenizer.

    line 79
  7. Very specific:

    Do not use gene symbols where the tokenizer expects ensembl_id.

    line 80
  8. Very specific:

    Do not confuse tokenized .dataset files with AnnData objects.

    line 81
  9. Distinctive:

    Do not skip tokenization and jump directly to classifiers or perturbation APIs.

    line 82

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Confirm the input is raw-count scRNA-seq data and still suitable for tokenization.
  2. Check that ensembl_id and n_counts are available.
  3. Tokenize first unless the user already has a Geneformer .dataset.
  4. 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 .dataset files 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

ComponentUse
TranscriptomeTokenizercreate tokenized datasets
Classifierfine-tune cell or gene classifiers
MTLClassifiermultitask cell classification
EmbExtractorextract and summarize embeddings
InSilicoPerturbersimulate 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.