fastembed

Generate local dense text embeddings with ONNX Runtime for semantic search.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill fastembed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fastembed
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/fastembed
Command: npx skills add https://github.com/antonyfmunoz/OS --skill fastembed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves slow, dependency-heavy embedding generation by providing a lightweight way to convert text into vectors locally for semantic search and matching.

Core Features & Use Cases

  • Dense text embeddings (CPU-friendly): Convert large volumes of text into fixed-size vectors using ONNX Runtime without GPUs.
  • Batch embedding at scale: Embed thousands of documents efficiently with configurable batching and parallelism.
  • Query vs document workflows: Support symmetric and asymmetric retrieval patterns for similarity search and skill matching.
  • EOS-ready integration patterns: Supports an EOS-style three-tier flow (FastEmbed local, optional cloud fallback, keyword fallback) to keep retrieval working even when embeddings fail.

Real-world example: You maintain a catalog of skills and notes inside your system, and you want an AI to automatically select the most relevant skill or retrieve the most similar past interactions based on a user’s task description.

Quick Start

Use the fastembed tool to embed your task description and compare it against pre-embedded skill vectors for semantic retrieval.

Frequently Asked Questions about fastembed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate local text embeddings for semantic search without a GPU?

You can generate local text embeddings without a GPU by using CPU-optimized ONNX Runtime to convert input text into dense vectors. This approach supports batch processing and configurable parallelism for semantic search and knowledge retrieval workflows.

What is the best way to embed thousands of documents for similarity comparison on a local machine?

The best way to embed thousands of documents locally is using batch processing with configurable batch size and parallelism. This method efficiently converts large text volumes into fixed-size vectors for similarity comparison without heavy dependencies.

Can I use CPU-optimized vectorization for pgvector skill matching workflows?

Yes, you can use CPU-optimized vectorization for pgvector skill matching by generating dense vector embeddings locally. You must ensure consistent model dimensions when storing and comparing vectors in your database for accurate retrieval.

How does query vs document embedding work for asymmetric retrieval patterns?

Query vs document embedding for asymmetric retrieval works by converting both query text and document text into fixed-size vectors. These vectors are then compared using similarity metrics to retrieve the most relevant documents for a given query.

Do I need cloud APIs to run vectorization for knowledge retrieval pipelines?

No, you do not need cloud APIs to run vectorization for knowledge retrieval pipelines. You can generate dense vectors entirely locally using ONNX Runtime, with optional cloud and keyword fallbacks to maintain retrieval continuity if embedding generation fails.