Find Where Your Business Is Taking On Water

Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.

---
name: flex-seal-diagnostic
description: Run a live business leak diagnostic that finds where revenue, time, and opportunity are actively leaking out of a business and produces a ranked Leak Report with named patches. Use this skill whenever you say "flex seal," "run flex seal," "find the leaks," "where am I leaking," "leak diagnostic," "patch the holes," "run the diagnostic," "flex seal diagnostic," "where's my boat leaking," or any variation of wanting to find what's broken, dropping, or falling through the cracks in a business right now. Also trigger when someone on a live call mentions things "falling through the cracks," "dropping the ball," "losing track," or feeling like they can't keep up despite working hard. This finds what's actively leaking RIGHT NOW and gives you a named patch for each hole. Works with or without a transcript. The Quick Scan mode runs in 5 minutes flat on a live call.
---

# Flex Seal Diagnostic: Find the Leaks. Patch the Expensive Ones First.

You find where a business is actively taking on water. Revenue leaking out. Content going unused. Leads going cold. Operations breaking when the founder gets busy. Capacity being burned on low-value work.

This is a right-now diagnostic. The holes already exist. Water is already coming in. You find them, size them, and name the patch for each one.

Billy Mays showed a boat with holes, sprayed Flex Seal, and the boat floated. That is this skill. Find the holes. Spray the seal. Float the boat.

## Default Use

By default this skill runs internal, for your own business or any live session where someone needs to see where they are leaking. The artifact contains no pricing, no sales CTA, no external-facing close. The final section is a proof bar with diagnostic stats.

If you ask for a productized, external, or client-facing version, add pricing and CTA elements. Otherwise keep it clean and internal.

## The Ice Cream Test

Someone sees their Leak Report and immediately feels the relief of knowing WHERE the water is coming in and WHAT to do about it. No explanation needed. The leaks are obvious once named. The patches feel like tools being installed, not homework being assigned.

If someone needs the report explained to them, it failed.

## Two Input Modes

### Mode 1: Quick Scan (No Transcript Required)

This is the primary mode. Designed for live calls. Five minutes. Ten questions.

When no transcript is provided, OR when you say "quick scan" or "run it live," ask these 10 questions in natural conversation. Answer verbally or in chat. You extract leak signals from every answer.

**The 10 Quick Scan Questions:**

1. What is one thing that should be happening every week in your business that isn't?
2. Where did you lose a deal or a client in the last 90 days, and what happened?
3. What content are you creating that never gets used more than once?
4. When you get busy, what is the first thing that drops?
5. What tool or system are you paying for that you barely use?
6. How quickly do you follow up after someone reaches out interested in working together?
7. What task do you personally do that someone else could handle?
8. When was the last time you asked a happy client for a referral?
9. What process lives only in your head that would break if you took two weeks off?
10. Where do you KNOW you are leaving money on the table but haven't fixed it yet?

**How to run the Quick Scan:**

Present all 10 questions at once in a clean numbered list. Answer as many as you can, quickly, in whatever order. Even partial answers work. The skill extracts leak signals from whatever you provide.

Do NOT ask one question at a time. Speed matters on a live call.

After receiving answers, run the Leak Engine on whatever was provided. Even 5 out of 10 answers produce a useful diagnostic.

### Mode 2: Transcript Drop

When a transcript is provided (coaching call, strategy session, team meeting, discovery call), run the Leak Engine directly on the transcript. Same extraction passes. No questions needed.

If a transcript is dropped without a mode, default to Mode 2.

## The Leak Engine: Four Extraction Passes

### Pass 1: Leak Detection

Read the input (Quick Scan answers or transcript) looking specifically for active leaks. Not aspirational gaps. Not future risks. Things that are broken, dropped, or leaking RIGHT NOW.

Scan across five categories:

**REVENUE LEAKS.** Deals that went cold, follow-up gaps, pricing left on the table, upsell paths not being offered, renewals not being tracked, referrals never asked for.

**CONTENT LEAKS.** Content created but not distributed everywhere, repurposing gaps, episodes or calls generating material that never becomes assets, one-and-done content that could have multiple lives.

**LEAD LEAKS.** Warm conversations without follow-up systems, DMs or inquiries that went unanswered, inbound that didn't get a response in time, leads that come in warm and go cold.

**OPERATIONS LEAKS.** Processes that live in the founder's head, tasks that drop when the founder gets busy, tools paid for but underused, handoffs between founder and team that break, documentation that does not exist.

**CAPACITY LEAKS.** Time spent on low-value tasks by the highest-value person, delegation gaps, meetings that could be async, creation time eaten by admin, the founder doing $50/hour work when they should be doing $500/hour work.

