Xpersona
M

Mission Control

CLAWHUB · Unverified

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: Mission Control Owner: rdsthomas Summary: 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... Tags: automation:2.0.0, dashboard:2.0.0, kanban:2.0.0, latest:2.3.1, tasks:2.0.0 Version history: v2.3.1 | 2026-02-20T16:02:08.123Z | user Fix: Renamed from 'Jeannie Control' to 'Mission Control'. Removed priva

62
Rank
84
Safety
15k
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 15.2K downloads reported by the source. Last updated 11/16/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s17ccgtyv0nm1dwt1bactxfpg5884ynb:mission-control
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-rdsthomas-mission-control--control-2/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

146,158 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: mission-control
description: Kanban-style task management dashboard for AI assistants. Manage tasks via CLI or dashboard UI. Use when user mentions tasks, kanban, task board, mission control, or wants to track work items with status columns (backlog, in progress, review, done).
homepage: https://github.com/rdsthomas/mission-control
metadata: {"clawdbot": {"emoji": "🎛️"}}
---

# 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:
1. Check prerequisites (Tailscale, gh CLI)
2. Copy dashboard files to your workspace
3. Create the config file (`~/.clawdbot/mission-control.json`)
4. Install the webhook transform
5. Set up GitHub webhook
6. Push to GitHub and enable Pages

**That's it.** The agent handles everything.

---

## Prerequisites

Before setup, you need:

