Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →get-bb/automations
Create and manage bb automations from the first-party automations plugin.
Passed 18 of 21 test cases with the skill, and 8 of 21 without it.
and 14 more in the full report
12 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
A paused automation `auto_5541` in project `proj_ops` needs to be reactivated so it resumes its regular cron execution schedule. What CLI command reactivates it?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the command bb automation resume auto_5541. | Missed | Passed |
| Specifies the flag --project on the resume command. | Missed | Passed |
The instructions your model reads when the skill loads.
An automation is a scheduled task. When due it runs in one of two modes:
agent Spawn a thread or re-prompt a target thread with a configured prompt. script Run a stored server-side script and capture stdout/stderr/exit.
Use the top-level bb automation command. The CLI routes it to this plugin.
Pass --project explicitly for every automation command. Inside a thread, automations are stamped origin agent and record the creating thread automatically. Automation-spawned threads cannot create automations.
Personal supports automations with --project proj_personal. Use bb project list --include-personal --json to include it in discovery; an empty default project list does not mean Personal is unavailable.
Choosing a mode:
Use script when the output is fully determined by code: watchdogs, threshold alerts, health checks, heartbeats, and API pollers with a fixed output shape. Scripts run on the bb server. New standard-project scripts use the server-host project source when one exists; Personal and projects without one run in the plugin's shared script storage directory. Existing scripts without a saved policy also run there. Use --working-directory automation-storage|project|<absolute-server-path> to select the policy. Script automations do not have an environment field and do not accept environment flags.
Design the script to print nothing when there is nothing to report: an exit-0 run with empty stdout/stderr, or a last non-empty line of {"wakeAgent": false}, is recorded as a skipped silent tick. Any other output is captured; non-zero exit or timeout is recorded as a failed run.
Use agent when the run needs reasoning: summarize a feed, pick interesting items, draft a human-friendly message, or branch on content.
Creating:
bb automation create --project <id> --name "..." [schedule flags] [mode flags]
For creation flags and mode-specific defaults, read references/creation.md.
Read references/script-runtime.md before you use a script file, depend on
injected variables, or diagnose retries, timeouts, restarts, and silent runs.
Managing:
bb automation list --project <id>
bb automation show <automationId> --project <id>
bb automation update <automationId> --project <id> [--name <name>] [schedule flags] [complete execution flags | partial agent update flags]
bb automation pause <automationId> --project <id>
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.