zeppelin

Store and retrieve text as 384-dimensional semantic vectors for similarity search.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/jcolano/loopColony --skill zeppelin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeppelin
Source: https://github.com/jcolano/loopColony/tree/main/TO-DO/X_DONE/X_DONE_loopcore_zeppelin_upgrade/zeppelin
Command: npx skills add https://github.com/jcolano/loopColony --skill zeppelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Provides a hosted vector search engine that removes the friction of storing, indexing, and retrieving text by semantic similarity or BM25 full-text ranking so users can build fast, production-ready semantic search over documents.

Core Features & Use Cases

  • Namespace management with server-generated UUIDs for isolated vector collections.
  • Text embedding via a hosted embed service, upsert of 384-dim vectors, and attribute-based filtering.
  • Vector nearest-neighbor search (ANN) and BM25 full-text ranking, with strong vs eventual consistency modes and S3-native segment compaction.
  • Use Case: embed and upsert product descriptions or documents, then run semantic queries and filtered searches to surface the most relevant items.

Quick Start

Create a 384-dimension namespace, embed your texts with the Embed API, upsert the returned vectors into that namespace, and run a similarity or BM25 query to retrieve top results.

Frequently Asked Questions about zeppelin

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

FAQPage Schema
How do I store and retrieve text using semantic embeddings for similarity search?

Store and retrieve text by encoding it into 384-dimensional semantic vectors via an embedding API, then upserting them into isolated namespaces to run nearest-neighbor or BM25 queries for fast document retrieval.

What is the difference between semantic vector search and BM25 full-text ranking?

Semantic vector search uses 384-dimensional embeddings to match meaning, while BM25 full-text ranking matches keyword relevance. You can run either query type against your stored documents to surface the most relevant items.

Can I use S3 for vector storage and compaction with semantic search?

Yes, S3-native manifests handle segment compaction and provide CAS safeguards. This enables strong versus eventual consistency modes for upsert and delete APIs managing your vector collections.

How do I filter results when running nearest-neighbor queries on stored embeddings?

You can apply attribute-based filtering to your upserted vectors. This allows you to restrict nearest-neighbor or BM25 query payloads to specific subsets of documents within a namespace.

Do I need to manage my own embedding model for 384-dimensional vector search?

No, the service uses a hosted embedding model, all-MiniLM-L6-v2, to generate 384-dimensional vectors. You simply embed your texts via the embed API and upsert the returned vectors into your namespace.

What is the best way to isolate different collections of vector search documents?

Use namespace management with server-generated UUIDs to create isolated vector collections. This keeps distinct document sets separate during upsert, compaction, and query operations.