coo

Designs customer onboarding flows, support SLAs, and operational readiness processes for scaling businesses.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/beelabstudio/ai --skill coo-beelabstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coo
Source: https://github.com/beelabstudio/ai/tree/main/skills/c-level/coo
Command: npx skills add https://github.com/beelabstudio/ai --skill coo-beelabstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Growing businesses struggle to deliver reliably as they scale: onboarding leaks customers, support has no defined SLAs, features ship without runbooks, and manual operational tasks pile up. This Skill provides a Chief Operating Officer perspective that designs the processes, metrics, and escalation paths needed to run operations predictably. ## Core Features & Use Cases - Onboarding & Time-to-Value Design: Builds onboarding funnels measured against a TTV budget, targeting a first value moment within a defined time from signup. - Support Tier & SLA Definition: Defines a four-tier support model (self-serve through engineering) with response-time SLAs and escalation rules, including the rule that any issue repeating 3+ times becomes an engineering fix. - Operational Readiness Gates: Applies a pre-launch checklist covering runbooks, alerting, rollback via feature flags, and updated support content before any feature ships. - Use Case: Before launching a new billing feature, use this Skill to produce an operational decision document covering the support runbook, alert thresholds, rollback path, vendor SLA risks for the payment processor, and the KPI that defines success. ## Quick Start Act as the COO and review the operational readiness of our upcoming subscription billing launch, including support SLAs, runbook needs, and vendor risks.

Frequently Asked Questions about coo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a customer onboarding flow with time-to-value targets?▼

Define what first value means for your product, then break onboarding into steps (account creation, setup, first value moment) each with a time budget. Any step exceeding its budget must be redesigned before launch, with a common target of under 30 minutes total.

How do I define support tiers and SLAs for a SaaS product?▼

Use a four-tier model: Tier 0 self-serve docs, Tier 1 chat support under 4 hours, Tier 2 email and screen share under 24 hours, and Tier 3 engineering under 48 hours. Any Tier 2+ issue repeating 3 or more times becomes an engineering fix rather than a support script.

What should an operational readiness checklist include before launch?▼

A readiness checklist covers a written support runbook, a defined alert metric that triggers incidents, a documented rollback path via feature flag, updated help content, and pre-approved outbound notification templates for channels like WhatsApp or email.

When should manual operational tasks be automated?▼

Apply the scale-without-headcount rule: any operational task occurring more than about 10 times per month must be automated or eliminated. Manual tasks are acceptable early on but should be logged and queued for automation once they cross the threshold.

Does this Skill write code or design product features?▼

No. It deliberately avoids product design and coding, focusing instead on delivery processes, onboarding, support operations, vendor management, and operational metrics. For product flows it defers to CPO or UX skills, and for infrastructure to a DevOps skill.