bundles/planning/skills/business-operator/SKILL.md
Orchestrates multiple business ventures using Hormozi portfolio frameworks, prioritizing which to focus on and routing to specialized skills. Triggers when a user manages multiple products or businesses, asks "which business should I focus on," needs cross-venture resource allocation, or wants a portfolio-level health check.
npx skillsauth add shipshitdev/library business-operatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrates Hormozi business frameworks across a portfolio of ventures, identifying which business needs attention, what specific actions to take, and which specialized skill to deploy.
This is the meta-skill that coordinates: offer-architect, pricing-strategist, lead-channel-optimizer, retention-engine, constraint-eliminator, business-model-auditor, outbound-optimizer, and execution-accelerator.
Hormozi Portfolio Principle: "Focus beats diversification, but the right portfolio multiplies returns."
Score each business on:
Priority Score = (Revenue × Traction × Leverage) / Effort
Ask the user:
"List all your active businesses/products. For each one, tell me:
- What is it? (one sentence)
- Current monthly revenue (or $0 if pre-revenue)
- Growth trend (growing/flat/declining)
- Hours you spend per week on it"
For each business, gather:
For each business, identify which Hormozi framework is needed most:
| Problem Detected | Route To |
|-----------------|----------|
| Weak/confusing offer | offer-architect |
| Underpriced, leaving money on table | pricing-strategist |
| Not enough leads/customers | lead-channel-optimizer |
| High churn, low LTV | retention-engine |
| Customers struggling to succeed | constraint-eliminator |
| Can't scale, you're the bottleneck | business-model-auditor |
| Outbound isn't converting | outbound-optimizer |
| Stuck, can't decide, overthinking | execution-accelerator |
Calculate priority score for each business:
Priority = (Revenue Potential × Current Traction × Leverage) / Effort Required
Where each factor is scored 1-10:
- Revenue Potential: Market size × pricing power
- Current Traction: Customers × growth rate × retention
- Leverage: Can it run without you? (10 = fully automated, 1 = you ARE the product)
- Effort Required: Your weekly hours (inverted: 1 hour = 10, 40 hours = 1)
For each business, output:
[Business Name]
See assets/output-template.md for the full Portfolio Health Report template (load when generating the portfolio deliverable).
After analysis, route to the appropriate skill:
offer-architectTriggers:
pricing-strategistTriggers:
lead-channel-optimizerTriggers:
retention-engineTriggers:
constraint-eliminatorTriggers:
business-model-auditorTriggers:
outbound-optimizerTriggers:
execution-acceleratorTriggers:
This skill orchestrates but doesn't replace the specialized skills:
| Skill | When Business-Operator Routes Here |
|-------|-----------------------------------|
| offer-architect | Offer clarity/conversion issues detected |
| pricing-strategist | Underpricing or pricing confidence issues |
| lead-channel-optimizer | Lead generation is the bottleneck |
| retention-engine | Churn is killing growth |
| constraint-eliminator | Customer success is blocked |
| business-model-auditor | Scale/leverage problems identified |
| outbound-optimizer | Direct sales channel needs help |
| execution-accelerator | User is stuck or overthinking |
Also integrates with existing skills:
leads-researcher - For identifying new customer segmentscopywriter - For messaging across businessesstripe-implementer - For payment/billing implementationUser: "I have 3 businesses and I'm stretched too thin. Help me figure out what to focus on."
Business Operator Response:
Let me help you prioritize. Tell me about each business:
For each business, share:
- What is it? (one sentence)
- Monthly revenue
- Growth trend (growing/flat/declining)
- Hours you spend per week
- Biggest current challenge
I'll run a Hormozi analysis on your portfolio and give you:
- Priority rankings with scores
- Which business gets focus this week
- The specific skill/framework each business needs
- A concrete action plan
Sometimes the answer is to kill a business. Consider killing when:
Before killing, ask:
Route to execution-accelerator if:
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.