菜单
Gracefully shut down a named project-lead and archive its memory. Use when the user says "shut down <project>", "kill <project>", "stop <project>", or "we're done with <project>".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Phase-1 FREE-only parallel task dispatch for a pilot lead. Load this skill (via the lead brief) only when HERMES_LEAD_PARALLELISM=1 is set in the lead's environment. When the flag is absent, ignore this skill entirely -- the lead must behave byte-identically to the serial baseline.
Auto-loaded when the user's incoming message has `voice_in: true` meta. Interprets the transcribed user intent and routes to the appropriate skill, team, or tool call. Always prefers acting over asking a clarifying question when the intent is reasonably clear from voice.
Generate or edit an image by delegating to the user's Codex CLI subscription. Use when the user requests "draw / render / generate / create / sketch / design an image of X" or similar. Returns a local PNG path which the Telegram channel will upload as a photo.
End-to-end social-media campaign publish. Gathers raw materials (transcript, video frames, screenshots, README) from a tutorial video and supporting links, generates branded diagrams via codex, writes per-platform content, then drives the platform-specific poster agents to draft or publish on each platform. Use when the user says "publish my build log", "launch a social campaign", or "ship this to X + LinkedIn + Medium" (any subset).
Generate an image via the grok CLI (/imagine command). Returns a local PNG/JPG path. Used as one of the two providers in parallel dual-image dispatch (the other is codex-image-gen). Do NOT call this inline — always dispatch via Agent so the channel stays responsive.
Schedule a one-shot Telegram reminder or a recurring cloud routine. For one-shot reminders ("remind me in 5m", "remind me tomorrow at 9am"), use mcp__hermes_api__schedule_reminder (primary path). For recurring cloud routines ("every weekday at 9am, do X"), use the RemoteTrigger path (legacy).
| name | kill-project |
| description | Gracefully shut down a named project-lead and archive its memory. Use when the user says "shut down <project>", "kill <project>", "stop <project>", or "we're done with <project>". |
| allowed-tools | ["mcp__project-orchestrator__kill_project","mcp__project-orchestrator__get_status","SendMessage"] |
Resolve the project's agent_id via mcp__project-orchestrator__get_status.
Send a graceful shutdown request via SendMessage:
SendMessage(to: "<agent_id>",
message: {"type": "shutdown_request",
"reason": "user requested kill"})
Mark killed in the registry: mcp__project-orchestrator__kill_project(name, archive=true).
Confirm to the user: "Hibernated f1-tracker. Memory archived. Spin it back up anytime."