Automation Ops Skills getting started

Name: Automation Ops Skills
SKU: guide

Before you buy

This is downloadable code, configuration examples and operating documentation to set up on your computer. You must install tools, connect accounts and review output. Uploading the ZIP to a web chat does not start the pipeline. Setup services, AI subscriptions, API credits and hosting are not included. Setup and first-output time depend on your environment.

The instructions target macOS and a terminal. Linux and Windows/WSL require changes to shells, paths, fonts, browser connections, notifications and scheduling; unchanged operation is not guaranteed. Start with one account and one output. Local jobs do not run while the computer is off or asleep.

Do I need both Claude and Codex subscriptions?

No. Start with one supported cloud CLI that your account can access, with enough remaining usage. Multiple engines provide alternatives when a provider is unavailable. An installation assistant and the CLI invoked by the scripts are separate: signing into a desktop app does not establish that CLI authentication is ready.

Option	Access needed	Cost and limits
Claude Code	Pro/Max, an eligible Team/Enterprise account, or Console API billing	Free Claude web chat does not include Claude Code. API usage is billed separately from subscriptions.
Codex CLI	A ChatGPT plan with CLI access, such as Plus/Pro, or an OpenAI API billing account	Do not equate Free/Go app access with CLI automation access. API-key use incurs API charges.
Gemini CLI	Supported Google sign-in or API authentication	Check the allowance for your account and authentication method. An API key does not imply free usage.
Ollama	Local models and computing resources	Requires memory, storage, power and time. Run only when the resource guard admits the job.

Set the engine order to the CLI you use. Image, voice and video APIs may charge separately from a text CLI subscription. Total running cost includes your chosen AI access, media generation and hosting/execution, in addition to the pack. Measure a single output before scheduling; no fixed monthly running cost is promised. Check provider billing and budget controls first.

Official documentation checked on 2026-09-28; check again before paying because plans, limits and models change.

Ask your installation assistant

Open the extracted folder in Claude Code or Codex and use this request. The assistant consumes your account's usage too. Enter secrets locally, not in chat.

Read docs/START-HERE.md and the README in this folder.
Check my OS, tools and the one cloud CLI I plan to use, including authentication.
Separate required tools, optional tools and additional charges.
Do not overwrite existing .env/config files or print secrets.
Keep schedulers, uploads, publishing and comment DMs disabled.
After checks, help me generate one local output only.
Identify unfinished adapters and failures explicitly.
Show output paths and the human review checklist. Stop before publishing.

Precautions

Keep .env, tokens, browser profiles and private source material out of public repositories and support requests. Back up existing settings; compare new examples rather than overwriting your configuration.
Review facts, numbers, sources and rights to images, video, music and voices. Check applicable platform and regional disclosure requirements for affiliate links. Automated review does not replace human review.
Do not force local-only drafts out of hold by editing their status. Review and revise them through the intended approval flow.
DRY=1 is a planning option only where the runner supports it. Generation with publishing disabled still consumes CLI/API usage and writes files. Adding an arbitrary --dry flag does not make a command safe.
To stop automation, disable registered dagu/launchd/cron/Actions schedules, then check posts already scheduled on the platform separately. Stopping local jobs does not cancel existing platform schedules.

Troubleshooting

Symptom	Next check
Command/module missing	Virtual environment, PATH and required tool installation; run the CLI's version command
Login error / 401 / 403	Account, channel, authentication method, token expiry and permissions; log in yourself
Quota / 429 / insufficient credits	Provider usage and billing; do not retry repeatedly or delete cooldown files
rc=75 / RESOURCE_DEFERRED	Another job, memory pressure or load; retry later without deleting locks
Output exists but is not published	Test flags, holds, review failures and publishing policy; a file is not proof of publishing
Browser step stopped working	Login expiry or changed platform UI; inspect that stage and sign in manually

For support, provide the pack and ZIP version, OS, failing stage/command, expected result and last 20 error lines with secrets removed. Never send keys, cookies or your full .env. See docs/HUMAN-STEPS.md for the operating checklist and docs/PIPELINE.md for the stage reference.

First use

Open START-HERE.html. Run python3 onboarding.py check, python3 onboarding.py init, then python3 onboarding.py sample for an offline exercise. Follow the README to connect only the tools you need.