Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Specialized workflow for implementing RAG (Retrieval-Augmented Generation) systems including embedding model selection, vector database setup, chunking strategies, retrieval optimization, and evaluation.
Use this workflow when:
ai-product - AI product designrag-engineer - RAG engineeringUse @ai-product to define RAG application requirements
embedding-strategies - Embedding selectionrag-engineer - RAG patternsUse @embedding-strategies to select optimal embedding model
vector-database-engineer - Vector DBsimilarity-search-patterns - Similarity searchUse @vector-database-engineer to set up vector database
rag-engineer - Chunking strategiesrag-implementation - RAG implementationUse @rag-engineer to implement chunking strategy
similarity-search-patterns - Similarity searchhybrid-search-implementation - Hybrid searchUse @similarity-search-patterns to implement retrieval
Use @hybrid-search-implementation to add hybrid search
llm-application-dev-ai-assistant - LLM integrationllm-application-dev-prompt-optimize - Prompt optimizationUse @llm-application-dev-ai-assistant to integrate LLM
prompt-caching - Prompt cachingrag-engineer - RAG optimizationUse @prompt-caching to implement RAG caching
llm-evaluation - LLM evaluationevaluation - AI evaluationUse @llm-evaluation to evaluate RAG system
User Query -> Embedding -> Vector Search -> Retrieved Docs -> LLM -> Response
| | | |
Model Vector DB Chunk Store Prompt + Context
ai-ml - AI/ML developmentai-agent-development - AI agentsdatabase - Vector databasesNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
The English summary is being prepared. Showing the original description.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
The English summary is being prepared. Showing the original description.