| Requirement | Check | Install |
|-------------|-------|---------|
| **Tailscale** | `tailscale status` | `brew install tailscale` or [tailscale.com/download](https://tailscale.com/download) |
| **Tailscale Funnel** | `tailscale funnel status` | `tailscale funnel 18789` (one-time) |
| **GitHub CLI** | `gh auth status` | `brew install gh && gh auth login` |

If any are missing, tell the agent — it will guide you through installation.

---

## How It Works

1. **Dashboard** — Web UI hosted on GitHub Pages where humans manage tasks
2. **Webhook** — GitHub sends push events to Clawdbot when tasks change
3. **Transform** — Compares old vs new tasks.json, detects status changes
4. **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`:

```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

| Status | Meaning |
|--------|---------|
| `permanent` | Recurring tasks (daily checks, etc.) |
| `backlog` | Waiting to be worked on |
| `in_progress` | **Agent is working on this** |
| `review` | Done, awaiting human approval |
| `done` | Completed and approved |

---

## CLI Commands

Use `<skill>/sc

README.md

# Mission Control

[![Agent-Powered Setup](https://img.shields.io/badge/Setup-Agent--Powered-brightgreen)](https://github.com/rdsthomas/mission-control)
[![Clawdbot Skill](https://img.shields.io/badge/Clawdbot-Skill-blue)](https://clawdhub.com)

A Kanban-style task management system for AI assistants. Your human creates and prioritizes tasks via a web dashboard; the agent executes them automatically when moved to "In Progress".

## Quick Start

**Just say:** *"Set up Mission Control for my workspace"*

The agent handles everything automatically:
- Checks prerequisites (Tailscale, gh CLI)
- Copies dashboard files
- Creates config
- Installs webhook transform
- Sets up GitHub webhook
- Deploys to GitHub Pages

## Features

- 📋 **Kanban Board** — Backlog, In Progress, Review, Done columns
- 🔄 **Auto-Execution** — Agent starts working when tasks are moved to "In Progress"
- 🎯 **EPIC Support** — Parent tasks with multiple child tickets
- 💬 **Comments** — Track progress and feedback
- 📊 **Subtasks** — Break complex tasks into steps
- 🔔 **Slack Notifications** — Optional status updates

## Documentation

- [SKILL.md](SKILL.md) — Full skill reference
- [docs/PREREQUISITES.md](docs/PREREQUISITES.md) — Installation requirements
- [docs/HOW-IT-WORKS.md](docs/HOW-IT-WORKS.md) — Technical architecture
- [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) — Common issues & solutions

## Requirements

| Tool | Check | Purpose |
|------|-------|---------|
| Tailscale | `tailscale status` | Secure tunnel for webhooks |
| Tailscale Funnel | `tailscale funnel status` | Expose Clawdbot to internet |
| GitHub CLI | `gh auth status` | Repository operations |

## Configuration

Config lives in `~/.clawdbot/mission-control.json`. See [CONFIG-REFERENCE.md](assets/examples/CONFIG-REFERENCE.md) for all options.

## CLI Usage

```bash
# Update task status
mc-update.sh status <task_id> review

# Add comment
mc-update.sh comment <task_id> "Progress update..."

# Complete task
mc-update.sh complete <task_id> "Summary of what was done"
```

## How It Works

1. Human moves task to "In Progress" in dashboard
2. GitHub sends webhook to Clawdbot
3. Transform detects status change
4. Agent receives work order
5. Agent executes task, updates status
6. Human reviews and approves

## Security

Mission Control passes human-authored task descriptions to an AI agent for execution. This is the product's core function — not a vulnerability.

**Trust model:** Designed for single-user / trusted-user setups where the task author is the same person who controls the agent. For multi-user scenarios, use Clawdbot's agent sandbox and permission settings.

**Mitigations included:**
- Input sanitization in `mc-update.sh` (blocks shell injection patterns)
- Webhook HMAC verification with `timingSafeEqual`
- Credential scanning before open-source sync
- No tokens or secrets stored in the dashboard

See [SKILL.md](SKILL.md#security) for full details.

## License

MIT

_meta.json

{
  "ownerId": "kn78wdsd1jkdn10m4bwtrnjntn80d7kk",
  "slug": "mission-control",
  "version": "2.3.1",
  "publishedAt": 1771603328123
}

assets/examples/CONFIG-REFERENCE.md

# Mission Control Configuration Reference

Die Konfigurationsdatei wird unter `~/.clawdbot/mission-control.json` erwartet.

## Felder

### `gateway`

| Feld | Typ | Default | Env Variable | Beschreibung |
|------|-----|---------|--------------|--------------|
| `url` | string | `http://127.0.0.1:18789` | `CLAWDBOT_GATEWAY` | Clawdbot Gateway URL |
| `hookToken` | string | `""` | `CLAWDBOT_HOOK_TOKEN` | Hook Token für authentifizierte Webhook-Aufrufe. Finde in `~/.clawdbot/clawdbot.json` unter `hooks.token` |

### `workspace`

| Feld | Typ | Default | Env Variable | Beschreibung |
|------|-----|---------|--------------|--------------|
| `path` | string | `~/clawd` | `MC_WORKSPACE` | Absoluter Pfad zum Workspace-Verzeichnis |
| `tasksFile` | string | `data/tasks.json` | - | Relativer Pfad zur tasks.json (vom workspace aus) |
| `snapshotFile` | string | `data/.tasks-snapshot.json` | - | Relativer Pfad zum Snapshot für Diff-Berechnung |
| `debugLog` | string | `data/.webhook-debug.log` | - | Relativer Pfad zum Debug-Log |

### `slack`

| Feld | Typ | Default | Env Variable | Beschreibung |
|------|-----|---------|--------------|--------------|
| `botToken` | string | `""` | `SLACK_BOT_TOKEN` | Slack Bot Token (beginnt mit `xoxb-`) |
| `channel` | string | `""` | `SLACK_CHANNEL` | Slack Channel ID (Format: `C0123456789`, ohne #) |

### `secrets`

| Feld | Typ | Default | Beschreibung |
|------|-----|---------|--------------|
| `webhookSecretFile` | string | `~/.clawdbot/secrets/github-webhook-secret` | Pfad zur Datei mit dem GitHub Webhook Secret |
| `githubTokenFile` | string | `~/.config/gh/hosts.yml` | Pfad zur gh CLI Token-Datei |

### `agent`

| Feld | Typ | Default | Beschreibung |
|------|-----|---------|--------------|
| `sessionPrefix` | string | `hook:mission-control` | Session-Prefix für Hook-Agents |
| `defaultTimeout` | number | `300` | Default Timeout für einzelne Tasks (Sekunden) |
| `epicTimeoutBase` | number | `600` | Basis-Timeout für EPICs (Sekunden) |
| `epicTimeoutPerChild` | number | `300` | Zusätzlicher Timeout pro Child-Task bei EPICs |

## Hinweise

- **Alle Felder sind optional** — nicht gesetzte Felder nutzen ihre Defaults
- **Environment Variables überschreiben Defaults**, aber die Config-Datei überschreibt Environment Variables
- **Secrets sollten nie in der Config-Datei stehen** — nutze `secrets.webhookSecretFile` um auf eine separate Datei zu verweisen

## Minimale Config

Wenn du nur die Defaults ändern willst, reicht eine minimale Config:

```json
{
  "gateway": {
    "hookToken": "dein-hook-token"
  },
  "workspace": {
    "path": "/path/to/your/workspace"
  },
  "slack": {
    "botToken": "xoxb-...",
    "channel": "C0123456789"
  }
}
```

assets/examples/HOOKS-CONFIG.md

# Clawdbot Hooks Configuration

This documents the hook-related settings in `~/.clawdbot/clawdbot.json`.

## Example Snippet

Add this to your main Clawdbot config:

```json
{
  "hooks": {
    "enabled": true,
    "token": "your-secure-token",
    "mappings": {
      "github": "github-mission-control.mjs"
    }
  }
}
```

## Fields

### `hooks.enabled`
- **Type:** boolean
- **Default:** `true`
- **Description:** Enable/disable webhook processing globally

### `hooks.token`
- **Type:** string
- **Required:** Yes
- **Description:** Token for authenticating incoming webhooks
- **Usage:** Append `?token=YOUR_TOKEN` to webhook URLs

### `hooks.mappings`
- **Type:** object (key → filename)
- **Description:** Maps webhook paths to transform modules

The key becomes the URL path. Example:
- Key: `"github"`
- URL: `https://your-machine.ts.net/hooks/github?token=...`
- Transform: `~/.clawdbot/hooks-transforms/github-mission-control.mjs`

## Multiple Hooks

You can have multiple webhook endpoints:

```json
{
  "hooks": {
    "mappings": {
      "github": "github-mission-control.mjs",
      "stripe": "stripe-payments.mjs",
      "custom": "my-custom-transform.mjs"
    }
  }
}
```

Each mapping creates:
- URL: `/hooks/{key}?token=...`
- Transform: `~/.clawdbot/hooks-transforms/{filename}`

## Security

1. **Token Required** — All webhook requests must include `?token=` 
2. **HMAC Optional** — Transforms can implement their own signature validation
3. **HTTPS via Funnel** — Tailscale Funnel provides TLS encryption

## Transform Location

Transforms must be placed in:
```
~/.clawdbot/hooks-transforms/
```

The Mission Control transform should be copied here during setup:
```bash
cp <skill>/assets/transforms/github-mission-control.mjs \
   ~/.clawdbot/hooks-transforms/
```

Sponsored

Ads related to Mission Control and adjacent AI workflows.