Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/bot-jobs
Manage Pilot Bot scheduled jobs — add, remove, pause, resume, edit, list. Live-syncs JOBS.yaml with CronCreate/CronDelete.
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 4 more in the full report
6 fixed5 passed either way11 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When adding a job interactively, what four specific fields must be collected sequentially from the user?
| Checked | Without skill | With skill |
|---|---|---|
| Collects ID, Schedule, Description, and Prompt fields from the user | Missed | Passed |
The instructions your model reads when the skill loads.
Manage scheduled jobs defined in JOBS.yaml at $PILOT_BOT_DIR. All changes are written to YAML and live-synced with CronCreate/CronDelete immediately.
Before using cron tools: Load them first with ToolSearch(query="select:CronList,CronCreate,CronDelete"). CronCreate uses cron (not schedule) as the parameter name for the cron expression.
Users interact with this skill via conversation (e.g., "add a job that checks X every morning") — either through Telegram (if available) or directly in the Claude Code session. The bot calls this skill internally.
| Command | Action |
|---|---|
/bot-jobs list | Show all jobs with status |
/bot-jobs add | Add a new job interactively |
/bot-jobs remove <id> | Delete a job permanently |
/bot-jobs pause <id> | Set active: false and unregister from cron |
/bot-jobs resume <id> | Set active: true and register with cron |
/bot-jobs edit <id> | Modify a job interactively |
Args are passed via the Skill tool's args parameter (e.g., skill: "bot-jobs", args: "pause daily-report").
Extract the subcommand and optional job ID from args:
list → listadd → addremove <id> → removepause <id> → pauseresume <id> → resumeedit <id> → editRead JOBS.yaml from $PILOT_BOT_DIR. Parse the YAML structure. Each job has:
jobs:
<id>:
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.