Generated banner for Train Sentence Transformers
Generated logo for Train Sentence Transformers

Train Sentence Transformers

Hugging FaceOfficialPublished by Hugging Face

  • Skill
  • Workflow
  • Data and AI
  • Apache-2.0
  • Medium risk
  • Has scripts

From the author

Train or fine-tune sentence-transformers models across `SentenceTransformer` (bi-encoder, dense or static embedding model for retrieval, similarity, clustering, classification, paraphrase mining, dedup, multimodal), `CrossEncoder` (reranker, pair scoring for two-stage retrieval / pair classification), `SparseEncoder` (SPLADE, sparse embedding model for learned-sparse retrieval), and `MultiVectorEncoder` (ColBERT / late-interaction, per-token embeddings scored with MaxSim). Covers loss selection, hard-negative mining, evaluators, distillation, LoRA, Matryoshka, and Hugging Face Hub publishing. Use for any sentence-transformers training task.
— the description by Hugging Face

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a standardized approach to training various embedding and ranking models using the sentence-transformers framework. It acts as a routing system that directs users to specific production templates and technical references based on the chosen model architecture. The workflow covers the entire lifecycle from model selection and data preparation to loss function configuration, evaluation, and publishing to the Hugging Face Hub.

What it does

  • Routes users to appropriate training templates for bi-encoders, cross-encoders, sparse encoders, and multi-vector encoders.
  • Provides technical references for loss functions, evaluators, and model architectures.
  • Offers guidance on hard-negative mining and dataset formatting for training.
  • Includes instructions for hardware-specific configurations and Hugging Face Hub integration.
  • Defines mandatory script requirements such as smoke testing, logging, and verdict reporting.

When to use it

  • When you need to train or fine-tune a sentence-transformers model for retrieval, similarity, or ranking tasks.
  • When you are unsure which model architecture (e.g., bi-encoder vs. cross-encoder) is best suited for your specific use case.
  • When you require a structured, repeatable process for training and evaluating embedding models.
  • When you need to integrate advanced training techniques like distillation, LoRA, or Matryoshka embeddings.

Advantages

  • Enforces consistent training practices through standardized production templates.
  • Reduces common errors by providing specific references for loss-to-data-shape mapping.
  • Facilitates systematic experimentation with built-in logging and verdict reporting.
  • Supports a wide range of model types including modern late-interaction and sparse architectures.

Usage examples

“I need to train a bi-encoder for semantic search on my internal documentation.”
The agent will identify the [SentenceTransformer] type, provide the relevant loss and evaluator references, and guide you to the bi-encoder production template.
“How do I implement a two-stage retrieval system using a reranker?”
The agent will direct you to the [CrossEncoder] documentation and template, explaining how to use it to score pairs for two-stage retrieval.
“I want to train a SPLADE model for sparse retrieval.”
The agent will provide the [SparseEncoder] references, including the required SpladeLoss wrapper and specific evaluators for sparse retrieval.
“How can I improve my retrieval model using hard negatives?”
The agent will guide you to the hard-negative mining script and explain how to generate n-tuple datasets for training.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/huggingface/train-sentence-transformers/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip train-sentence-transformers.zip -d .agents/skills

Documentation by Hugging Face

Train a sentence-transformers Model

This SKILL.md is a router, not a manual. It tells you which references and example scripts to load for your task. The actual content (recommended losses, evaluators, training-script structure, model selection, training-arg knobs, troubleshooting) lives in references/ and scripts/.

Do not synthesize a training script from this file alone. Open the per-type production template (scripts/train_<type>_example.py) and copy it as your starting point. The templates contain load-bearing scaffolding (autocast helper, model-card class, logger silencing list, force=True, seed, TF32, version-compatible imports, named-evaluator metric handling) that prior agent runs have repeatedly missed when rolling their own from a synthesized snippet.

1. Identify the model type

TagClassWhat it doesWhen to pick
[SentenceTransformer]SentenceTransformer (bi-encoder)Maps each input to a fixed-dim dense vectorRetrieval, similarity, clustering, classification, paraphrase mining, dedup
[CrossEncoder]CrossEncoder (reranker)Scores (query, passage) pairs jointlyTwo-stage retrieval (rerank top-100 from bi-encoder), pair classification
[SparseEncoder]SparseEncoder (SPLADE)Sparse vectors over the vocabularyLearned-sparse retrieval, inverted-index backends (Elasticsearch / OpenSearch / Lucene)
[MultiVectorEncoder]MultiVectorEncoder (ColBERT)One embedding per token, scored with MaxSimLate-interaction retrieval, recall gains over bi-encoders at higher storage cost, multimodal (ColPali / ColQwen2)

