Help
npx machina-cli add skill ConaryLabs/Mira/help --openclawname: help description: This skill should be used when the user asks "help", "what commands", "list commands", "what can mira do", "mira help", "show commands", "what can you do", "how do I use mira", or wants to see all available Mira skills and tools.
Mira Commands
Getting Started
| Command | Description |
|---|---|
/mira:help | Show all available commands and tools |
/mira:status | Quick health check: index stats, storage, active goals |
/mira:recap | Get session context, preferences, and active goals |
Daily Use
| Command | Description |
|---|---|
/mira:search <query> | Semantic code search — find code by meaning, not just text |
/mira:goals | Track cross-session objectives with milestones |
/mira:diff | Semantic analysis of git changes with impact assessment |
/mira:insights | Surface background analysis and predictions |
Power User
| Command | Description |
|---|---|
/mira:experts | Expert consultation via Agent Teams |
/mira:full-cycle | End-to-end expert review with implementation and QA |
/mira:qa-hardening | Production readiness review and hardening backlog |
/mira:refactor | Safe code restructuring with architect and reviewer validation |
MCP Tools
Beyond slash commands, Mira provides MCP tools that Claude uses automatically:
code, diff, project, session, insights, goal, index, launch
Note: team is available via mira tool team ... (CLI only, not exposed as an MCP tool).
These power semantic search, call graph analysis, persistent memory, and more — no slash command needed.
Tool Dependencies
Some tools require indexing before they work. Here's what depends on what.
Requires code index (index(action="project"))
| Tool | Notes |
|---|---|
code(action="search") | Semantic search over indexed code |
code(action="callers") / code(action="callees") | Call graph analysis |
code(action="bundle") | Module extraction |
diff(include_impact=true) | Impact analysis of changes |
Requires health scan (index(action="health"))
| Tool | Notes |
|---|---|
code(action="dependencies") | Auto-queues health scan if missing |
code(action="dead_code") | Auto-queues health scan if missing |
insights() | Needs health data for analysis |
Works without indexing
| Tool | Notes |
|---|---|
project(*), session(*), goal(*) | Session and goal management |
code(action="symbols") | Single-file parsing via tree-sitter |
diff() (without impact) | Git-based analysis only |
Note: project(action="start") auto-triggers background indexing, so most users never need to manually index.
Instructions
Present the command reference above. If the user seems new to Mira, highlight /mira:status and /mira:recap as good starting points.
Tip
New session? Run /mira:recap to restore context from previous work.
Quick health check? Run /mira:status to see index stats, storage, and active goals.
Source
git clone https://github.com/ConaryLabs/Mira/blob/main/plugin/skills/help/SKILL.mdView on GitHub Overview
The Help skill exposes all Mira commands and tools, organized into Getting Started, Daily Use, Power User, and MCP Tools. It helps users quickly discover what Mira can do, how to use it, and where to start, including quick access to status and recap for new users.
How This Skill Works
When a user asks for help, Mira assembles a structured reference of all slash commands and MCP tools, organized into sections by usage. It highlights starting points for newcomers and notes indexing and tool-dependency considerations so users know what requires indexing.
When to Use It
- User asks for help or queries like 'what commands' or 'what can Mira do'.
- User wants to see all available Mira skills and tools.
- User is new to Mira and needs quick starting points (status and recap).
- User wants to understand which tools exist and how they relate to indexing and dependencies.
- User wants to perform common tasks (search, goals, diff, insights) and learn related commands.
Quick Start
- Step 1: Type '/mira:help' to view all commands and MCP tools.
- Step 2: If you're new, run '/mira:status' to see index stats and active goals, and '/mira:recap' to restore context.
- Step 3: Try a task-specific command such as '/mira:search <query>' or '/mira:experts' to see practical usage.
Best Practices
- Start with the Getting Started table to identify core commands (/mira:help, /mira:status, /mira:recap).
- If new, emphasize /mira:status and /mira:recap as good starting points for context and health.
- Use Daily Use commands (+ /mira:search, /mira:goals, /mira:diff, /mira:insights) to accomplish typical tasks.
- Explore Power User and MCP Tools to access advanced capabilities like experts, full-cycle reviews, and code tools.
- Be mindful of Tool Dependencies and indexing requirements before using tools that rely on indexing (e.g., code index) and point users to relevant notes.
Example Use Cases
- User: 'What commands does Mira offer?'
- User: 'Show me all available Mira skills and tools.'
- User: 'I want to search code semantically using /mira:search.'
- User: 'Check system health now with /mira:status.'
- User: 'I need an end-to-end expert review with /mira:full-cycle.'
