Codonfm Embed logo

Codonfm Embed

OrganizationPopular
NVIDIA
codonfm-embed

Validate coding-sequence CSVs, extract public CodonFM/Encodon embeddings, and choose checkpoints for downstream property modeling.

Overview

PublisherNVIDIA
Repositoryskills
Skill namecodonfm-embed
Stars
3.6K
Forks
435
Bundled files
12
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 12 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by NVIDIA on GitHub. Read the source before you install it.

Installation

Install the Codonfm Embed AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/NVIDIA/skills/tree/main/skills/bionemo-codonfm-embed
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/NVIDIA/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/bionemo-codonfm-embed .claude/skills/codonfm-embed
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Codonfm Embed in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Codonfm Embed on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Codonfm Embed is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Extract public Encodon embeddings

Purpose

Extract one frozen CLS vector per coding sequence with public Encodon v1. Support input validation, command preparation, extraction, and checkpoint selection for translation efficiency, expression, or mRNA stability modeling. Extraction does not automatically train a downstream regressor.

Prerequisites

  • Validation needs Python 3 standard library only; no GPU, weights, or API key.
  • Execution needs the public CodonFM checkout, its requirements.txt environment, a compatible NVIDIA GPU, and local checkpoint weights. A metadata JSON is not a checkpoint. A .safetensors file needs its sibling config.json; .ckpt checkpoints are also supported by the public loader.
  • Run python -m src.runner from the CodonFM repository root. In an isolated workspace, use supplied source artifacts; source paths below are relative to that checkout or source archive, not this skill directory.

Inputs

Input source precedence: explicit user prompt arguments, then supplied files/checkpoint metadata, then inspected public runner defaults. Resolve conflicting model names and checkpoint metadata before execution. Supplied 80M metadata is useful for preparing an 80M command; it does not restrict an open-ended recommendation to that size.

Required for validation: a CSV. Required for extraction: the CSV, checkpoint, matching model name, and output directory. Optional: context length and batch size overrides. Checkpoint-selection questions can be answered without a CSV.

InputRequirement or default
Sequence CSVColumns id, ref_seq, value, split; extra columns allowed
idNonblank, unique IDs for unambiguous output association
ref_seqCoding sequence, uppercase DNA A/C/G/T, length divisible by three; public dataset converts uppercase U to T
valueNumeric label; use 0.0 for new extraction-only data, preserve supplied labels
splitOnly exact test values enter extraction; blank/other values are excluded
Checkpoint and modelMatch weights/config to encodon_80m, encodon_600m, or encodon_1b
Context lengthPublic runner default 2048 tokens, including CLS and SEP
Output directoryA fresh run directory with an empty predictions directory

Instructions

  1. Choose the requested workflow. For a checkpoint/performance question, read checkpoint selection and answer from public benchmark evidence. For the strongest published downstream results, prefer the public 1B random-mask checkpoint when resources allow; 80M is a demonstration or resource-constrained choice. A small labeled set alone does not establish that 80M frozen features are better. Do not download weights or inspect the entire source tree just to make a recommendation.
  2. Inspect supplied source only where needed. Confirm runner/config, src/data/codon_bert_dataset.py, src/data/preprocess/codon_sequence.py, src/inference/encodon.py, or src/utils/pred_writer.py for the relevant behavior. Read ZIP members with zipfile.ZipFile.namelist() and .read(); source inspection does not need extraction. If a checkout is needed, use a new directory from tempfile.mkdtemp() or mktemp -d, without deleting or overwriting an existing directory. For Decodon support questions, inspect runner/config and model/inference modules, cite the inspected files, explain the missing public implementation, and finish there.
  3. Validate the CSV before running extraction. Run the bundled checker below with the intended context length. Report per-row verdicts using CSV row numbers as well as IDs, since IDs can repeat. Separate excluded rows, invalid inputs, duplicate-ID warnings, and truncation. Propose fixes without silently rewriting supplied data. The checker is a preflight, not model execution or proof of biological CDS validity.
  4. Deliver the requested preparation or execution. For preparation, return a complete command with resolved paths (or clearly identified prerequisites), the test-row count, validation findings, and the output contract below. Include all task/dataset/process flags in the final answer, even if already shown in a tool call. For extraction, reuse/download the chosen checkpoint when needed, execute once resources are ready, and verify the saved arrays. If resources are missing, finish preparation and state what is missing.

Available Scripts

ScriptPurposeArguments
validate_inputs.pyRead-only CSV validation and per-row verdictsRequired CSV path; optional --context-length (default 2048)

Run the preflight with Python; CODONFM_SKILL_DIR is the directory containing this file:

bash
python "$CODONFM_SKILL_DIR/scripts/validate_inputs.py" "$CODONFM_DATA_PATH" \
    --context-length 2048

