Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/bot-boot
Pilot Bot boot sequence — health check, job registration, heartbeat setup
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 9 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Phase 3, if Telegram tools were determined unavailable during Phase 1, what fallback reporting should occur?
| Checked | Without skill | With skill |
|---|---|---|
| Logs 'Pilot Bot online (no Telegram)' to the console | Missed | Passed |
The instructions your model reads when the skill loads.
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 contextPILOT_BOT_DIR — path to ~/.pilot/bot/ (contains JOBS.yaml)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 (invoke Skill tool with skill=bot-heartbeat)'. |
| 4 | Jobs registration — Read JOBS.yaml from $PILOT_BOT_DIR. If missing or empty (jobs: {}), skip. Otherwise use CronList to get existing crons, then for each job with active: true, register via CronCreate with cron='<schedule>' and prompt='<prompt>' if not already registered (match by job ID in prompt content). |
description='MCP health check', run_in_background=true. Prompt:
Check MCP health silently. Do NOT send any message to any channel.
1) Check if Telegram MCP tools (reply, react) are available in the tool list. Do NOT call them — just confirm they exist. Track telegram_available.
2) If tools are not available on first check, wait 5s and recheck (up to 3 attempts).
3) Log result to console: 'Telegram: available' or 'Telegram: not available (bot will run without messaging)'.
4) Exit. Do NOT send any message via reply or any other channel tool.
Phase 3 — Boot completion (main session, after Phase 2):
test cases passed, vs 5 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.