add-automation

⚠️ Before any call to wrangler (to be done BEFORE any other wrangler command in this skill)

eval "$(node "${CLAUDE_SKILL_DIR}/../../scripts/wrangler-env-init.mjs")"

This line loads CLOUDFLARE_API_TOKEN from the User scope (Windows registry / shell rc on Mac/Linux) if it is not in process.env, and adds the pnpm bin to the PATH (for bash sessions where pnpm setup has not yet propagated). Without it, wrangler fails with "command not found" on Mac (Spotlight), or may use a different Cloudflare account than the one the user expects.

Add Automation - Discovery & routing

You help the user add an automation: to their project, or to their own toolkit.

Communication

• Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like /bootstrap carries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim.
• Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms.
• When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
• Show progress as a short natural-language checklist (in-progress and done states).

This skill is mostly orchestration. Your job is:

1. Understand what the user actually wants
2. Infer WHO the automation serves: the app, or the operator (see "The app/ops split")
3. Decide on the right architecture and recommend it with reasons
4. Invoke the right helper skill to do the actual work

You will rarely write code yourself in this skill - you delegate to:

• add-cron - scheduled tasks that fit in a Vercel function (< 60s, stateless). Uses the unified shared hypervibe-jobs worker by default (1 Cloudflare slot for everything).
• _create-workflow - finite event-triggered pipelines running INSIDE the app (2-8 known steps, some intelligent through the project's AI brick, bounded duration). The most common shape behind "I want an agent".
• _create-routine - operator-side recurring AI missions (a Claude routine on the user's own account). Direct user entry: add-routine (thin front over the same engine - when routing from here, call the engine directly).
• _create-agent - AI-driven processes that are part of the PRODUCT (serve the app's end users) with a true agentic loop or autonomy
• _setup-wrangler - installs Wrangler CLI if missing
• _setup-render - ensures the Render API key is in the vault (Render via REST API, no CLI)
• _convert-to-turborepo - converts the project to a monorepo (idempotent)
• _create-cloudflare-worker - scaffolds and deploys a Cloudflare Worker in apps/worker/
• _create-render-worker - scaffolds a Render background process in apps/worker/ (free web service by default, paid background worker on request)