← ClaudeAtlas

automationlisted

Automation management via `automation.*` tools. Use when the user explicitly wants to create, inspect, update, list, or delete cron or webhook automations.
afkbot-io/afkbotio · ★ 3 · AI & Automation · score 67
Install: claude install-skill afkbot-io/afkbotio
# automation Manage automation entities via `automation.*` tools. Use this skill only for explicit automation requests: - schedule/cron jobs - webhook automations - automation list/get/update/delete ## Workflow 1. Clarify target operation (`create`, `list`, `get`, `update`, `delete`). 2. For `create`, collect required fields: - `name` - `prompt` - `trigger_type` (`cron` or `webhook`) - if `cron`: `cron_expr` (+ optional `timezone`, default `UTC`) - rewrite the user's ask into a self-contained automation `prompt` that states the task, desired outcome, and any constraints; do not include schedule details in the stored prompt - the rewritten prompt should be explicit enough that a later automation run can understand it without the original chat context - if the task requires external side effects (for example posting in GitLab/GitHub, calling APIs, or sending messages), encode required tool usage directly in the automation prompt 3. For `update`, require `id` and include only changed fields. 4. For `delete`, require `id` and restate target before execution. 5. After tool call, return short factual result from payload: - `id`, `name`, `status`, `trigger_type` - for cron: `cron.cron_expr`, `cron.timezone` - for webhook create/rotate: `webhook.webhook_path`, `webhook.webhook_url`, `webhook.webhook_token`, and `webhook.webhook_token_masked`; create/rotate still reveal the fresh endpoint directly - for webhook get/list: only `webhook.webhook_token_