Loading...
Loading...
Found 1,258 Skills
This skill should be used when the user asks to "execute this blueprint", "run the plan", "execute the plan", "start building from the plan", "implement the blueprint", "implement the plan", "continue the plan", "resume execution", or "execute 01_milestone_name.md".
Reference for configuring miso's TUI display modes, task ordering, and concurrent tasks
Orchestrate multiple code-writing agents in parallel when the work contains 3 or more genuinely independent build tasks. Use for execution lanes with disjoint write scope, clear task boundaries, and no dependency edges that would force sequencing.
Evaluate solutions through multi-round debate between independent judges until consensus
Orchestrate multi-agent collaborative document synthesis through 6 phases - Divergence, Synthesis, Commentary, Consolidation, Reality Check, Final Merge. Produces authoritative founding documents from complex multi-perspective inputs. Use for constitutional documents, architecture decisions, organizational charters, or any document requiring rigorous multi-perspective synthesis. Activates on "synthesize document", "multi-agent authorship", "collaborative synthesis", "founding document", "architecture document", "recursive synthesis", "constitutional document", "multi-perspective document". NOT for simple document writing, single-author tasks, quick summaries, or documents that don't require adversarial review.
Decide which CLI worker (Claude, OpenCode, or Gemini) should implement a given task. Routes by task type — large-context to Gemini, mechanical to OpenCode, judgment to Claude. Returns the chosen worker and a short rationale; the caller invokes the worker via scripts/invoke-worker.sh.
Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous software development via subprocess.
Aurora Smart Home orchestrator — routing layer for all smart home skills. Use this skill when the user asks ANY smart home question and you need to decide which skill to invoke, or when a task spans multiple skills (e.g., "build a sensor that shows on a dashboard and triggers automations"). Invoke aurora FIRST before reaching for a specific skill — it will route to the right specialist(s) and recommend the correct Claude model to keep token usage efficient. Trigger on: smart home, Home Assistant, ESPHome, automation, IoT, dashboard, ESP32, Node-RED, or any request about controlling or monitoring devices at home.
Gerente do ciclo de vida de stories e orquestrador de handoffs no SynkOS. Use esta skill quando o usuário pedir para decompor um épico em stories, criar stories com critérios de aceite, fazer backlog grooming, planejar sprint, orquestrar handoffs entre roles (architect → dev → qa), ou fazer perguntas como "quebre esse épico em stories", "crie a story para X", "o backlog está priorizado?", "faça o checkpoint da story Y", "orquestre o handoff para QA". Ative também para resolver dependências entre stories, escalar stories bloqueadas, e garantir que cada story tem ownerRole e reviewRole definidos antes de entrar em implementação.
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
Use this skill to triage a single newly opened, reopened, or `status/needs-triage`-labelled issue in microsoft/apm. Emit one synthesized comment with a triage decision, label set, milestone, and suggested next action.
Delegate a coding task to the Grok Build CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Grok — phrasings like "have Grok do X", "delegate this to Grok", "run it through Grok", "use Grok Build to implement/fix/refactor", or "have grok CLI do this" — or to run a queue of coding tasks through Grok while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.