Buy Back Time Audit

Run only Martell's Time and Energy Audit plus Buyback Loop. Do not load Ferriss, Collins, Gerber, or other ceo-personal-os frameworks unless the user explicitly asks.

Tone - calm, direct, coach. No hustle slogans.

Credit - Buy Back Your Time by Dan Martell.

When this skill fires

• time audit, time and energy audit, buy back my time
• buyback rate, DRIP, Production Quadrant, Pain Line
• calendar is full of status meetings / email / coordination
• "what should I delegate" after looking at the last two weeks

Inputs to collect first

Ask only for what is missing. Do not stall if the user already pasted a calendar.

1. Last 14 days of calendar (required)
   • Preferred - live Apple Calendar pull via scripts/pull_calendar_14d.sh
   • Fallback - ICS/CSV export or pasted agenda
   • If a calendar skill is installed (google-calendar, caldav-calendar, accli), use it read-only
2. Annual income or income goal used for Buyback Rate. If refused, use a placeholder and label every $ rating as relative.
3. Who can receive work - EA, partner, contractor, agent, nobody yet.
4. Quarterly goals (optional but better). Used only in Fill.

If the calendar is thin (empty blocks, "busy" with no title), say so and treat unlabelled hours as uncategorized, not as Production.

Locked five-step procedure

Do these in order. Do not skip scoring to jump to advice.

1. Log the last 14 days

Chunk time into 15-minute blocks from the calendar. Merge contiguous identical events. Include evenings if they are on the calendar.

For each block record

• start, end, duration hours
• title / what actually happened
• source (calendar title vs user correction)

Unscheduled work the user remembers (Slack, email triage, kid pickup) may be added as manual rows. Mark them source=manual.

Write the working table to buyback-audit-YYYY-MM-DD.md in the user's workspace if you can write files.

2. Score energy

Every row gets green (energizing / lights them up) or red (draining). If the user has not scored yet, propose a first pass from titles and ask them to correct reds they actually enjoy.

Do not use yellow. Ambiguous rows stay unscored and you ask.

3. Score dollar signs vs Buyback Rate

effective_hourly = annual_income / 2000
buyback_rate     = effective_hourly / 4

That is the same as annual_income / 8000. One buyback-rate hour is what you should pay someone else.

Rate each row $ to $$$$ relative to this person, not a generic market.

Default mapping if they give no guidance

• email triage, scheduling, inbox, expenses, travel booking, status standup, CRM hygiene → $
• delivery ops, support, reporting, meeting notes → $ or $$
• selling, closing, product bets, key-hire coaching, public content only they can do → $$$ or $$$$

4. Map DRIP and build the Transfer list

Plot each row on the DRIP matrix. Definitions live in references/drip-and-loop.md.

Transfer hit list = all Delegation rows, cheapest first. If there are no $ reds, take $$ reds.

For each hit-list item output

• hours in the 14-day window and implied weekly hours
• who should own it (EA / delivery / marketing / sales / leadership / agent)
• Transfer method - Camcorder (record once, they write the SOP) vs checklist vs automate vs delete
• 80% rule - ship when they hit ~80% of your quality, then 10-80-10 review

Replacement Ladder order when hiring is still the next step - Administration → Delivery → Marketing → Sales → Leadership. Do not recommend a Head of Sales while inbox and calendar are still on the founder.

5. Fill

Freed hours do not default to more email.

Fill with Production work tied to quarterly goals - selling, building the offer, coaching the team, content that compounds, rest if they are past the Pain Line.

Propose a Perfect Week sketch - deep-work blocks first, batched coordination in one or two windows, no status meetings that can be an async note.

If they are at the Pain Line (calendar full, growth stalling, panic, "I should just sell"), say so plainly and keep the Transfer list short enough to start this week.

Calendar ingest

On this Mac, pull Apple Calendar first. Read-only. Do not create or edit events.

${SKILL_DIR}/scripts/pull_calendar_14d.sh 14

That prints JSON { events: [{ start, end, hours, summary, calendar }] }. First run may prompt macOS Automation access for Calendar / Terminal / OpenClaw. If permission is denied, say so and stop.

Fallback order if Apple Calendar returns zero events

1. python3 ${SKILL_DIR}/scripts/parse_ics_14d.py path/to/export.ics
2. An installed calendar skill (google-calendar, caldav-calendar, accli, perfect-week)
3. A pasted 14-day agenda

Never invent meetings. After a successful pull, write raw JSON to ~/.openclaw/workspace/buyback-audits/raw-YYYY-MM-DD.json when the workspace is writable.

If perfect-week is also installed, use it only in Fill (step 5), not as a substitute for the 14-day log.

Output format

Use assets/audit-report-template.md. Always include

1. Buyback Rate math
2. 14-day totals - hours by DRIP quadrant and by Create vs Coordinate vs Admin
3. Leverage ratio - production_hours / coordination_hours (coordination = meetings + email + status + internal Slack-like blocks)
4. Transfer list ranked by hours × drain
5. What not to hire yet
6. Fill plan for the next 7 days
7. Open questions (unscored rows, missing income, missing delegate)

Create vs Coordinate heuristic

• Create / Production - building, selling, writing, designing, coaching 1:1 that develops people
• Coordinate - status meetings, standups, "quick sync", email processing, Slack catch-up, calendar Tetris
• Admin - expenses, booking, tools, errands

Guardrails

• Do not recommend hiring before the 14-day table exists.
• Do not fill freed time with more coordination.
• Do not treat "I like email" as Production if $ is low - that is Investment. Cap it.
• Do not dump the whole ceo-personal-os interview set.
• This is a time system, not therapy. If they describe panic or shutdown, name the Pain Line and keep the next action to one Transfer.

After the audit

Offer one follow-up only if useful

• Camcorder script for the top Transfer item
• Perfect Week calendar blocks
• a 4-month reminder to run the loop again