miso

Telegramでマルチエージェント進捗をリアルタイム表示し、ステータス反映・リアクション・ピン連動でミッションの全過程を可視化します。

This skill appears to implement a legitimate Telegram mission-control UI, but there are mismatches between what it declares and what the code does. Before installing or running it: - Inspect /Users/shunsukehayashi/.openclaw/openclaw.json (or the equivalent OpenClaw config on your system). The helper script expects to read a Telegram bot token there; ensure you understand and control that file and token. - Consider modifying miso_telegram.py to require an explicit environment variable (e.g., MISO_TELEGRAM_BOT_TOKEN) or to prompt for the token rather than reading a hardcoded path. - Verify whether the GIF assets the scripts expect actually exist (assets/progress/* and agent GIFs). The package snapshot here doesn't list an assets/ folder. - Be cautious about automatic state writes: the skill will create/update ~/.openclaw/workspace/skills/mission-control/.miso-state.json per its docs; if you don't want persistent files, run it in an isolated environment or sandbox. - If you don't trust the author or don't want the skill automatically sending messages, do not provide bot credentials or run the scripts that contact Telegram. If you want to proceed but reduce risk: run the code in a disposable environment, supply a test bot token with limited permissions, or change the code to log actions instead of performing network calls until you confirm behavior. If you want higher confidence, ask the author to (1) remove hardcoded user paths, (2) explicitly declare required config paths/credentials in the registry metadata, and (3) require credentials via explicit env vars or an interactive config step.

Type: OpenClaw Skill Name: miso Version: 0.1.3 The skill is classified as suspicious due to a critical vulnerability in `scripts/miso_telegram.py`. This script directly accesses a hardcoded path (`/Users/shunsukehayashi/.openclaw/openclaw.json`) to load the Telegram bot token. While the script uses the token for its intended purpose of interacting with the Telegram API (sending/editing messages, pinning/unpinning), this direct and hardcoded access to a sensitive configuration file containing credentials represents a significant security flaw that could be exploited if the skill is run in an untrusted environment or if the file permissions are misconfigured, potentially leading to token exposure.