A Claude skill that reads your goals, your pipeline, and your network, then designs the audacious swings most people never take. You review. You approve. You swing.
Home Run Time turns your biggest opportunities into a managed portfolio. Claude reads your context and produces three audacious swings, each scored, each with a next move, each with a kill or push date. Copy the two blocks below and your Claude runs the whole system for you.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, my goals, my pipeline, my network, and where I track my work. Confirm when it is installed and tell me 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.
Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.
Every week you see what's working, build it live with Claude, and put it to work in your business.
Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.
You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.
Big swings die in the space between "someday" and your calendar. Home Run Time closes that space with a system: every swing gets scored, every swing gets a lane, and every swing gets a date where you decide. The audacity is designed in, and the follow-through is automatic.
The size of the game matches the size of the player. The skill starts by asking what a home run looks like at your level, then holds you to it.
Revenue, Reach, Relationship. Every swing lives in one lane, and the system shows you at a glance which lane you keep avoiding.
Seven to ten only. If it could happen as a normal outcome of doing the work, it is a task. The skill pushes back when you try to file a task as a home run.
Every active swing gets a Kill or Push date, 21 days by default. Revive it, pause it, or kill it with the lesson captured. Zero swings drift.
Fifteen minutes Monday, one two-hour window mid-week, ten minutes Friday. The portfolio stays alive on less than twenty percent of your week.
A Claude skill is a reusable set of instructions that teaches Claude how to run a specific system for you. Install it once and Claude remembers the whole workflow: the steps, the standards, and the output format. You trigger it with a simple phrase, like saying home run time to run this one.
Copy the two blocks on this page and paste them into Claude, install instruction first, skill block second. Claude builds the skill file, installs it, and personalizes it with what it knows about you. The whole process takes under a minute and works the same way for every skill in the library.
Home Run Time is a free Claude skill that designs and manages your Home Run Portfolio. Claude reads your goals, your pipeline, and your network, then produces three audacious swings, each scored on the Audacity Floor with a kill or push date and a concrete next move. You review, approve, and swing.
Every week you see what's working, build it live with Claude, and put it to work in your business.