CHRISTINE Take Swings Big Enough to Change the Business
Home Run Time reads your goals, your pipeline, your offers, and your network, then designs your boldest swings for you — one Revenue, one Reach, one Relationship — each scored on the Audacity Floor, with a kill-or-push date and a next move you can take this week.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
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: home-run-time description: Design and manage my Home Run Portfolio. Read my context, goals, pipeline, offers, and network, then produce audacious swings with Audacity scoring, strategic reasoning, and concrete next moves. Trigger when I say "run home run time," "home run time," "home run portfolio," "pick my swings," "score my home runs," "kill or push," "what's in my portfolio," "add a home run," or "update my swings." Also trigger when reviewing active swings or running the weekly cadence. --- # Home Run Time ## What This Skill Does Designs and manages my Home Run Portfolio. You read my context, my goals, my pipeline, my offers, and my network, then produce the swings with Audacity scoring, strategic reasoning, and concrete next moves. I review, adjust, approve. Then it gets logged. ## When I Trigger It I say "run home run time" or "home run time" when I want to: - **Seed my portfolio for the first time.** Generate three home runs based on my context. One Revenue, one Reach, one Relationship. Each scored on the Audacity Floor with a Kill or Push date and a next move I can take this week. - **Run my weekly cadence.** Monday: review what is alive. Mid-week: work my active swings with everything prepped. Friday: Kill, Pause, or Push every active swing. Log the lesson. - **Add or update a swing.** A new opportunity showed up that qualifies. An active swing needs a new angle. A swing needs to be killed with a lesson captured. ## What Comes Out - **Three home runs** generated from my context with Lane, Audacity Score, Upside, Why This One, Kill or Push Date, and Next Move - **Weekly reviews** that update Last Touch dates, surface stale swings, and force the Kill or Push decision - **Killed swings** that generate a short field note with the outcome and the lesson ## The Rules 1. **The Audacity Floor is non-negotiable.** Seven to ten only. If it could happen as a normal outcome of doing the work, it is a task. Push back on me if I try to file a task as a home run. 2. **Three lanes, always.** Revenue, Reach, Relationship. Surface which lane is underweighted. Most operators cap out at two of three. 3. **No swing drifts.** Every active swing has a Kill or Push date. 21 days default. By that date: Revive, Pause, or Kill. 4. **Killed swings are lessons.** Every kill generates a short field note. The lesson compounds even when the swing did not. 5. **You do the work.** Read my operating context, my goals, my pipeline, my offers, and my network. Produce the swings. I review, adjust, and approve. 6. **Present before logging.** Always show the swings back to me for confirmation before writing anything to my tracker. ## The Architecture ### The Audacity Floor Every home run gets scored on a scale of seven to ten. Seven is a stretch. Eight is bold. Nine is audacious. Ten is the Misogi tier (Jesse Itzler's language for the biggest swing of the year). There is no six. There is no five. If it could happen as a normal outcome of doing the work, it is a task, and the system refuses to file it as anything else. ### The Three Lanes A home run can only live in one of three lanes. Every active swing gets one lane. The system shows me at a glance which lane is underweighted. - 💰 **Revenue** - The partnerships, the months, the checks that move the business to a level it has never been at before - 📡 **Reach** - The content that travels, the stages that change who knows I exist, the moments that shift discoverability - 🤝 **Relationship** - The specific person whose orbit changes my trajectory, the rooms two levels above where I currently operate, the spiderweb of connections that opens doors ### The Forcing Function Most home runs die. That is the job. I am running a portfolio, and every active swing has a Kill or Push date. By that date, one of three things happens. - **Revive** with a new angle. The swing is still alive. The path needs to change. - **Pause** with a re-engage trigger. The timing is wrong. Document what brings it back. - **Kill** with a field note. Capture what was learned. The lesson compounds even when the swing did not. ### The Weekly Cadence Twenty percent of the week. One dedicated block for home runs. - **Monday, 15 minutes** - Scan the portfolio. Flag what is alive. - **Home Run Window, 2 hours** - Work the active swings with everything prepped. Pure execution. - **Friday, 10 minutes** - Kill, pause, or push. Update the portfolio. Log one lesson. ### Five Layers Stack 1. **Identity** - The size of the game matches the size of the player 2. **Lanes** - Revenue, Reach, Relationship 3. **Audacity Floor** - Seven to ten, no exceptions 4. **Forcing Function** - Kill or Push every 21 days 5. **Cadence** - The weekly rhythm that keeps the portfolio alive ## Routing - New and updated swings route to my Home Run Portfolio tracker (Notion, a doc, a spreadsheet, wherever I track my work; ask me once and remember it) - Killed swings generate a short field note logged alongside the portfolio ## The Principle Worth Preserving Home runs are what the system is designed to produce. The architecture of audacity comes first. Design the game. Then play it.
From then on, just say "Run home run time."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingA portfolio of home runs, not a wish list.
Seed it once and you get three swings built from your real context. Every home run in the portfolio carries the same parts — and the system keeps them honest week after week:
1 · Lane
Revenue, Reach, or Relationship. Every swing lives in exactly one lane — and the system shows you at a glance which lane is underweighted.
2 · Audacity Score
Seven to ten only. Seven is a stretch, eight is bold, nine is audacious, ten is the biggest swing of the year. There is no six.
3 · Upside
What the swing means if it lands — the level the business has never been at before.
4 · Why This One
The strategic reasoning: why this swing, from your context, right now.
5 · Kill or Push Date
Every swing gets one — 21 days by default. By that date it gets revived with a new angle, paused with a re-engage trigger, or killed.
6 · Next Move
A concrete step you can take this week. A swing without a next move is just a daydream.
7 · Weekly Reviews — and Field Notes for Killed Swings
Monday, 15 minutes: scan what's alive. A two-hour window mid-week: work the active swings with everything prepped. Friday, 10 minutes: kill, pause, or push — and every killed swing generates a short field note with the outcome and the lesson.
And it will tell you when a swing is really a task
The Audacity Floor is non-negotiable. If something could happen as a normal outcome of doing the work, it's a task — and the skill pushes back rather than file it as a home run. Nothing drifts, either: every swing carries a kill-or-push date, and nothing gets logged to your tracker until you've reviewed and approved it. Most home runs die. That's the job — you're running a portfolio.
Keep stacking: pairs beautifully with Growth Engine Designer
Home Run Time manages the audacious swings that could change everything — Growth Engine Designer builds the revenue architecture underneath, turning a single-offer business into a connected portfolio of engines with targets and sensors.
Get Growth Engine Designer →Because audacity needs architecture.
Big swings don't survive on inspiration — they survive on structure. Home Run Time stacks the layers so the boldest part of your business gets managed as carefully as the reliable part.
The Audacity Floor filters out disguised tasks
Scoring every swing seven to ten forces the honest question: could this happen just by doing the work? If yes, it's a task. The floor keeps your portfolio reserved for outcomes that would genuinely change your trajectory.
Three lanes keep ambition balanced
Revenue, Reach, Relationship — most operators cap out at two of the three. Because every swing is tagged to one lane, the underweighted lane is visible at a glance instead of invisible for a year.
The kill-or-push date is the forcing function
Ideas don't die of failure nearly as often as they die of drift. A 21-day decision date means every swing gets revived, paused, or killed on purpose — never forgotten.
Killed swings still pay you
Every kill generates a field note with the outcome and the lesson. The lesson compounds even when the swing didn't — which is what makes this a portfolio instead of a gamble.
You stay the decision-maker
Claude reads your operating context, your goals, your pipeline, your offers, and your network, then produces the swings — but it always presents them to you before logging anything. You review, adjust, and approve. Then it goes in the tracker.