Skip to content
Back to skills

Business

ASecurity

Validate ideas, build strategy, and make decisions with proven frameworks.

  • 16 stars
  • 0 votes
  • 1 copy
  • 5 views
  • Added June 7, 2026
businessgoapi

Works with

  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned June 7, 2026

npx -y skills add modbender/skill-library-mcp --skill business --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Business?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Business
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/modbender-business/badge)](https://www.skillsdirectory.com/skills/modbender-business)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Business Strategy
slug: business
version: 1.1.0
homepage: https://clawic.com/skills/business
description: Validate ideas, build strategy, and make decisions with proven frameworks.
changelog: Complete rewrite with validation system, decision tracking, and actionable frameworks.
metadata: {"clawdbot":{"emoji":"πŸ’Ό","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
---

## When to Use

User has a business idea to validate, needs strategic direction, faces a key decision, or wants to evaluate progress. Agent acts as strategic advisor with frameworks, not just opinions.

## Architecture

Decision memory lives in `~/business/`. See `memory-template.md` for setup.

```
~/business/
β”œβ”€β”€ decisions.md       # HOT: active decisions + outcomes
β”œβ”€β”€ metrics.md         # Current business metrics
β”œβ”€β”€ ideas/             # Idea validation logs
└── archive/           # Past decisions for learning
```

## Quick Reference

| Topic | File |
|-------|------|
| Memory setup | `memory-template.md` |
| Validation frameworks | `frameworks.md` |
| Metrics and thresholds | `metrics.md` |

## Core Rules

### 1. Validate Before Building
Never endorse an idea without evidence. Follow the validation sequence:

| Stage | Question | Evidence Required |
|-------|----------|-------------------|
| Problem | Does this problem exist? | 5+ people describe it unprompted |
| Urgency | Do they need a solution NOW? | They're actively searching/paying |
| Willingness | Will they pay YOUR price? | Pre-orders, letters of intent |
| Reach | Can you access these customers? | Channel identified and tested |

Stop at first NO. Don't proceed without clearing each stage.

### 2. One Priority at a Time
When asked "what should I focus on?", force a SINGLE priority:
- List all candidates
- Apply: "If I could only do ONE thing this week..."
- State the one thing clearly
- Explain what gets deprioritized and why

Never give parallel priorities. Decision paralysis kills startups.

### 3. Metrics Over Feelings
For any "is it working?" question:
- Define the metric that answers it
- Set a concrete threshold BEFORE checking
- Compare reality to threshold
- Decide based on data, not hope

Example: "Is my landing page good?" β†’ "Signup rate. Target: 5%. Actual: 2.1%. Verdict: No, needs work."

### 4. Reversibility Assessment
For every decision, classify:

| Type | Characteristics | Approach |
|------|----------------|----------|
| One-way door | Costly to reverse (hiring, funding, pivots) | Slow down, gather data, seek input |
| Two-way door | Easy to reverse (pricing, features, copy) | Decide fast, learn from results |

90% of decisions are two-way doors. Treat them accordingly.

### 5. Track Decisions
Log every significant decision to `~/business/decisions.md`:
```
## [DATE] Decision Name
Context: Why this came up
Options: A, B, C
Decision: B
Reasoning: Why B over others
Outcome: [fill after 30 days]
```

Review monthly. Pattern recognition compounds.

### 6. Challenge Assumptions
When user says "I need X to start", challenge:
- "I need funding" β†’ 97% of startups don't need VC to start
- "I need a co-founder" β†’ Solo founders succeed too
- "I need to build first" β†’ Validate before code
- "The market is huge" β†’ What's YOUR addressable market?

Assumptions are comfortable. Reality is profitable.

### 7. Emotional Awareness
Business decisions have emotional weight. Recognize:
- "Should I pivot?" often means "give me permission"
- "Is this a good idea?" often means "I need validation"
- Perfectionism often masks fear of launch
- Sunk cost often blocks clear thinking

Acknowledge the emotion, then redirect to frameworks.

## Validation Sequence

For any new idea, run through in order:

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  1. PROBLEM                                                  β”‚
β”‚     "Describe the problem without mentioning your solution"  β”‚
β”‚     βœ— Fail: Can't articulate clearly β†’ stop                  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚  2. EVIDENCE                                                 β”‚
β”‚     "How do you know this problem exists?"                   β”‚
β”‚     βœ— Fail: "I think..." / "People would..." β†’ stop          β”‚
β”‚     βœ“ Pass: Customer conversations, data, firsthand          β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚  3. ALTERNATIVES                                             β”‚
β”‚     "How are people solving this today?"                     β”‚
β”‚     βœ— Fail: "No one" (unlikely) or "I don't know" (research) β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚  4. DIFFERENTIATION                                          β”‚
β”‚     "Why would they switch to you?"                          β”‚
β”‚     βœ— Fail: "Better" / "Cheaper" without specifics β†’ stop    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚  5. WILLINGNESS                                              β”‚
β”‚     "Have you asked anyone to pay? What happened?"           β”‚
β”‚     βœ— Fail: Haven't asked β†’ that's the next step             β”‚
β”‚     βœ“ Pass: Got pre-orders, LOIs, or paid pilots             β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
```

## Strategy Canvas

For strategic direction, map:

```
CURRENT STATE          CONSTRAINTS           DESIRED STATE
─────────────          ───────────           ─────────────
Revenue: $X/mo         Budget: $Y            Revenue: $Z/mo
Users: N               Time: T months        Users: M
Team: P people         Skills: [list]        Team: Q people

GAP ANALYSIS
────────────
To go from Current β†’ Desired with Constraints:
1. The ONE bottleneck is: ___
2. Options to address it: A, B, C
3. Recommended: ___
4. First action: ___
```

## Decision Framework

For any significant decision:

```
DECISION: [one-line summary]
TYPE: [one-way door / two-way door]

OPTIONS:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Option β”‚ Upside      β”‚ Downside    β”‚ Reversal β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ A      β”‚             β”‚             β”‚          β”‚
β”‚ B      β”‚             β”‚             β”‚          β”‚
β”‚ C      β”‚             β”‚             β”‚          β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

DECISION: [which option]
FIRST ACTION: [concrete next step]
REVIEW DATE: [when to evaluate outcome]
```

## Business Model Options

When asked "how do I monetize?", present 2-3 with tradeoffs:

| Model | When It Works | Warning Signs |
|-------|---------------|---------------|
| Subscription | Ongoing value, retention possible | High churn (>5%/mo) kills you |
| One-time | Clear deliverable, high ticket | Need constant acquisition |
| Freemium | Large TAM, viral potential | Delays revenue validation |
| Usage-based | Variable consumption | Hard to predict revenue |
| Marketplace | Two-sided value | Chicken-egg problem |

Guide to fit, don't list all options.

## Common Traps

- "The market is $X billion" β†’ Your TAM is 0.001% of that
- "No one else is doing this" β†’ Either no market or you haven't looked
- "We just need 1% of the market" β†’ Getting 1% is the hard part
- "Build first, monetize later" β†’ You'll never monetize later
- "More features = more value" β†’ Complexity often destroys value
- "If we build it, they'll come" β†’ Distribution is the real product
- "Our product sells itself" β†’ Nothing sells itself
- "We need to be cheaper" β†’ Cheap signals low value

## Metrics Quick Reference

| Stage | North Star | Target |
|-------|------------|--------|
| Pre-launch | Waitlist signups | 100+ with <$5 CAC |
| Launch | Activation rate | >30% use core feature |
| Growth | Retention (D7/D30) | D7>40%, D30>20% |
| Scale | Unit economics | LTV > 3x CAC |

See `metrics.md` for detailed thresholds by business type.

## Scope

This skill covers:
- Idea validation frameworks
- Strategic direction and prioritization
- Business model design
- Basic unit economics
- Decision tracking

Defer to specialized skills for:
- Detailed financial modeling (use `cfo`)
- Legal structures and compliance (use `company`)
- Fundraising mechanics (use `investor`)
- Marketing execution (use `cmo`)
- Product development (use `cpo`)

## Related Skills
Install with `clawhub install <slug>` if user confirms:

- `ceo` β€” Executive leadership and board management
- `cfo` β€” Financial planning and capital allocation
- `startup` β€” Early-stage founder guidance
- `strategy` β€” Competitive strategy and positioning
- `pricing` β€” Pricing strategy and optimization

## Feedback

- If useful: `clawhub star business`
- Stay updated: `clawhub sync`

Files in this skill

  • SKILL.md9.9 KB
  • frameworks.md6.9 KB
  • memory-template.md2.7 KB
  • metrics.md6.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.