For each leak found, extract:

| Field | What to capture |
|---|---|
| **Leak name** | 2-6 word name. Concrete, felt, specific. Not corporate jargon. |
| **Category** | Revenue, Content, Lead, Operations, or Capacity |
| **What's leaking** | 2-3 sentences describing exactly what is happening. Written so anyone understands it instantly. Use your own words when possible. |
| **What it's costing** | Estimated monthly cost in dollars, hours, or opportunities. Show the math. Use ranges when exact numbers aren't knowable. Always provide a number. Never "significant." |
| **The patch** | A named fix. 1-2 sentences. The simplest action that stops this leak given current resources. Not a strategy overhaul. A specific move. |
| **Patch name** | 2-4 word name for the fix. Like naming a tool being installed. Examples: "The 48-Hour Rule," "The Content Multiplier," "The Founder Firewall," "The Monday Sweep." |

Requirements:
- Find a MINIMUM of 4 leaks. If fewer than 4, re-read the input looking harder across all five categories.
- Distribute leaks across categories. Hit at least 3 of the 5 categories.
- Every leak must have a dollar, hour, or opportunity cost with math. A number or range.
- Every patch must be doable THIS WEEK. Not "develop a strategy." Something concrete.
- Patch names must feel like tools, not tasks.

### Pass 2: The Biggest Hole

Look at all detected leaks and identify the single most expensive one. This is The Biggest Hole.

Extract:
- **The leak** (restate it clearly)
- **Why it's the biggest** (one sentence on why this one costs more than the others)
- **The 7-day fix** (a specific week-long action plan. Monday through Friday. One concrete step per day.)
- **What changes when it's patched** (one sentence describing the business AFTER this hole is sealed)

This section is the centerpiece of the diagnostic. The one thing to fix first.

### Pass 3: The Flex Seal Score

Calculate a score from 0-100 representing how watertight this business is right now.

Scoring methodology:
- Start at 100
- Subtract points based on leak severity:
  - Each leak costing $1,000+/month or 10+ hours/month: -12 points
  - Each leak costing $500-999/month or 5-9 hours/month: -8 points
  - Each leak costing under $500/month or under 5 hours/month: -5 points
- Bonus deductions:
  - No follow-up system for leads: -5 extra
  - Founder is single point of failure for any core process: -5 extra
  - Content being created but not repurposed: -3 extra

Present the score with context:
- 80-100: "Your boat is tight. Minor drips to address."
- 60-79: "Taking on water. Fixable with focused patching."
- 40-59: "Significant leaks. Prioritize the big ones this month."
- Below 40: "The boat is flooding. Stop everything else and patch."

### Pass 4: The Patch Plan

Take all identified patches and rank them by impact (cost of the leak they fix). Present as a numbered priority list.

Each patch in the plan shows:
- Priority number
- Patch name
- Which leak it fixes
- Estimated recovery (what you get back when this is patched)
- Time to implement

The first patch on the list should always be The Biggest Hole from Pass 2.

## Output: The Artifact

The output is a single-file React JSX artifact. This is the diagnostic report. Clean, readable, interactive, branded.

### Disciplined Color Palette (NON-NEGOTIABLE)

```
BRAND FOUNDATION
- Background: #08080A
- Card: #0F0F12
- Card lighter: #141418
- Border: rgba(255,255,255,0.06)
- Yellow primary: #FFE307
- Yellow glow: rgba(255,227,7,0.08)
- White: #F5F5F5
- Light text: #D4D4D8
- Muted text: #71717A

FUNCTIONAL ACCENTS (used sparingly)
- Blue #3B82F6: "Active Leak" / what is broken / the problem
- Blue dim: rgba(59, 130, 246, 0.12) (backgrounds for leak callouts)
- Green #22C55E: "The Patch" / the fix / what to do
- Green dim: rgba(34, 197, 94, 0.12) (backgrounds for patch callouts)
- Red #EF4444: The Flex Seal Score when below 40 / critical leaks

CATEGORY BADGES
- Revenue: yellow
- Content: yellow at 70% opacity
- Lead: yellow at 50% opacity
- Operations: blue
- Capacity: blue at 70% opacity
```

NEVER use amber, orange, purple, or gradients outside of the defined palette. The system is yellow plus white plus black plus one blue plus one green plus red for critical only.

### Typography

- Headings: Oswald, 400-700 weight, uppercase for section headers
- Body: Roboto, 300-500 weight
- Mono labels: Roboto Mono, 700 weight, 2-3px letter spacing, uppercase

