bot-boot
Pilot Bot boot sequence — health check, job registration, heartbeat setup
npx skills add majiayu000/claude-skill-registry --skill bot-boot --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bot Boot Skill Boot orchestrator for Pilot Bot. Runs on every bot session start via `pilot bot`. The bot is an automation agent — scheduled tasks, background jobs, 24/7 operation. Telegram integration is optional (auto-detected). Environment variables available: - `PILOT_BOT_MODE=1` — confirms bot context - `PILOT_BOT_DIR` — path to `~/.pilot/bot/` (contains JOBS.yaml) ## Execution **Phase 1** — Single message with parallel tool calls (foreground + background agents): | # | Type | Action | |---|------|--------| | 1 | **Foreground** | Read `$PILOT_BOT_DIR/JOBS.yaml` to understand current job configuration. | | 2 | **Background Agent** | **MCP health check** — silent check, no greeting (see below) | **Phase 2** — After Phase 1 completes, register crons in the **main session** (Cron tools are not available to subagents): | # | Action | |---|--------| | 3 | **Heartbeat registration** — First load tools: `ToolSearch(query="select:CronList,CronCreate")`. Then use CronList to check if a heartbeat cron already exists (look for 'bot-heartbeat' in prompt text). If it already exists, do nothing. If not found, use CronCreate with `cron='*/30 * * * *'` and `prompt='Run /bot-heartbeat skill (i
- Execution
- #2 MCP health check
- Done
- Usage
What does the bot-boot skill do?
Pilot Bot boot sequence — health check, job registration, heartbeat setup
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill bot-boot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.