Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Telegramでマルチエージェント進捗をリアルタイム表示し、ステータス反映・リアクション・ピン連動でミッションの全過程を可視化します。
Telegramでマルチエージェント進捗をリアルタイム表示し、ステータス反映・リアクション・ピン連動でミッションの全過程を可視化します。
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
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. Summarize what changed and any follow-up checks I should run.
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.
INIT → RUNNING → PARTIAL → AWAITING APPROVAL → COMPLETE (+ ERROR) State reactions: 🔥 : INIT / RUNNING / PARTIAL 👀 : AWAITING APPROVAL 🎉 : COMPLETE ❌ : ERROR
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
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: #<issue-number> Goal: <one-sentence objective> Scope: <files/areas> Completion Criteria: <what defines done> Risk: <none|low|medium|high>
/task-plan Execution plan: issue-analysis agent-execution (or agent-teams / ai-triad) git-workflow debugging-troubleshooting
/task-close Implemented: <summary> Validation: <tests/checks passed> Changes: <files changed> Risks / next steps: <follow-up> Notify: pushcut / telegram-buttons
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.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.