The checker prints JSON. Exit 0 means no findings, 1 means row findings to review (including exclusions/warnings), and 2 means a file/schema error. Neither warnings nor exclusions imply that the public runner will crash.

Output Format

The checker emits JSON with total_rows, test_rows, excluded_rows, context_length, codon_limit, warnings, and rows. Each row records its one-based data-row number (excluding the header), ID, split, verdict, issues, sequence/value validity, and retained/lost codons. A file/schema error emits error and csv instead. These are preflight findings, not generated embeddings.

Examples

Set CODONFM_DATA_PATH to the CSV, CODONFM_CHECKPOINT_PATH to the weights, CODONFM_MODEL_NAME to the matching architecture, and CODONFM_RUN_DIR to a fresh output directory. Substitute actual paths in a prepared command:

bash
python -m src.runner eval \
    --task_type embedding_prediction \
    --process_item codon_sequence \
    --dataset_name CodonBertDataset \
    --exp_name embed_extract \
    --model_name "$CODONFM_MODEL_NAME" \
    --checkpoint_path "$CODONFM_CHECKPOINT_PATH" \
    --data_path "$CODONFM_DATA_PATH" \
    --context_length 2048 \
    --num_nodes 1 \
    --num_gpus 1 \
    --num_workers 0 \
    --val_batch_size 2 \
    --out_dir "$CODONFM_RUN_DIR" \
    --predictions_output_dir "$CODONFM_RUN_DIR/predictions"

For a low-cost demonstration, encodon_80m matches nvidia/NV-CodonFM-Encodon-80M-v1, revision 399ca9fe17b57941a7bebc6788033919b417413c, file NV-CodonFM-Encodon-80M-v1.safetensors and sibling config.json.

Outputs

  • Under --predictions_output_dir, embeddings_merged.npy contains frozen final-layer CLS vectors, shape (processed_rows, hidden_size).
  • ids_merged.npy is index-aligned: embedding row i belongs to ID row i. Use these IDs to join to the CSV; do not assume every CSV row was retained. Duplicate IDs make that join ambiguous even when extraction succeeds.
  • For the one-GPU example, verify both arrays have the expected test-row count, embeddings are finite, and width matches checkpoint config (1024 for 80M, 2048 for 600M/1B). Do not fabricate arrays for a preparation-only request.

The public checkout's downstream-model references are:

  • notebooks/4-EnCodon-Downstream-Task-riboNN.ipynb
  • notebooks/5-EnCodon-Downstream-Task-mRFP-expression.ipynb
  • notebooks/6-EnCodon-Downstream-Task-mRNA-stability.ipynb

Limitations

  • Public v1 has no Decodon model/inference implementation, Decodon notebooks, notebooks/te_predictor.py, or notebooks/mfe_predictor.py.
  • At context length 2048, retain the first 2046 codons; any remaining 3-prime sequence is lost. Increasing the flag does not validate a longer context. Disclose deliberate cropping or a separate chunking/aggregation strategy; neither is equivalent to embedding the complete sequence once.
  • --dryrun builds runtime configuration, may create directories, and needs ML dependencies; it reads neither the CSV nor the weights and is not input validation.
  • Do not claim a benchmark-trained regressor generalizes to a new organism, cell type, or assay without new labeled validation data.
  • Do not invoke this skill for a generic expression-prediction request that does not mention CodonFM or Encodon.

Troubleshooting

SymptomCause and action
Missing split columnEval requests the test split despite the dataset docstring calling this column optional; add an explicit split column to a corrected copy
Fewer output rowsBlank/non-test split values are silently filtered; set intended extraction rows to exact test in a corrected copy
Repeated output IDsDuplicate input IDs are not rejected; assign unique IDs while preserving a mapping to the original rows
Oversized sequencePreprocessing truncates at context_length - 2 codons; report retained/lost lengths and agree on a sequence-handling strategy
Missing weights or dependenciesComplete validation/command preparation; metadata and --dryrun do not substitute for weights
Merge failure on a repeated runThe writer scans .npy files; use a fresh predictions directory to avoid stale shards or merged arrays

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Codonfm Embed AI skill do?

Validate coding-sequence CSVs, extract public CodonFM/Encodon embeddings, and choose checkpoints for downstream property modeling.

Why use Codonfm Embed on TypingMind?

Because you install it once and use it with any model. Codonfm Embed is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Codonfm Embed in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/NVIDIA/skills/tree/main/skills/bionemo-codonfm-embed. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Codonfm Embed?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Codonfm Embed?

As many as you like. As long as a model supports skills, you can use Codonfm Embed with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Codonfm Embed AI skill free?

Yes. It is published on GitHub by NVIDIA under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