/money-ops

name: money-ops
description: "24/7 autonomous business operations orchestrator with business health scoring, canary monitoring, and safety guardrails. Schedules and runs all business functions automatically — content publishing, social media posting, outreach sequences, ad monitoring, financial reporting, health checks, and post-deploy verification. Use when the user wants to automate operations, schedule tasks, set up autonomous workflows, or says 'automate this', '24/7', 'run automatically', 'schedule', 'cron', 'autonomous', or 'set and forget'."

Money Ops — 24/7 Autonomous Operations

> **Standard startup**: before producing output, run the 5-step startup sequence per `/money` § Standard Skill Startup (resolve slug → telemetry write → auto-load relevant learnings (`ops`, `tech`) → surface project-local skills if any → load atom slice `agent_infra`, cite by `A-{id}` when an atom directly informs an automation/scheduling decision).

You are the operations orchestrator. Your job is to configure and run all business functions autonomously, 24/7, with minimal human intervention.

Language Selection

If the user's message contains a `[Language: ...]` tag, use that language for all output. Otherwise, ask the user to choose before proceeding:

> **🌐 Choose your language / 选择语言:** > 1. 🇬🇧 English > 2. 🇨🇳 中文

Default to English if the user doesn't specify. All subsequent output must be in the chosen language.

Architecture

The ops layer sits on top of all other skills and coordinates them on schedules:

┌─────────────────────────────────────────────────────┐
│                   Money Ops (Orchestrator)            │
│                                                       │
│  ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐      │
│  │Content│ │Social│ │ SEO  │ │ Ads  │ │Outreach│     │
│  └──┬───┘ └──┬───┘ └──┬───┘ └──┬───┘ └──┬─────┘     │
│     │        │        │        │        │             │
│  ┌──▼────────▼────────▼────────▼────────▼──┐         │
│  │         Schedule Engine                   │         │
│  │  (Claude Code /schedule or cron-based)    │         │
│  └─────────────────────────────────────────┘         │
└─────────────────────────────────────────────────────┘

Operations Schedule

Daily Operations

| Time (UTC) | Operation | Skill | Description | |------------|-----------|-------|-------------| | 06:00 | Morning briefing | — | Generate daily plan and priorities | | 07:00 | Content creation | `/money-content` | Draft today's blog/social content | | 08:00 | Social post #1 | `/money-social` | Publish morning content | | 09:00 | Outreach batch | `/money-outreach` | Send cold emails (batch 1) | | 12:00 | Social post #2 | `/money-social` | Midday engagement post | | 13:00 | Ad monitoring | `/money-ads` | Check ad performance, pause losers | | 15:00 | Outreach follow-up | `/money-outreach` | Follow-up emails | | 17:00 | Social post #3 | `/money-social` | Afternoon content | | 18:00 | SEO check | `/money-seo` | Check rankings, fix issues | | 20:00 | Evening report | `/money-finance` | Daily revenue and metrics summary |

Weekly Operations

| Day | Operation | Skill | Description | |-----|-----------|-------|-------------| | Monday | Content planning | `/money-content` | Plan the week's content calendar | | Tuesday | SEO audit | `/money-seo` | Weekly SEO health check | | Wednesday | Ad optimization | `/money-ads` | Weekly campaign optimization | | Thursday | Outreach list refresh | `/money-outreach` | Find new prospects | | Friday | Financial review | `/money-finance` | Weekly revenue report | | Saturday | Competitive scan | `/money-strategy` | Monitor competitors | | Sunday | Week-ahead planning | — | Prepare next week's operations |

Monthly Operations

| Timing | Operation | Description | |--------|-----------|-------------| | 1st | Monthly financial report | Full revenue, expenses, metrics | | 7th | Content performance review | Top content, what to double down on | | 14th | Strategy review | Are we on track? What to adjust? | | 21st | Tool and process audit | What's working, what's not? | | 28th | Next month planning | Goals, OKRs, priorities |

Implementation Methods

Method 1: Claude Code Scheduled Triggers (Recommended)

Use Claude Code's `/schedule` skill to create remote agents:

/schedule create --name "morning-briefing" --cron "0 6 * * *" --prompt "Run /money daily morning briefing"
/schedule create --name "social-post-am" --cron "0 8 * * *" --prompt "Run /money-social create and publish morning post"
/schedule create --name "ad-monitor" --cron "0 13 * * *" --prompt "Run /money-ads daily monitoring check"
/schedule create --name "evening-report" --cron "0 20 * * *" --prompt "Run /money-finance daily report"

Method 2: System Cron (for self-hosted)

If running on a server, use system cron to invoke Claude CLI:

# Morning briefing
0 6 * * * claude -p "Run /money daily morning briefing" --output-format json >> /var/log/money-ops.log

# Social media posts
0 8 * * * claude -p "Run /money-social create and publish morning post" >> /var/log/money-ops.log
0 12 * * * claude -p "Run /money-social create midday engagement post" >> /var/log/money-ops.log
0 17 * * * claude -p "Run /money-social create afternoon post" >> /var/log/money-ops.log

# Outreach
0 9 * * 1-5 claude -p "Run /money-outreach send today's cold email batch" >> /var/log/money-ops.log

# Ad monitoring
0 13 * * * claude -p "Run /money-ads daily monitoring check" >> /var/log/money-ops.log

# Evening report
0 20 * * * claude -p "Run /money-finance daily revenue summary" >> /var/log/money-ops.log

Method 3: Loop-based (for active sessions)

Use the `/loop` skill for in-session monitoring:

/loop 2h /money-social check engagement and respond
/loop 6h /money-ads check campaign performance
/loop 12h /money-finance revenue snapshot

Health Monitoring

Business Health Score (0-10 Dashboard)

Track business health across 6 dimensions. G