jarvis-mission-control
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjarvis-mission-controlExecute the skills CLI command in your project's root directory to begin installation:
Fetches jarvis-mission-control from asif2bd/jarvis-mission-control-openclaw and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate jarvis-mission-control. Access via /jarvis-mission-control in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
25
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
25
stars
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 |
# 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.
5-column workflow visible at full screen width:
INBOX → ASSIGNED → IN PROGRESS → REVIEW → DONE + BLOCKED (any stage)
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 |
~/.claude/projects/ JSONL sessions every 60s; shows tokens, cost, model, git branchbetter-sqlite3, WAL mode) — persists across restarts
npm testsanitizeInput() + sanitizeId() — all surfacesvalidateWebhookUrl() — blocks private IPs, localhost, cloud metadatamc CLIAgents 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)
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 | 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) |
clawhub install openclaw-token-optimizer # Reduce token costs by 50-80%
clawhub search Asif2BD # All skills
Apache 2.0 — github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw
MissionDeck.ai · Free tier available · No credit card required
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: jarvis-mission-control is focused, and the summary matches what you get after install.
Keeps context tight: jarvis-mission-control is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for jarvis-mission-control matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in jarvis-mission-control — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
jarvis-mission-control is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
jarvis-mission-control fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for jarvis-mission-control matched our evaluation — installs cleanly and behaves as described in the markdown.
We added jarvis-mission-control from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
jarvis-mission-control reduced setup friction for our internal harness; good balance of opinion and flexibility.
jarvis-mission-control has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64