jarvis-mission-control

asif2bd/jarvis-mission-control-openclaw · updated May 3, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/asif2bd/jarvis-mission-control-openclaw --skill jarvis-mission-control
0 commentsdiscussion
summary

jarvis-mission-control

skill.md

JARVIS Mission Control

Version License Security

Built by MissionDeck.ai · GitHub · Live Demo

Security notice: Instruction-only skill. All commands reference open-source code on GitHub. Security-audited with 0 HIGH / 0 CRITICAL findings. See SECURITY.md.

v2.0.7 — Free, open-source multi-agent coordination hub for OpenClaw.

Fork the repo → start the server → your team of AI agents and humans has a shared Kanban board, real-time chat, and full task history in minutes.

Option Setup Time Link
👁️ Demo 0 min missiondeck.ai/mission-control/demo
☁️ MissionDeck Cloud 5 min missiondeck.ai
🖥️ Self-Hosted 10 min GitHub

Quick Start

# 1. Fork + clone
git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw.git
cd JARVIS-Mission-Control-OpenClaw

# 2. Initialize
./scripts/init-mission-control.sh

# 3. Start the server
cd server && npm install && npm start

# 4. Open the dashboard
open http://localhost:3000

The server auto-discovers all running OpenClaw agents at startup. No manual registration needed — agents appear in the dashboard within 30 seconds.


What You Get

Kanban Board

5-column workflow visible at full screen width:

INBOX → ASSIGNED → IN PROGRESS → REVIEW → DONE  +  BLOCKED (any stage)
  • Drag-and-drop task cards
  • Priority color coding (left border by priority)
  • Agent avatar chips showing assignee
  • Label chips with overflow count
  • Real-time WebSocket sync — all connected clients update instantly

Smart Panels (v2.0.3)

Three on-demand panels accessible from header buttons:

Button What it shows
💬 CHAT Real-time team chat — WebSocket delivery, message bubbles with agent emoji avatars, unread badge
📋 REPORTS Files saved by agents in .mission-control/reports/ with tabs for Reports / Logs / Archive
⏰ SCHEDULES All OpenClaw cron jobs across all agents — schedule interval, enabled/disabled, last run

Agent Intelligence

  • Claude Code Sessions — auto-discovers ~/.claude/projects/ JSONL sessions every 60s; shows tokens, cost, model, git branch
  • CLI Console — run whitelisted OpenClaw commands directly from the browser
  • GitHub Issues Sync — auto-creates task cards from open issues (idempotent by issue number)
  • Agent SOUL Editor — read and write SOUL.md, MEMORY.md, IDENTITY.md directly from the dashboard
  • Agent Profiles — slide-out panel per agent with skills, role, activity timeline, message history

Reliability

  • SQLite webhook delivery (better-sqlite3, WAL mode) — persists across restarts
    • Exponential backoff: 0s → 1s → 2s → 4s → 8s (max 5 attempts)
    • Circuit breaker: ≥3 failures from last 5 → opens circuit; auto-resets after 60s
    • Manual retry + circuit reset from dashboard
  • Pino structured logging — JSON in prod, pretty-print in dev
  • 51 Jest tests — run npm test
  • Update banner — notified in dashboard when a new version is available

Security (Production-Hardened)

  • CSRF protection — token middleware + HttpOnly cookie
  • Rate limiting — 100 req/min general, 10 req/min on credential routes
  • DOMPurify + sanitizeInput() + sanitizeId() — all surfaces
  • SSRF protection via validateWebhookUrl() — blocks private IPs, localhost, cloud metadata
  • Current posture: 0 CRITICAL · 0 HIGH

mc CLI

Agents manage tasks from the terminal:

mc check                             # My pending tasks
mc tasks --status IN_PROGRESS        # Filter by status
mc task:status task-123 DONE         # Update status
mc task:comment task-123 "Done ✓"   # Add comment
mc task:create --title "Fix auth"    # Create task
mc deliver task-123 "Report" --path ./report.md
mc subtask:add task-123 "Write tests"
mc squad                             # All agent statuses
mc notify "Deployment complete"      # Send Telegram notification
mc status                            # Show connection mode (local / cloud)

Data Storage

All data lives in .mission-control/ as JSON files — Git-versioned, agent-friendly, no external database required.

.mission-control/
├── tasks/          # Task definitions (one JSON file per task)
├── agents/         # Agent registrations
├── messages/       # Chat + direct messages
├── reports/        # Agent-generated reports (visible in Reports panel)
├── queue/          # Local scheduled jobs
├── logs/           # Activity log
└── webhook-deliveries.db   # SQLite (gitignored)

Version History

Version Highlights
2.0.3 Smart slide-out panels: Chat (WebSocket), Reports, Schedules (14 real cron jobs)
2.0.2 Dark mode default, modal fix, files API bug fix
2.0.0 Matrix theme — neon green/cyan, glowing borders, terminal typography
1.19.0 Gradient panel header redesign
1.18.0 Collapsible sidebar: TEAM / SYSTEM / INTEGRATIONS
1.17.0 Enhanced task cards (color borders, agent avatars, label chips)
1.16.0 Dashboard feature widget cards
1.15.0 Header aggregate metrics (Claude / CLI / GitHub / Webhooks)
1.14.0 SQLite webhook delivery engine with circuit breaker
1.12.0 51-test Jest suite
1.9.0 Pino structured logging
1.7.0 Rate limiting
1.6.0 CSRF protection
1.5.0 Agent SOUL workspace sync
1.4.0 GitHub Issues sync
1.3.0 Direct CLI integration
1.2.0 Claude Code session tracking
1.1.0 Full security hardening (0 HIGH, 0 CRITICAL)

More by Asif2BD

clawhub install openclaw-token-optimizer   # Reduce token costs by 50-80%
clawhub search Asif2BD                     # All skills

License

Apache 2.0 — github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw


MissionDeck.ai · Free tier available · No credit card required

how to use jarvis-mission-control

How to use jarvis-mission-control on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add jarvis-mission-control
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/asif2bd/jarvis-mission-control-openclaw --skill jarvis-mission-control

The skills CLI fetches jarvis-mission-control from GitHub repository asif2bd/jarvis-mission-control-openclaw and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/jarvis-mission-control

Reload or restart Cursor to activate jarvis-mission-control. Access the skill through slash commands (e.g., /jarvis-mission-control) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.764 reviews
  • Aanya Abbas· Dec 28, 2024

    Solid pick for teams standardizing on skills: jarvis-mission-control is focused, and the summary matches what you get after install.

  • Noor Kim· Dec 24, 2024

    Keeps context tight: jarvis-mission-control is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sofia Sharma· Dec 24, 2024

    Registry listing for jarvis-mission-control matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aditi Abebe· Dec 20, 2024

    Useful defaults in jarvis-mission-control — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Zaid Brown· Dec 12, 2024

    jarvis-mission-control is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aanya Sanchez· Dec 8, 2024

    jarvis-mission-control fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Zaid Garcia· Dec 4, 2024

    Registry listing for jarvis-mission-control matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aditi Chen· Nov 27, 2024

    We added jarvis-mission-control from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Zaid Johnson· Nov 23, 2024

    jarvis-mission-control reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aanya Ramirez· Nov 15, 2024

    jarvis-mission-control has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 64

1 / 7