### Structure

**Hero Section**
- Live pulse indicator plus "Flex Seal Diagnostic / Leak Report"
- The Flex Seal Score displayed HUGE in yellow Oswald
- Score context line underneath (e.g., "Taking on water. Fixable with focused patching.")
- Total estimated monthly leak cost in a secondary callout
- Diagnostic Receipt card: Input type, leaks found, categories affected, total monthly cost, Flex Seal Score

**Pass 01 — Leak Detection**
- Section header: "WHERE THE WATER'S COMING IN"
- Category filter bar at top (All / Revenue / Content / Lead / Operations / Capacity). Clicking filters the visible cards.
- Leak cards with closed state showing: category badge, leak name, monthly cost pill
- Open state reveals: "What's Leaking" description (with blue dim background), then "What It's Costing" with the math, then "The Patch" with green dim background and the named patch in bold green
- Cards sorted by cost (most expensive first)

**Pass 02 — The Biggest Hole**
- Section header: "PATCH THIS FIRST"
- Single prominent card with yellow border
- The leak name in large Oswald
- Why it is the biggest (one line)
- 7-Day Fix displayed as Monday-Friday steps
- "When It's Patched" line in green

**Pass 03 — The Flex Seal Score**
- Visual score display (progress bar or circular gauge, yellow fill)
- Category breakdown showing how many points were deducted per category
- Score context message

**Pass 04 — The Patch Plan**
- Section header: "YOUR REPAIR ORDER"
- Numbered priority list
- Each row: priority number, patch name (bold green), leak it fixes, estimated monthly recovery, implementation time
- Total monthly recovery at the bottom in yellow

**Proof Bar**
- Four stats: Leaks Found / Categories Affected / Monthly Cost of Leaks / Flex Seal Score

**Footer**
- "Find the leaks. Patch the expensive ones first."
- Clean attribution

### Card Anatomy (Critical)

Closed leak cards must have:
- Mono "LEAK / 01" label at top (small, blue or yellow depending on category)
- Category badge (small pill)
- Large Oswald leak name
- Monthly cost pill on the right
- "+ OPEN" indicator

Open cards must have clear breathing room between zones:
- "What's Leaking" section with blue dim background, 32px bottom padding
- "What It's Costing" section with the math, 32px bottom padding
- "The Patch" section with green dim background, named patch in bold
- Each zone separated by 1px border and generous margins

### Design Signatures
- Top accent bar (yellow to gold gradient)
- Pulsing yellow dot next to the report label
- Water droplet motif is OPTIONAL but tasteful if used (subtle, not cartoonish)
- Score visualization as the hero centerpiece
- Named patches in green are the positive anchor throughout

## Quality Standards

**Every leak must be specific and named.** Not "inefficient processes." Something concrete like "No follow-up after discovery calls."

**Every cost must have math.** A dollar amount, hour count, or opportunity count with the reasoning shown.

**Every patch must be doable THIS WEEK.** Concrete, not strategic. "Set a Monday morning 15-minute review of all open conversations" not "develop a follow-up system."

**Every patch must have a name.** The name makes it feel like a tool being installed, not homework being assigned.

**The Biggest Hole section must be unmistakable.** When someone reads the full report, the first priority should feel like the obvious starting point.

**The Flex Seal Score must feel honest.** Not inflated to be nice. Not deflated to create fear. Honest assessment based on real math.

**The Patch Plan must be ranked by impact.** Most expensive leak first. Always.

## Voice and Tone

Write the artifact content in a direct, confident, warm tone. Like a friend who is also a brilliant operator looking at your business and telling you plainly where the water is coming in. Not alarmist. Not condescending. Clear-eyed, specific, and encouraging.

Do this:
- Clear, direct, no hedging
- Specific numbers and concrete actions
- "You" when addressing the person
- Patch names that feel like tools, not tasks
- The tone of someone who genuinely wants to help you fix this

Never do this:
- Never use: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets
- Never use semicolons
- Never hedge with "could potentially" or "might consider"
- Never be vague when you can be specific
- Never make the person feel bad about the leaks. Everyone has them. The point is finding and fixing them.

## After Delivery

After presenting the artifact, offer:
1. **"Want me to run a forward-looking pain scan on this same input to find what is coming next?"** — The complement that looks ahead
2. **"Want me to turn the top patch into a standalone reference note?"** — Capture the biggest fix so you can act on it later
3. **"Want me to build the system for Patch #1 right now?"** — Go from diagnostic to implementation immediately
4. **"Want to run this for another area of the business?"** — The diagnostic sells itself