From axon
Use when the user wants to ask a question and get an LLM-synthesized answer grounded in indexed documents, do RAG over previously crawled or embedded content, get cited answers from the knowledge base, or find information that was previously indexed. Triggers on "ask axon", "what does the documentation say about", "according to what I've indexed", "RAG query", "use axon to answer", or any question where the user wants grounded answers from indexed content rather than hallucination.
How this skill is triggered — by the user, by Claude, or both
Slash command
/axon:askThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
RAG query: retrieves relevant chunks from Qdrant then synthesizes an answer with citations.
RAG query: retrieves relevant chunks from Qdrant then synthesizes an answer with citations.
{ "action": "ask", "query": "How does axon handle Chrome auto-switching?" }
With temporal filter:
{ "action": "ask", "query": "latest rust async patterns", "since": "7d" }
With diagnostics (shows retrieval scores):
{ "action": "ask", "query": "embedding pipeline", "diagnostics": true }
axon ask "how does axon handle Chrome auto-switching?" --since 7d --diagnostics
| Option | Default | Notes |
|---|---|---|
since | — | 7d, 30d, YYYY-MM-DD — filters by indexing date |
before | — | Upper date bound |
diagnostics | false | Show retrieval scores and sources |
hybrid_search | true | false for dense-only comparison |
graph | false | Deprecated compatibility option; graph retrieval is not available in the current runtime |
collection | cortex | Override collection per-request |
diagnostics: true — check retrieval scoreshybrid_search: false to compare approaches{ "action": "sources" } to verify content is indexednpx claudepluginhub jmagar/lab --plugin axonGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.