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

single-cell-foundation-model-langcell

Skill1.1k starsChanged 8 months agoMITView on GitHub

Use this skill when a task involves the LangCell project for single-cell language-cell modeling, especially zero-shot cell type annotation, few-shot annotation, LangCell-CE finetuning, Geneformer-style tokenization, or preparing text descriptions for candidate cell identities and multimodal cell-text matching workflows.

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

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 8 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for the local LangCell project at /DATA/disk0/zhaosy/home/LangCell.

    line 15
  2. Distinctive:

    Do not use this skill for ordinary Scanpy analysis that does not depend on LangCell.

    line 25
  3. Distinctive:

    Check that the input is already tokenized, or route through preprocessing first.

    line 30
  4. Distinctive:

    Check whether the required external assets exist: checkpoints, tokenized dataset, ontology / text-description JSON.

    line 31
  5. Distinctive:

    Prefer the zero-shot path first if the user is exploring LangCell rather than benchmarking a supervised baseline.

    line 32
  6. Distinctive:

    Start here for most LangCell usage.

    line 38
  7. Very specific:

    Use LangCell-annotation-zeroshot/zero-shot.ipynb as the primary reference path.

    line 45
  8. Very specific:

    Use LangCell-annotation-fewshot/fewshot.py when only a tiny labeled support set is available and the user still wants the multimodal …

    line 49
  9. Very specific:

    Use LangCell-CE-annotation/finetune.py when the user wants a standard supervised classifier on top of the pretrained cell encoder.

    line 54
  10. Very specific:

    read AnnData with scanpy

    line 61
  11. Very specific:

    Do not claim raw .h5ad can be passed directly into LangCell inference.

    line 69
  12. Distinctive:

    Do not assume checkpoints live in the repo.

    line 70
  13. Distinctive:

    Do not treat zero-shot prediction as plain nearest-neighbor on cell embeddings.

    line 71
  14. Very specific:

    Do not assume label columns are named consistently.

    line 72
  15. Distinctive:

    If new cell types are needed, prepare textual descriptions carefully instead of inventing bare labels with no ontology context.

    line 73
  16. Very specific:

    Read references/local-usage.md for entry points, asset requirements, and practical checks.

    line 77
  17. Very specific:

    Read references/model-notes.md when the task depends on LangCell's multimodal design or paper-level motivation.

    line 78

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

LangCell

Use This Skill When

Use this skill for the local LangCell project at /DATA/disk0/zhaosy/home/LangCell. It is the right choice when the task involves:

  • zero-shot cell identity or cell type annotation from tokenized single-cell data
  • few-shot cell type annotation with very limited labels
  • finetuning only the LangCell cell encoder (LangCell-CE)
  • preprocessing AnnData into the tokenized format expected by LangCell
  • preparing text descriptions for candidate cell identities
  • understanding how LangCell combines cell embeddings and text embeddings

Do not use this skill for ordinary Scanpy analysis that does not depend on LangCell.

Start Here

  1. Confirm whether the user wants zero-shot annotation, few-shot annotation, or cell-encoder-only finetuning.
  2. Check that the input is already tokenized, or route through preprocessing first.
  3. Check whether the required external assets exist: checkpoints, tokenized dataset, ontology / text-description JSON.
  4. Prefer the zero-shot path first if the user is exploring LangCell rather than benchmarking a supervised baseline.

Choose A Path

Zero-shot annotation

Start here for most LangCell usage. The defining behavior is:

  • encode cells with cell_bert + cell_proj
  • encode candidate texts with text_bert + text_proj
  • score cell-text matches with ctm_head
  • combine similarity and matching scores for final predictions

Use LangCell-annotation-zeroshot/zero-shot.ipynb as the primary reference path.

Few-shot annotation

Use LangCell-annotation-fewshot/fewshot.py when only a tiny labeled support set is available and the user still wants the multimodal LangCell path.

LangCell-CE finetuning

Use LangCell-CE-annotation/finetune.py when the user wants a standard supervised classifier on top of the pretrained cell encoder.

Preprocessing

LangCell does not take raw .h5ad directly for these downstream scripts. First:

  • read AnnData with scanpy
  • add obs["n_counts"]
  • ensure var["ensembl_id"] exists
  • tokenize with LangCellTranscriptomeTokenizer
  • save with save_to_disk(...)

Guardrails

  • Do not claim raw .h5ad can be passed directly into LangCell inference; tokenization is required first.
  • Do not assume checkpoints live in the repo. The official repo expects external downloads.
  • Do not treat zero-shot prediction as plain nearest-neighbor on cell embeddings; the project combines similarity and cell-text matching.
  • Do not assume label columns are named consistently. The repo checks several alternatives such as celltype, cell_type, str_labels, and labels.
  • If new cell types are needed, prepare textual descriptions carefully instead of inventing bare labels with no ontology context.

Read More Only If Needed

  • Read references/local-usage.md for entry points, asset requirements, and practical checks.
  • Read references/model-notes.md when the task depends on LangCell's multimodal design or paper-level motivation.

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.