{ "schemaVersion": "1.0", "item": { "slug": "mission-control", "name": "Mission Control", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/rdsthomas/mission-control", "canonicalUrl": "https://clawhub.ai/rdsthomas/mission-control", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/mission-control", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=mission-control", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "CHANGELOG.md", "README.md", "SKILL.md", "assets/data/crons.json", "assets/data/tasks.json", "assets/data/version.json" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/mission-control" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/mission-control", "agentPageUrl": "https://openagent3.xyz/skills/mission-control/agent", "manifestUrl": "https://openagent3.xyz/skills/mission-control/agent.json", "briefUrl": "https://openagent3.xyz/skills/mission-control/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Mission Control — Task Management for AI Assistants", "body": "A Kanban-style task board that you (the AI assistant) manage. Your human creates and prioritizes tasks via the web dashboard; you execute them automatically when they're moved to \"In Progress\"." }, { "title": "🚀 Quick Start", "body": "Just say: \"Set up Mission Control for my workspace\"\n\nThe agent will:\n\nCheck prerequisites (Tailscale, gh CLI)\nCopy dashboard files to your workspace\nCreate the config file (~/.clawdbot/mission-control.json)\nInstall the webhook transform\nSet up GitHub webhook\nPush to GitHub and enable Pages\n\nThat's it. The agent handles everything." }, { "title": "Prerequisites", "body": "Before setup, you need:\n\nRequirementCheckInstallTailscaletailscale statusbrew install tailscale or tailscale.com/downloadTailscale Funneltailscale funnel statustailscale funnel 18789 (one-time)GitHub CLIgh auth statusbrew install gh && gh auth login\n\nIf any are missing, tell the agent — it will guide you through installation." }, { "title": "How It Works", "body": "Dashboard — Web UI hosted on GitHub Pages where humans manage tasks\nWebhook — GitHub sends push events to Clawdbot when tasks change\nTransform — Compares old vs new tasks.json, detects status changes\nAuto-Processing — When a task moves to \"In Progress\", the agent starts working" }, { "title": "The Flow", "body": "Human moves task → GitHub push → Webhook → Transform → Agent receives work order\n ↓ ↓\n Dashboard Executes task\n ↓ ↓\nAgent updates status ← Commits changes ← Marks subtasks done ←─┘" }, { "title": "Task Structure", "body": "Tasks live in /data/tasks.json:\n\n{\n \"id\": \"task_001\",\n \"title\": \"Implement feature X\",\n \"description\": \"Detailed context for the agent\",\n \"status\": \"backlog\",\n \"subtasks\": [\n { \"id\": \"sub_001\", \"title\": \"Research approach\", \"done\": false },\n { \"id\": \"sub_002\", \"title\": \"Write code\", \"done\": false }\n ],\n \"priority\": \"high\",\n \"dod\": \"Definition of Done - what success looks like\",\n \"comments\": []\n}" }, { "title": "Status Values", "body": "StatusMeaningpermanentRecurring tasks (daily checks, etc.)backlogWaiting to be worked onin_progressAgent is working on thisreviewDone, awaiting human approvaldoneCompleted and approved" }, { "title": "CLI Commands", "body": "Use /scripts/mc-update.sh for task updates:\n\n# Status changes\nmc-update.sh status review\nmc-update.sh status done\n\n# Comments\nmc-update.sh comment \"Progress update...\"\n\n# Subtasks\nmc-update.sh subtask sub_1 done\n\n# Complete (moves to review + adds summary)\nmc-update.sh complete \"Summary of what was done\"\n\n# Push to GitHub\nmc-update.sh push \"Commit message\"" }, { "title": "Agent Workflow", "body": "When you receive a task (moved to \"In Progress\"):\n\nRead — Check title, description, subtasks, dod\nMark started — mc-update.sh start \nExecute — Work through subtasks, mark each done\nDocument — Add progress comments\nComplete — mc-update.sh complete \"Summary\"" }, { "title": "Handling Rework", "body": "If a completed task is moved back to \"In Progress\" with a new comment:\n\nRead the feedback comment\nAddress the issues\nAdd a comment explaining your changes\nMove back to Review" }, { "title": "EPICs", "body": "EPICs are parent tasks with multiple child tickets. When you receive an EPIC:\n\nChild tickets are listed in the subtasks (format: MC-XXX-001: Title)\nWork through them sequentially (1 → 2 → 3...)\nAfter each child: comment result, set to \"review\", mark EPIC subtask done\nAfter last child: set EPIC to \"review\"" }, { "title": "Heartbeat Integration", "body": "Add to your HEARTBEAT.md:\n\n## Task Check\n\n1. Check `data/tasks.json` for tasks in \"in_progress\"\n2. Flag tasks with `processingStartedAt` but no recent activity\n3. Check \"review\" tasks for new feedback comments" }, { "title": "Configuration", "body": "Config lives in ~/.clawdbot/mission-control.json. See assets/examples/CONFIG-REFERENCE.md for all options.\n\nMinimal config (set by agent during setup):\n\n{\n \"gateway\": { \"hookToken\": \"your-token\" },\n \"workspace\": { \"path\": \"/path/to/workspace\" },\n \"slack\": { \"botToken\": \"xoxb-...\", \"channel\": \"C0123456789\" }\n}" }, { "title": "Troubleshooting", "body": "See docs/TROUBLESHOOTING.md for common issues:\n\nDashboard shows sample data → Connect GitHub token\nWebhook not triggering → Check Tailscale Funnel\nChanges not appearing → GitHub Pages cache (wait 1-2 min)" }, { "title": "Security", "body": "Mission Control is a task management system for AI agents — its core purpose is to pass human-authored task descriptions to an agent for execution. This is by design, not a vulnerability." }, { "title": "Trust Model", "body": "Single-user / trusted-user setup: Task authors are the same people who control the agent. The trust boundary is identical to typing a message directly to your assistant.\nMulti-user setups: If multiple users can create tasks on the dashboard, treat task content as untrusted input. Use Clawdbot's agent sandbox and permission model to limit what the agent can do." }, { "title": "Mitigations", "body": "Input sanitization: mc-update.sh validates all inputs against injection patterns before passing them to Python or git.\nNo credential storage: The dashboard stores no tokens or secrets — all auth is handled by Clawdbot's config.\nWebhook HMAC verification: The transform module validates webhook signatures using timingSafeEqual to prevent tampering.\nSecurity scan on sync: The sync-to-opensource.sh script scans for leaked credentials before publishing." }, { "title": "Recommendations", "body": "Keep your dashboard repository private if you don't want others to see your task data.\nReview task descriptions before moving them to \"In Progress\" if the task was created by someone else.\nUse Clawdbot's groupPolicy and allowFrom settings to restrict who can interact with the agent." }, { "title": "Files", "body": "FilePurpose/index.htmlDashboard UI/data/tasks.jsonTask data/scripts/mc-update.shCLI tool~/.clawdbot/mission-control.jsonConfig~/.clawdbot/hooks-transforms/github-mission-control.mjsWebhook transform" } ], "body": "Mission Control — Task Management for AI Assistants\n\nA Kanban-style task board that you (the AI assistant) manage. Your human creates and prioritizes tasks via the web dashboard; you execute them automatically when they're moved to \"In Progress\".\n\n🚀 Quick Start\n\nJust say: \"Set up Mission Control for my workspace\"\n\nThe agent will:\n\nCheck prerequisites (Tailscale, gh CLI)\nCopy dashboard files to your workspace\nCreate the config file (~/.clawdbot/mission-control.json)\nInstall the webhook transform\nSet up GitHub webhook\nPush to GitHub and enable Pages\n\nThat's it. The agent handles everything.\n\nPrerequisites\n\nBefore setup, you need:\n\nRequirement\tCheck\tInstall\nTailscale\ttailscale status\tbrew install tailscale or tailscale.com/download\nTailscale Funnel\ttailscale funnel status\ttailscale funnel 18789 (one-time)\nGitHub CLI\tgh auth status\tbrew install gh && gh auth login\n\nIf any are missing, tell the agent — it will guide you through installation.\n\nHow It Works\nDashboard — Web UI hosted on GitHub Pages where humans manage tasks\nWebhook — GitHub sends push events to Clawdbot when tasks change\nTransform — Compares old vs new tasks.json, detects status changes\nAuto-Processing — When a task moves to \"In Progress\", the agent starts working\nThe Flow\nHuman moves task → GitHub push → Webhook → Transform → Agent receives work order\n ↓ ↓\n Dashboard Executes task\n ↓ ↓\nAgent updates status ← Commits changes ← Marks subtasks done ←─┘\n\nTask Structure\n\nTasks live in /data/tasks.json:\n\n{\n \"id\": \"task_001\",\n \"title\": \"Implement feature X\",\n \"description\": \"Detailed context for the agent\",\n \"status\": \"backlog\",\n \"subtasks\": [\n { \"id\": \"sub_001\", \"title\": \"Research approach\", \"done\": false },\n { \"id\": \"sub_002\", \"title\": \"Write code\", \"done\": false }\n ],\n \"priority\": \"high\",\n \"dod\": \"Definition of Done - what success looks like\",\n \"comments\": []\n}\n\nStatus Values\nStatus\tMeaning\npermanent\tRecurring tasks (daily checks, etc.)\nbacklog\tWaiting to be worked on\nin_progress\tAgent is working on this\nreview\tDone, awaiting human approval\ndone\tCompleted and approved\nCLI Commands\n\nUse /scripts/mc-update.sh for task updates:\n\n# Status changes\nmc-update.sh status review\nmc-update.sh status done\n\n# Comments\nmc-update.sh comment \"Progress update...\"\n\n# Subtasks\nmc-update.sh subtask sub_1 done\n\n# Complete (moves to review + adds summary)\nmc-update.sh complete \"Summary of what was done\"\n\n# Push to GitHub\nmc-update.sh push \"Commit message\"\n\nAgent Workflow\n\nWhen you receive a task (moved to \"In Progress\"):\n\nRead — Check title, description, subtasks, dod\nMark started — mc-update.sh start \nExecute — Work through subtasks, mark each done\nDocument — Add progress comments\nComplete — mc-update.sh complete \"Summary\"\nHandling Rework\n\nIf a completed task is moved back to \"In Progress\" with a new comment:\n\nRead the feedback comment\nAddress the issues\nAdd a comment explaining your changes\nMove back to Review\nEPICs\n\nEPICs are parent tasks with multiple child tickets. When you receive an EPIC:\n\nChild tickets are listed in the subtasks (format: MC-XXX-001: Title)\nWork through them sequentially (1 → 2 → 3...)\nAfter each child: comment result, set to \"review\", mark EPIC subtask done\nAfter last child: set EPIC to \"review\"\nHeartbeat Integration\n\nAdd to your HEARTBEAT.md:\n\n## Task Check\n\n1. Check `data/tasks.json` for tasks in \"in_progress\"\n2. Flag tasks with `processingStartedAt` but no recent activity\n3. Check \"review\" tasks for new feedback comments\n\nConfiguration\n\nConfig lives in ~/.clawdbot/mission-control.json. See assets/examples/CONFIG-REFERENCE.md for all options.\n\nMinimal config (set by agent during setup):\n\n{\n \"gateway\": { \"hookToken\": \"your-token\" },\n \"workspace\": { \"path\": \"/path/to/workspace\" },\n \"slack\": { \"botToken\": \"xoxb-...\", \"channel\": \"C0123456789\" }\n}\n\nTroubleshooting\n\nSee docs/TROUBLESHOOTING.md for common issues:\n\nDashboard shows sample data → Connect GitHub token\nWebhook not triggering → Check Tailscale Funnel\nChanges not appearing → GitHub Pages cache (wait 1-2 min)\nSecurity\n\nMission Control is a task management system for AI agents — its core purpose is to pass human-authored task descriptions to an agent for execution. This is by design, not a vulnerability.\n\nTrust Model\nSingle-user / trusted-user setup: Task authors are the same people who control the agent. The trust boundary is identical to typing a message directly to your assistant.\nMulti-user setups: If multiple users can create tasks on the dashboard, treat task content as untrusted input. Use Clawdbot's agent sandbox and permission model to limit what the agent can do.\nMitigations\nInput sanitization: mc-update.sh validates all inputs against injection patterns before passing them to Python or git.\nNo credential storage: The dashboard stores no tokens or secrets — all auth is handled by Clawdbot's config.\nWebhook HMAC verification: The transform module validates webhook signatures using timingSafeEqual to prevent tampering.\nSecurity scan on sync: The sync-to-opensource.sh script scans for leaked credentials before publishing.\nRecommendations\nKeep your dashboard repository private if you don't want others to see your task data.\nReview task descriptions before moving them to \"In Progress\" if the task was created by someone else.\nUse Clawdbot's groupPolicy and allowFrom settings to restrict who can interact with the agent.\nFiles\nFile\tPurpose\n/index.html\tDashboard UI\n/data/tasks.json\tTask data\n/scripts/mc-update.sh\tCLI tool\n~/.clawdbot/mission-control.json\tConfig\n~/.clawdbot/hooks-transforms/github-mission-control.mjs\tWebhook transform" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/rdsthomas/mission-control", "publisherUrl": "https://clawhub.ai/rdsthomas/mission-control", "owner": "rdsthomas", "version": "2.3.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/mission-control", "downloadUrl": "https://openagent3.xyz/downloads/mission-control", "agentUrl": "https://openagent3.xyz/skills/mission-control/agent", "manifestUrl": "https://openagent3.xyz/skills/mission-control/agent.json", "briefUrl": "https://openagent3.xyz/skills/mission-control/agent.md" } }