Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Mission Control
Kanban-style task management dashboard for AI assistants. Manage tasks via CLI or dashboard UI. Use when user mentions tasks, kanban, task board, mission con...
skill openclawclawhub Free
Kanban-style task management dashboard for AI assistants. Manage tasks via CLI or dashboard UI. Use when user mentions tasks, kanban, task board, mission con...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- CHANGELOG.md, README.md, SKILL.md, assets/data/crons.json, assets/data/tasks.json, assets/data/version.json
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.3.1
Provenance
- Publisher
- rdsthomas
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Mission Control โ Task Management for AI Assistants
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".
๐ Quick Start
Just say: "Set up Mission Control for my workspace" The agent will: Check prerequisites (Tailscale, gh CLI) Copy dashboard files to your workspace Create the config file (~/.clawdbot/mission-control.json) Install the webhook transform Set up GitHub webhook Push to GitHub and enable Pages That's it. The agent handles everything.
Prerequisites
Before setup, you need: RequirementCheckInstallTailscaletailscale statusbrew install tailscale or tailscale.com/downloadTailscale Funneltailscale funnel statustailscale funnel 18789 (one-time)GitHub CLIgh auth statusbrew install gh && gh auth login If any are missing, tell the agent โ it will guide you through installation.
How It Works
Dashboard โ Web UI hosted on GitHub Pages where humans manage tasks Webhook โ GitHub sends push events to Clawdbot when tasks change Transform โ Compares old vs new tasks.json, detects status changes Auto-Processing โ When a task moves to "In Progress", the agent starts working
The Flow
Human moves task โ GitHub push โ Webhook โ Transform โ Agent receives work order โ โ Dashboard Executes task โ โ Agent updates status โ Commits changes โ Marks subtasks done โโโ
Task Structure
Tasks live in <workspace>/data/tasks.json: { "id": "task_001", "title": "Implement feature X", "description": "Detailed context for the agent", "status": "backlog", "subtasks": [ { "id": "sub_001", "title": "Research approach", "done": false }, { "id": "sub_002", "title": "Write code", "done": false } ], "priority": "high", "dod": "Definition of Done - what success looks like", "comments": [] }
Status Values
StatusMeaningpermanentRecurring tasks (daily checks, etc.)backlogWaiting to be worked onin_progressAgent is working on thisreviewDone, awaiting human approvaldoneCompleted and approved
CLI Commands
Use <skill>/scripts/mc-update.sh for task updates: # Status changes mc-update.sh status <task_id> review mc-update.sh status <task_id> done # Comments mc-update.sh comment <task_id> "Progress update..." # Subtasks mc-update.sh subtask <task_id> sub_1 done # Complete (moves to review + adds summary) mc-update.sh complete <task_id> "Summary of what was done" # Push to GitHub mc-update.sh push "Commit message"
Agent Workflow
When you receive a task (moved to "In Progress"): Read โ Check title, description, subtasks, dod Mark started โ mc-update.sh start <task_id> Execute โ Work through subtasks, mark each done Document โ Add progress comments Complete โ mc-update.sh complete <task_id> "Summary"
Handling Rework
If a completed task is moved back to "In Progress" with a new comment: Read the feedback comment Address the issues Add a comment explaining your changes Move back to Review
EPICs
EPICs are parent tasks with multiple child tickets. When you receive an EPIC: Child tickets are listed in the subtasks (format: MC-XXX-001: Title) Work through them sequentially (1 โ 2 โ 3...) After each child: comment result, set to "review", mark EPIC subtask done After last child: set EPIC to "review"
Heartbeat Integration
Add to your HEARTBEAT.md: ## Task Check 1. Check `data/tasks.json` for tasks in "in_progress" 2. Flag tasks with `processingStartedAt` but no recent activity 3. Check "review" tasks for new feedback comments
Configuration
Config lives in ~/.clawdbot/mission-control.json. See assets/examples/CONFIG-REFERENCE.md for all options. Minimal config (set by agent during setup): { "gateway": { "hookToken": "your-token" }, "workspace": { "path": "/path/to/workspace" }, "slack": { "botToken": "xoxb-...", "channel": "C0123456789" } }
Troubleshooting
See docs/TROUBLESHOOTING.md for common issues: Dashboard shows sample data โ Connect GitHub token Webhook not triggering โ Check Tailscale Funnel Changes not appearing โ GitHub Pages cache (wait 1-2 min)
Security
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.
Trust Model
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. Multi-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.
Mitigations
Input sanitization: mc-update.sh validates all inputs against injection patterns before passing them to Python or git. No credential storage: The dashboard stores no tokens or secrets โ all auth is handled by Clawdbot's config. Webhook HMAC verification: The transform module validates webhook signatures using timingSafeEqual to prevent tampering. Security scan on sync: The sync-to-opensource.sh script scans for leaked credentials before publishing.
Recommendations
Keep your dashboard repository private if you don't want others to see your task data. Review task descriptions before moving them to "In Progress" if the task was created by someone else. Use Clawdbot's groupPolicy and allowFrom settings to restrict who can interact with the agent.
Files
FilePurpose<workspace>/index.htmlDashboard UI<workspace>/data/tasks.jsonTask data<skill>/scripts/mc-update.shCLI tool~/.clawdbot/mission-control.jsonConfig~/.clawdbot/hooks-transforms/github-mission-control.mjsWebhook transform
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs3 Config
- SKILL.md
- CHANGELOG.md
- README.md
- assets/data/crons.json
- assets/data/tasks.json
- assets/data/version.json