Manages issues via the br CLI (beads), a local-first tracker stored in .beads/ (SQLite + JSONL). Use when capturing issues, finding ready work, claiming issues, managing dependencies, or syncing changes. Triggers: "br", "beads", "issue tracking".
Review, rewrite, and debug LLM prompts. Use when asked to: (1) improve an existing prompt, (2) design a new system or developer prompt, (3) add few-shot examples, (4) define output schemas and success criteria, (5) diagnose prompt failures from transcripts. Not for: model policy workarounds, producing domain answers without context, or guaranteeing model-specific behavior.
Creates or updates mala.yaml project configuration files for the local mala orchestrator. Use when asked to initialize, generate, write, edit, validate, fix, or explain a mala.yaml config, including presets, commands, coverage, evidence checks, validation triggers, or review settings.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. Triggers: simplify, refine, clean up code.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
Executes SQL queries on Dune Analytics and writes results as CSV to /tmp. Use when the user needs blockchain data from Dune or wants to run a saved Dune query by ID. Triggers: "dune query", "dune sql", "query dune", "blockchain data"
Explore Python import graphs and enforce layered architecture using grimp.
Search and analyze mala orchestrator and Claude session logs. Use when searching for session logs, debugging agent runs, finding tool errors, analyzing mala run history, or investigating issue-specific logs. Triggers on queries like "find logs for issue X", "what went wrong in the last run", "show tool errors", "list recent sessions".