// the find
Lifecycle-Innovations-Limited/claude-ops
Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue (Stripe+RevenueCat), e-commerce (Shopify), marketing (Klaviyo/Meta/GA4), voice (Bland/ElevenLabs), APM (Datadog/NewRelic/OTEL), YOLO mode.
claude-ops is a Shell-based Claude Code plugin that turns the CLI into a business-operations layer: unified inbox across WhatsApp/Slack/Telegram/Email, autonomous PR merging with auto-fix, AWS/CI monitoring, revenue tracking (Stripe/RevenueCat), e-commerce and marketing dashboards, and even outbound voice calls. It's aimed at solo founders or small teams already living in Claude Code who want one tool replacing a dozen SaaS dashboards and manual status checks.
There's real engineering around the risky parts: per-repo hourly budget caps on the auto-fix subsystem, single-flight locks, and content-hash dedup to stop runaway LLM spend on repeated failures. The Agent Teams design (TeamCreate/SendMessage) lets scanner subagents share findings instead of running in isolation, and a CI test (test-agent-teams.sh) actually audits every skill for compliance rather than just documenting the pattern. The credential resolution chain tries password managers and OS keychain before falling back to plaintext env vars, and the privacy section is specific about what the setup wizard scans rather than a vague reassurance.
Everything is Shell - orchestrating dozens of skills and 22 external API integrations (Stripe, AWS, Twilio, Bland, Shopify) in bash means no real unit testing of business logic and a much larger blast radius for a quoting bug or injection when LLM output gets piped into shell commands. The README can't agree with itself on scope: the badge claims 66 skills, the TOC says 57, agent counts flip between 21 and 12 across sections - for a tool whose job is reporting numbers accurately, that's a bad look. Autonomous PR merging and 'YOLO mode' are the highest-risk features and get the thinnest explanation up front - the actual guardrails live in a separate doc rather than next to where the feature is introduced. Trying to cover inbox, CI, AWS, revenue, e-commerce, marketing, and voice in one plugin means no single integration gets deep treatment; a tool focused on just PR automation or just revenue tracking will likely do that one job better.