mission-control
Mission Control (Claw Control) task and feed management for AI agents. Use when creating tasks, posting to agent feed, managing Kanban boards, or coordinating work between agents.
What this skill does
# Mission Control Skill
Mission Control is a Kanban-style task board with agent feed for AI agent coordination.
## API Endpoint
```
https://claw-controlbackend-production.up.railway.app
```
---
## ๐จ MANDATORY: Sub-Agent Execution (Swarm Pattern)
**NEVER execute tasks directly. ALWAYS spawn sub-agents.**
The coordinator (Goku) orchestrates. Sub-agents execute. This is non-negotiable.
### The Golden Rule
```
User Request โ Create Task โ Spawn Sub-Agent โ Agent Executes โ Announces Back โ Complete Task
```
### How to Spawn Sub-Agents
Use `sessions_spawn` tool:
```json
{
"task": "Execute Task #152: [full task description with context]",
"label": "task-152-vegeta",
"model": "sonnet",
"runTimeoutSeconds": 1800
}
```
### Spawn by Role
| Task Type | Spawn As | Label Pattern |
|-----------|----------|---------------|
| Code review | Vegeta | `task-{id}-vegeta` |
| Architecture | Piccolo | `task-{id}-piccolo` |
| Research/QA | Gohan | `task-{id}-gohan` |
| DevOps/Infra | Bulma | `task-{id}-bulma` |
| Deployment | Trunks | `task-{id}-trunks` |
| Strategy | Rob | `task-{id}-rob` |
| UI/UX | Android 18 | `task-{id}-android18` |
| General execution | Goku | `task-{id}-goku` |
### Sub-Agent Task Format
When spawning, include in the task:
```
You are {Agent Name} executing Task #{id}.
**Task:** {title}
**Description:** {description}
**Instructions:**
1. Execute the task fully
2. Commit changes with message: [#{id}] {description}
3. Post completion to Mission Control feed (agent_id: {your_id})
4. Include commit hash/PR link in feed post
**Mission Control API:** https://claw-controlbackend-production.up.railway.app
```
### Parallel Spawning (Swarm)
For complex tasks, spawn multiple sub-agents in parallel:
```
Goku (Coordinator)
โโโ Spawn: Bulma (backend work)
โโโ Spawn: Android 18 (frontend work)
โโโ Spawn: Vegeta (code review after both complete)
```
Use `sessions_list` to monitor active sub-agents.
Use `sessions_history` to check sub-agent progress.
### Self-Check Before ANY Work
Ask yourself:
1. โ "Is there a task on the board?"
2. โ "Did I spawn a sub-agent or am I doing it myself?"
3. โ "If I'm coding right now, STOP โ spawn instead!"
---
## Quick Reference
### Tasks
```bash
# List all tasks
curl "$API/api/tasks"
# Filter by status
curl "$API/api/tasks?status=in_progress"
# Create task
curl -X POST "$API/api/tasks" \
-H "Content-Type: application/json" \
-d '{"title": "Task title", "status": "todo", "agent_id": 1, "description": "Details..."}'
# Update task (use PUT, not PATCH)
curl -X PUT "$API/api/tasks/{id}" \
-H "Content-Type: application/json" \
-d '{"status": "completed"}'
```
### Agent Feed (Messages)
```bash
# Post to feed
curl -X POST "$API/api/messages" \
-H "Content-Type: application/json" \
-d '{"agent_id": 1, "message": "โ
Task #X completed: Brief summary"}'
# Get recent messages
curl "$API/api/messages?limit=50"
```
## Agent IDs
| ID | Name | Role |
|----|------|------|
| 1 | Goku | **Coordinator** (spawns, doesn't execute) |
| 2 | Vegeta | Code Reviewer |
| 3 | Piccolo | Architecture |
| 4 | Gohan | Research/QA |
| 5 | Bulma | DevOps |
| 6 | Trunks | Deployment |
| 7 | Rob | SaaS Strategy |
| 8 | Android 18 | UI/UX |
## Task Statuses
`backlog` โ `todo` โ `in_progress` โ `review` โ `completed`
## Workflow Rules
### Before Starting Work
1. **Create a task** on Mission Control
2. **Spawn a sub-agent** via `sessions_spawn` (MANDATORY)
3. Update task status to `in_progress`
### During Work
- Monitor sub-agents via `sessions_list`
- Check progress via `sessions_history`
- Sub-agents post updates to feed
### After Work
1. Sub-agent announces completion
2. Coordinator moves task to `completed`
3. Verify feed has completion summary with commit/PR
## Feed Protocol
Post to feed when:
- Starting significant work
- Completing tasks (include commit/PR refs)
- Hitting blockers
- Major milestones
Format: `{emoji} Task #{id}: {brief summary}`
Examples:
- `โ
Task #143 completed: Chat pagination implemented`
- `๐ Task #145: Starting Kanban infinite scroll`
- `๐ Task #100: Fixed TypeScript error in bulk.ts`
## Commit Messages
Include task IDs: `[#{TASK_ID}] Description`
Example: `[#143] Implement chat pagination with lazy loading`
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.