Content operations monitor via custom loop.md
A marketing-facing loop.md playbook that turns a bare /loop into a recurring content-ops sweep: checks GA4 for week-over-week organic traffic drops, scans GSC for position 4-15 query opportunities, and audits WordPress posts for broken internal links and missing meta descriptions — reporting one line when everything is green.
Implementation note
Requires GA4/GSC/WordPress access via MCP connectors before it can do anything useful — without them the loop will hallucinate or no-op. Step 3 lets the agent fix issues silently below a threshold; run with a scoped WordPress account and review the first few iterations before trusting silent fixes. Replace kokasexton.com with your own property. Loops expire after 7 days by default in Claude Code, which caps runaway cost.
More automation loops
Ship production-grade apps autonomously
Hand an idea to Claude Code; it authors specs, designs, builds, tests, secures, and ships until enterprise done or budget exhausted.
claude-progress.txt harness pattern (Anthropic)
Anthropic's first-party file-as-memory harness for long-running agents: every fresh-context session recovers state from a progress file and the git log, does one unit of work, updates the file, commits, and exits.
Complete all tasks in tasks.md
Work through your tasks.md file, completing each task until none remain or max iterations is reached.