Tiebreakers when the request is ambiguous: "embedding model" / "vector search" / "similarity" → [SentenceTransformer]. "rerank" / "ranker" / "two-stage" → [CrossEncoder]. "SPLADE" / "sparse" / "inverted index" → [SparseEncoder]. "ColBERT" / "late interaction" / "multi-vector" / "MaxSim" / "ColPali" / "ColQwen" → [MultiVectorEncoder]. If still unclear, ask.

2. Required reading

Read these in full before writing any code. Do not triage by perceived relevance.

Per-type: always required

[SentenceTransformer]

  • references/losses_sentence_transformer.md: loss-to-data-shape mapping, BatchSamplers.NO_DUPLICATES requirement for MNRL-family, Cached* ↔ gradient_checkpointing incompatibility.

  • references/evaluators_sentence_transformer.md: evaluator-to-task mapping, metric_for_best_model key construction (named vs unnamed), per-evaluator primary_metric values.

  • references/model_architectures.md: encoder vs decoder vs static vs Router pipelines, pooling rules (mean / cls / lasttoken), auto-mean-pooling behavior for fresh-start MLM bases.

  • scripts/train_sentence_transformer_example.py: production template. Copy this as your starting point.

[CrossEncoder]

  • references/losses_cross_encoder.md: pointwise / pairwise / listwise / distillation, pos_weight derivation, activation_fn=Identity() mandatory for non-BCE losses (silent eval-rank collapse otherwise).

  • references/evaluators_cross_encoder.md: CrossEncoderRerankingEvaluator recipe, named-evaluator key format eval_{name}_{primary_metric}.

  • scripts/train_cross_encoder_example.py: production template. Copy this as your starting point.

[SparseEncoder]

  • references/losses_sparse_encoder.md: SpladeLoss wrapper requirement, FLOPS regularizer weights, smoke-test active-dim ramp behavior.

  • references/evaluators_sparse_encoder.md: SparseNanoBEIREvaluator (English-only) and the in-domain alternative, eval_{name}_{primary_metric} key format.

  • scripts/train_sparse_encoder_example.py: production template. Copy this as your starting point.

[MultiVectorEncoder]

  • references/losses_multi_vector_encoder.md: MaxSim scoring, scale choice per scoring mode (scale=1.0 for MaxSim, roughly the average query length for MeanMaxSim), MNRL / CachedMNRL / MarginMSE / DistillKLDiv, XTR-vs-ColBERT scoring, CachedMNRL ↔ gradient_checkpointing incompatibility.

  • references/evaluators_multi_vector_encoder.md: MultiVectorNanoBEIREvaluator (English-only) and the in-domain alternative, eval_NanoBEIR_mean_maxsim_ndcg@10 key format, distillation-eval spearman variant.

  • scripts/train_multi_vector_encoder_example.py: production template. Copy this as your starting point.

Cross-cutting: always required (regardless of task)
  • references/training_args.md: TrainingArguments knobs, precision rules (load fp32 + autocast bf16/fp16, never torch_dtype=bfloat16), warmup_steps (float) vs deprecated warmup_ratio, save_steps must be a multiple of eval_steps for load_best_model_at_end, schedulers, HPO, tracker, resume, hub-push variants.

  • references/dataset_formats.md: column-matching rules (label name auto-detection, column-order-not-name), reshaping recipes, hard-negative mining options.

  • references/base_model_selection.md: discovery commands, per-type model namespaces, ModernBERT-family max_seq_length=8192 trap, datasets >= 4 script-loader rejection, non-English starting-point shortcuts.

  • references/troubleshooting.md: symptom-indexed failure recipes. Skim the section headings on every run, even a healthy one. The "Metrics don't improve" and "Hub push fails" entries cover bugs that bite frequently and are cheaper to recognize before they fire than to debug after.

Cross-cutting: load when applicable
  • references/hardware_guide.md: VRAM sizing, multi-GPU, FSDP / DeepSpeed, HF Jobs flavors. Required for >24GB models, multi-GPU, or HF Jobs runs.

  • references/hf_jobs_execution.md: required when running on HF Jobs.

  • references/prompts_and_instructions.md: required when using prompt-tuned bases (E5, BGE, GTE, Qwen3-Embedding, Instructor, Nomic, etc.) or adding query: / passage: style prefixes.

