This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Milvus Marketplace is a Claude Code skills marketplace for building AI applications in the data retrieval domain. It is not a traditional software project with source code — it is a structured collection of markdown-based skills, workflows, and code templates organized around the Milvus vector database.
The project is maintained by Zilliz and licensed under Apache 2.0.
marketplace.json → defines 7 plugins
├── plugins/core/ → pilot (controller) + atomic operators
├── plugins/rag-toolkit/ → RAG solutions (4 skills)
├── plugins/memory-system/ → Long-term memory (1 skill)
├── plugins/retrieval-system/ → Text search (4 skills)
├── plugins/multimodal-retrieval/ → Image/video/multimodal (4 skills)
├── plugins/rec-system/ → Recommendation (2 skills)
└── plugins/data-analytics/ → Data analysis (2 skills)
Core plugin (plugins/core/skills/): The pilot skill is the main controller that routes user requests. Other skills are atomic operators: embedding, chunking, indexing, rerank, ray, local-setup.
Scenario plugins: Pre-built solutions organized by use case:
| Plugin | Skills | Description |
|---|---|---|
rag-toolkit |
rag, rag-with-rerank, agentic-rag, multi-hop-rag | RAG and knowledge base solutions |
memory-system |
chat-memory | Long-term memory for chatbots |
retrieval-system |
semantic-search, filtered-search, hybrid-search, multi-vector-search | Text search variations |
multimodal-retrieval |
image-search, text-to-image-search, video-search, multimodal-rag | Image, video, and multimodal |
rec-system |
item-to-item, user-to-item | Recommendation systems |
data-analytics |
duplicate-detection, clustering | Data analysis patterns |
Each skill follows this pattern:
skills/<skill-name>/
├── SKILL.md # Main skill definition (YAML frontmatter + markdown)
├── verticals/ # Optional: vertical application guides
│ ├── <vertical>.md
│ └── ...
└── references/ # Optional: detailed reference docs (pilot only)
The YAML frontmatter in SKILL.md contains name and description fields used for skill discovery and trigger matching.
Scenarios are classified by architectural differences (different code structure/pipeline), not by industry. Variations that only differ in model/parameters are handled as verticals within the same scenario.
The pilot skill asks exactly two questions (data type + query type), then auto-routes to either:
- A matching scenario skill (if one fits)
- A combination of core operators (if no scenario matches)
| File | Purpose |
|---|---|
.claude-plugin/marketplace.json |
Root marketplace definition, lists all plugins |
plugins/<name>/.claude-plugin/plugin.json |
Plugin metadata |
All generated application code uses this stack — no user choice involved:
- Python — language
- FastAPI — API framework
- Ray — data processing
- uv — package management
- Milvus / Zilliz Cloud — vector storage
- New skill in existing category: Add directory under
plugins/<category>/skills/<skill-name>/with aSKILL.md - New core operator: Add directory under
plugins/core/skills/<operator-name>/with aSKILL.md - New vertical: Add
<vertical>.mdunder the relevant skill'sverticals/directory - New category plugin: Create
plugins/<category>/with.claude-plugin/plugin.jsonandskills/directory, then add tomarketplace.json - Update the routing table in
plugins/core/skills/pilot/SKILL.mdwhen adding new skills
- Ship 60% first, iterate to 80%: Skills should generate working code quickly, then offer optimization paths
- Don't let users choose tech stack: The pilot auto-selects models, storage, and index based on data characteristics
- Scenarios as cache: Pre-built solutions are reused directly when matched; only fall back to composing operators when no scenario fits