How do I install the Miso skill?

Run npx skillmds@latest add javimosch/miso in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Miso skill do?

Mission Control - MISO It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Miso?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

javimosch (@javimosch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Miso by javimosch — Agent Skill

Name: Miso
Author: javimosch

File contents

Mission Control - MISO

Overview

MISO is a Telegram-native mission control for OpenClaw multi-agent workflows. It standardizes visibility for parallel work so operators can track progress from the chat list.

State model

INIT → RUNNING → PARTIAL → AWAITING APPROVAL → COMPLETE (+ ERROR)

State reactions:

🔥 : INIT / RUNNING / PARTIAL
👀 : AWAITING APPROVAL
🎉 : COMPLETE
❌ : ERROR

Message format (required)

Use plain text, no code blocks.

Left aligned
Keep this frame:
- 🤖 MISSION CONTROL
- ——————————————
- 🌸 powered by miyabi

Template:

🤖 MISSION CONTROL —————————————— 📋 {mission} ⏱ {elapsed} ∣ 🧩 {done}/{total} agents ∣ {state}

Issue: #{issue-number}
Owner: SHUNSUKE AI
Goal: {goal}

↳ {agent-a}: {status-a} ↳ {agent-b}: {status-b} ↳ {agent-c}: {status-c}

Next: {next action} —————————————— 🌸 powered by miyabi

Commands

Comment on Issue with:

/agent analyze
/agent execute
/agent review
/agent status
/task-start
/task-plan
/task-close

/task-start

Owner: SHUNSUKE AI
Issue/Context: #
Goal:
Scope: <files/areas>
Completion Criteria:
Risk: <none|low|medium|high>

/task-plan

/task-plan Execution plan:

issue-analysis
agent-execution (or agent-teams / ai-triad)
git-workflow
debugging-troubleshooting

/task-close

Implemented:
Validation: <tests/checks passed>
Changes:
Risks / next steps:
Notify: pushcut / telegram-buttons

Reproducibility rules

Same header/footer for all missions.
Keep state and status updates deterministic.
Include Issue, Goal, Status, Next action every update.
For approvals, use explicit AWAITING state and user action.
On completion/error, close each mission with state summary and artifacts.

---name: misodescription: Mission Control - MISO---# Mission Control - MISO## Overview**MISO** is a Telegram-native mission control for OpenClaw multi-agent workflows.It standardizes visibility for parallel work so operators can track progress from the chat list.## State model`INIT` → `RUNNING` → `PARTIAL` → `AWAITING APPROVAL` → `COMPLETE` (+ `ERROR`)State reactions:- `🔥` : INIT / RUNNING / PARTIAL- `👀` : AWAITING APPROVAL- `🎉` : COMPLETE- `❌` : ERROR## Message format (required)Use plain text, no code blocks.- Left aligned- Keep this frame: - `🤖 MISSION CONTROL` - `——————————————` - `🌸 powered by miyabi`Template:🤖 MISSION CONTROL——————————————📋 {mission}⏱ {elapsed} ∣ 🧩 {done}/{total} agents ∣ {state}- Issue: #{issue-number}- Owner: SHUNSUKE AI- Goal: {goal}↳ {agent-a}: {status-a}↳ {agent-b}: {status-b}↳ {agent-c}: {status-c}- Next: {next action}——————————————🌸 powered by miyabi## CommandsComment on Issue with:- `/agent analyze`- `/agent execute`- `/agent review`- `/agent status`- `/task-start`- `/task-plan`- `/task-close`## /task-start/task-start- Owner: SHUNSUKE AI- Issue/Context: #<issue-number>- Goal: <one-sentence objective>- Scope: <files/areas>- Completion Criteria: <what defines done>- Risk: <none|low|medium|high>## /task-plan/task-planExecution plan:- issue-analysis- agent-execution (or agent-teams / ai-triad)- git-workflow- debugging-troubleshooting## /task-close/task-close- Implemented: <summary>- Validation: <tests/checks passed>- Changes: <files changed>- Risks / next steps: <follow-up>- Notify: pushcut / telegram-buttons## Reproducibility rules1. Same header/footer for all missions.2. Keep state and status updates deterministic.3. Include `Issue`, `Goal`, `Status`, `Next action` every update.4. For approvals, use explicit AWAITING state and user action.5. On completion/error, close each mission with state summary and artifacts.

Frequently asked questions

Miso