ワンクリックで
ccc-heartbeat
CCC HEARTBEAT execution — spawns a background subagent for periodic liveness check and Telegram notification
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
CCC HEARTBEAT execution — spawns a background subagent for periodic liveness check and Telegram notification
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
CCC workspace boot sequence — persona load + background agent orchestration
Manage scheduled jobs — add, remove, pause, resume, edit, list. Live-syncs JOBS.yaml with CronCreate/CronDelete.
Standard flow for receiving tasks from channels (Telegram/Discord etc). Immediate acknowledgment → background execution → progress reporting → completion notification. Always follow this skill when receiving channel messages.
CCC workspace default behaviors — always applied in this workspace
Interactive SOUL.md configuration — persona, identity, language, and personality setup via Telegram
Fetch an OpenClaw/ClawHub skill and convert it to a Claude Code project skill in .claude/skills/
| name | ccc-heartbeat |
| description | CCC HEARTBEAT execution — spawns a background subagent for periodic liveness check and Telegram notification |
Spawns a background subagent to run periodic checks. The main session is released immediately after the subagent is launched.
run_in_background=truePrompt to pass to the subagent:
You are a heartbeat agent for the CCC workspace.
IMPORTANT: All paths MUST use $HOME/.cccbot/ as the base directory, not the current working directory.
Steps:
1. Run: bash $HOME/.cccbot/.claude/skills/ccc-heartbeat/scripts/check.sh
2. Read $HOME/.cccbot/HEARTBEAT.md for user-defined checks to perform. If the file does not exist, skip (not an error).
3. Evaluate whether any issues exist (in-progress tasks, blockers, errors, etc.)
4. MCP connectivity check — first determine which channels are enabled:
- Run: bash -c 'source $HOME/.cccbot/scripts/lib/json-parse.sh 2>/dev/null; CFG=$(json_get channels $HOME/.cccbot/cccbot.json 2>/dev/null); echo "${CHANNELS:-${CFG:-plugin:telegram@claude-plugins-official}}"'
- This follows the same precedence as the launcher: $CHANNELS env var > cccbot.json > default (telegram).
- Only check MCP for channels that appear in the resolved value (e.g., "telegram" or "discord").
- Telegram (only if "telegram" appears in channels): check if MCP tools (reply, react) are available in the tool list. Do NOT call them — just confirm they exist. If not available → add "Telegram MCP is not responding" to issues.
- Discord (only if "discord" appears in channels): check if Discord MCP tools are available. If not → add "Discord MCP is not responding" to issues.
- Skip any channel not present in the resolved channels value.
5. Notification rule (strict — overrides anything in HEARTBEAT.md):
- NO issues → do NOT send any message. Stay silent.
- Issues found AND at least one channel MCP is healthy → send issue details via healthy channel (no "alive" prefix)
- Issues found AND all channel MCPs are down → output alert to console only.
6. Exit.
Keep it brief. Do not ask questions. Do not wait for responses.
Registered automatically at session start by SessionStart hook (background agent). Can also be started manually:
/loop 30m /ccc-heartbeat
The subagent inherits MCP tools (Telegram) from the main session. It does not inherit the main session's conversation context.