Variant scripts (open when the task matches)
  • [SentenceTransformer] scripts/train_sentence_transformer_<matryoshka|multi_dataset|with_lora|distillation|make_multilingual|static_embedding>_example.py.

  • [CrossEncoder] scripts/train_cross_encoder_<distillation|listwise>_example.py.

  • [SparseEncoder] scripts/train_sparse_encoder_distillation_example.py.

  • Hard-negative mining CLI: scripts/mine_hard_negatives.py.

3. Defaults

Override only if the user specifies otherwise:

  • Local execution. Pitch HF Jobs only if local hardware can't fit the job.

  • Single run. After it completes, propose experimentation if the user would benefit (weak/marginal verdict, "see how high you can push it" framing, etc.). Iteration rules in references/training_args.md (Experimentation section).

  • Public Hub push at end-of-run, wrapped in try-except. On HF Jobs (ephemeral env) ALSO enable in-trainer push (push_to_hub=True + hub_strategy="every_save"). Details in references/hf_jobs_execution.md.

4. Constraints the produced script must satisfy

These are non-negotiable contracts. Implementation lives in the production templates and references. Do not reinvent.

  • Capture the pre-training evaluator score as baseline_eval before trainer.train().

  • Emit a single end-of-run line: VERDICT: WIN|MARGINAL|REGRESSION | score=... | baseline=... | delta=.... A monitor scrapes for this.

  • Silence httpx, httpcore, huggingface_hub, urllib3, filelock, fsspec to WARNING (otherwise HF download URLs flood the agent's context).

  • Tee logs to logs/{RUN_NAME}.log.

  • End with model.push_to_hub(...) wrapped in try/except.

  • Smoke-test before any long run (max_steps=1 + tiny dataset slice). The production templates show one common pattern (SMOKE_TEST env var).

  • [CrossEncoder] Include EarlyStoppingCallback(patience>=3). CE rerankers often peak mid-training and regress.

  • [SparseEncoder] Log query_active_dims / corpus_active_dims on the verdict line. High nDCG with collapsed sparsity is not a win. The keys come back name-prefixed (e.g. ..._query_active_dims). Use suffix matching to pluck them. See the SPARSE production template for the exact pattern.

  • [MultiVectorEncoder] Match scale to the scoring mode on any MNRL-family loss: near 1.0 for unnormalized MaxSim (do not copy scale=20.0 from bi-encoder MNRL), roughly the average query length with length-normalized MeanMaxSim, since each score is divided by its query's token count. XTRScores is a train-only similarity_fct: the evaluators reject it, so evaluation always scores with MaxSim, including for XTR-trained models.

5. Workflow

  1. Identify the model type (§1). Ask if ambiguous.

  2. Load the §2 required-reading files for that type.

  3. Open scripts/train_<type>_example.py and copy it as your starting point.

  4. Replace MODEL_NAME, DATASET_NAME, RUN_NAME, the loss, and the evaluator with the user's task. Cross-check loss/data-shape match against references/losses_<type>.md. Cross-check the metric_for_best_model key against references/evaluators_<type>.md (named evaluators format the key as eval_{name}_{primary_metric}).

  5. Smoke-test (max_steps=1).

  6. Run.

  7. After the run, append to logs/experiments.md and propose iteration if the verdict is weak/marginal.

Prerequisites

pip install "sentence-transformers[train]>=5.0"        # add [train,image] / [audio] / [video] for [SentenceTransformer] multimodal
                                                       # [MultiVectorEncoder] requires >=6.0
pip install trackio                                    # optional tracker (or wandb / tensorboard / mlflow)
hf auth login                                          # or set HF_TOKEN with write scope (for Hub push)

GPU strongly recommended. CPU works only for demos and [SentenceTransformer] StaticEmbedding.

Files

references/losses_multi_vector_encoder.md

Multi-Vector-Encoder Losses (ColBERT / late-interaction)

All losses live in sentence_transformers.multi_vector_encoder.losses.

Multi-vector models emit one embedding per token and score (query, document) via MaxSim (for each query token, take the max similarity to any document token, then sum across query tokens). This is fundamentally different from single-vector cosine, which changes what "temperature" means: MaxSim is an unbounded sum over query-token similarities, so for it a scale near 1.0 makes sense. The default scale=1.0 (temperature=1.0) is correct for unnormalized MaxSim: do not copy scale=20.0 from bi-encoder MNRL. With MeanMaxSim scoring (similarity_fct=mean_colbert_scores, and set model.similarity_fn_name = "meanmaxsim" so evaluation matches), each score is divided by its query's token count, so a scale of roughly the average length is a reasonable start, although some works use larger scales.

Top-line decision table

You haveUse
(anchor, positive) or (anchor, positive, negative) tripletsMultiVectorMultipleNegativesRankingLoss
Same, want effective batch size of 128+CachedMultiVectorMultipleNegativesRankingLoss
Cross-encoder teacher scores, (query, positive, negative, score_diff)MultiVectorMarginMSELoss
Listwise distillation (query, [doc_1..doc_N], scores)MultiVectorDistillKLDivLoss

Hard-negative mining is essential for competitive results, because random in-batch negatives leave a lot on the table for late-interaction models. See dataset_formats.md (Hard-negative mining section) and ../scripts/mine_hard_negatives.py.

Contrastive losses

MultiVectorMultipleNegativesRankingLoss

The default late-interaction contrastive loss. In-batch positives plus explicit hard negatives, scored with MaxSim (or XTR).

from sentence_transformers.multi_vector_encoder.losses import MultiVectorMultipleNegativesRankingLoss

loss = MultiVectorMultipleNegativesRankingLoss(model=model)  # scale=1.0 (temperature=1.0) is the correct default
  • Data: (anchor, positive) or (anchor, positive, negative_1, ..., negative_n). The collator stamps each column's task (column 0 becomes query, others become document). Pass task=... on a column to override.

  • Set batch_sampler=BatchSamplers.NO_DUPLICATES on training args (same reason as bi-encoder MNRL).

  • similarity_fct=colbert_scores by default. Pass XTRScores(top_k=...) for the sparser XTR-style scoring (from sentence_transformers.multi_vector_encoder.scoring). XTR applies to training only: evaluation always scores with MaxSim (see Gotchas).

  • scale=1.0 (temperature=1.0) matches PyLate and is correct for unnormalized MaxSim. Do NOT copy scale=20.0 from bi-encoder MNRL. With MeanMaxSim (similarity_fct=mean_colbert_scores), raise the scale to roughly the average query length instead, which is the same objective at the same strength.

CachedMultiVectorMultipleNegativesRankingLoss

GradCache variant: chunked embedding forward, cached gradients, and a second re-embedding pass. Decouples per-device batch size from effective in-batch negatives.

loss = CachedMultiVectorMultipleNegativesRankingLoss(
    model=model,
    mini_batch_size=8,           # or use mini_batch_num_tokens=... for token-budgeted packing
    score_mini_batch_size=4,     # optional, smaller trims the transient (Q, Q*N, q_tok, d_tok) buffer
)
  • Incompatible with gradient_checkpointing=True (same as every Cached* loss).

  • mini_batch_num_tokens=N packs sequences until N real tokens per mini-batch instead of a fixed mini_batch_size. Big win on variable-length data with flash-attention / input flattening.

  • score_mini_batch_size chunks the SCORING phase (which builds (Q, Q*N, q_tokens, d_tokens) intermediates) independently from the embedding phase. Drop it first when hitting OOM in the loss stage.

  • chunk_elements is the second lever on that same phase, and it cuts the other axis: score_mini_batch_size chunks queries, chunk_elements chunks documents inside each MaxSim call. Pass it through the scorer, e.g. similarity_fct=partial(colbert_scores, chunk_elements=1_000_000). Scores and gradients are unchanged (it is a pure memory knob), and it composes with score_mini_batch_size.

  • gather_across_devices=True gathers document embeddings across DDP ranks. Enables cross-rank in-batch negatives.

Distillation losses

Distillation is where multi-vector models learn most efficiently: cross-encoder teachers (e.g. gte-modernbert-base) score (query, doc) pairs offline, and the student MaxSim model regresses to that signal.

For the standard MS MARCO KD format (LightOn's ms-marco-en-bge and similar: (query_id, document_ids, scores) with separate queries / documents splits), you can use sentence_transformers.util.resolve_ids to join the IDs against the text splits at load time. It's a factory that returns a batched transform: pass a mapping from each input ID column to its lookup dataset, e.g. dataset.set_transform(resolve_ids({"query_id": queries, "document_ids": documents}, max_list_length=32)) (lazy, no caching) or via dataset.map(..., batched=True, remove_columns=["query_id", "document_ids"]) (eager, cached: map keeps input columns unless told to drop them, so pass the ID columns to remove_columns), yielding (query, document_1, ..., document_32, scores) rows ready for MultiVectorDistillKLDivLoss. The same mapping shape covers triplets with IDs ({"query_id": queries, "positive_id": documents, "negative_id": documents}) and ID-only contrastive datasets without a scores column.

MultiVectorMarginMSELoss

Regress the margin between positive and negative MaxSim scores against the teacher's margin.

loss = MultiVectorMarginMSELoss(model=model)
  • Data: (query, positive, negative, score_diff) where score_diff = teacher_score(query, positive) - teacher_score(query, negative). Raw teacher scores [score(q, pos), score(q, neg_1), ...] also work, converted to margins internally.

  • Popular recipe from PyLate / colpali-engine.

  • Teacher scores are precomputed once, stored as the label column. The loss does not run the teacher inline.

  • Same similarity_fct convention as the other losses, but pairwise-shaped: defaults to colbert_scores_pairwise, or pass xtr_scores_pairwise for XTR.

MultiVectorDistillKLDivLoss

Listwise KL-div: student's softmax distribution over N candidates should match the teacher's.

loss = MultiVectorDistillKLDivLoss(model=model)
  • Data: (query, document_1, ..., document_N, scores) where scores is a list of N teacher scores per row. One column per candidate document (the standard positional multi-column convention), and the label column must use a recognized name (label, labels, score, scores). resolve_ids expands a stored ID list into the numbered columns.

  • Stronger training signal than MarginMSE when you have full N-way teacher scores (not just positive/negative margins).

  • similarity_fct defaults to colbert_kd_scores, the listwise KD variant, not the colbert_scores used by the MNRL family. XTRKDScores is the XTR counterpart.

  • temperature softens both distributions before the softmax, and can be overridden per side with student_temperature / teacher_temperature. Set teacher_temperature from the spread of your teacher's scores rather than from a value copied out of a paper: a float32 softmax underflows to exact zeros once a row's spread divided by the temperature exceeds about 100, and every candidate that underflows drops out of the KL, which is the ranking information you are distilling. Sharpening student_temperature far below the student's own score spread collapses that side too, and once both are one-hot the loss and its gradient are exactly zero. Start at 1.0 / 1.0 and only move a side you have a measured reason to move.

  • The loss is scaled by the student temperature squared, which keeps gradient magnitudes comparable only for a shared temperature at or above 1.0 (the regime Hinton et al. cover). Below that the factor shrinks the loss instead, by 1e-6 at student_temperature=0.001: when combining KD with a contrastive loss, scale the KD weight back up accordingly.

  • OOM: drop per_device_train_batch_size first and raise gradient_accumulation_steps to hold the effective batch. Only reduce N (candidate-list length) as a last resort, since lowering N changes the experiment.

Data-shape gotchas

  • Column 0 is always the query. Losses call self.model(sf, task="query" if idx==0 else "document"). Use the collator's router_mapping to override if you need a non-standard column layout.

  • Cross-column varlen T is handled: the batch's positive and negative columns can have different token counts (Qwen2-VL family etc.). stack_padded_token_embeddings pads to the per-batch max before MaxSim.

  • Mask flow: MVE reads the SCORING mask from the model OUTPUT dict (MultiVectorMask rewrites the input mask). Custom loss code that reads sentence_features[i]["attention_mask"] directly instead of outputs[i]["attention_mask"] will silently score against skiplisted tokens.

Gotchas

  • scale=20.0 copied from bi-encoder MNRL: misscaled for the unnormalized MaxSim sum. Keep scale=1.0 there. Only length-normalized MeanMaxSim wants a larger scale, roughly the average query length.

  • Missing Normalize at the token level in the pipeline: colbert_scores assumes L2-normalized token embeddings. If your custom pipeline drops the token-level Normalize, either add one or pass normalize_embeddings=True semantics via a wrapper.

  • CachedMultiVectorMultipleNegativesRankingLoss + gradient_checkpointing=True: crash. Pick one.

  • MultiVectorMarginMSELoss without precomputed score_diff: label column must be populated from a teacher pass ahead of training. The loss does not compute the teacher inline.

  • Expecting XTR scoring at eval: XTRScores is a train-only similarity_fct. XTR takes its top-k across the whole candidate set, so a (query, document) pair has no standalone score, which means it cannot be the model's similarity_fn_name and the evaluators reject it outright. Evaluation and inference score with MaxSim, also for XTR-trained models. That is by design, not a mismatch to fix. To score a fixed candidate set ad hoc, call xtr_scores directly.

  • Distillation with a weak teacher: multi-vector students easily match a small-model teacher and then plateau. Use a strong cross-encoder (e.g. gte-modernbert-base, mxbai-rerank-large-v2) for the teacher pass.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Medium risk

  • Instructions that use the network
  • Downloads piped into a shell
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Hugging Face
Publisher
Hugging Face (Official)
Source
huggingface/skills · skills/train-sentence-transformers · commit 25910b3
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Hugging Face or Hugging Face.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download train-sentence-transformers.zip