Skill · v1.0

Daily Admin Orchestrator

Daily Admin Orchestrator is the delegation surface for the Solopreneur Admin Toolkit. It replaces the question "which skill do I start?" with a single ritual that runs all four admin primitives in sequence. Three variants: morning briefing (5-10 min), end-of-day rolldown (5 min), Friday weekly review (45-60 min). Nothing lives only in the practitioner's head after this runs.

Install

Claude Code (CLI / WSL / Git Bash)

/plugin marketplace add https://www.infinitegameos.io/marketplace.json
/plugin install daily-admin-orchestrator@igos-library

Claude Code (VS Code)

Install in VS Code

Opens the Claude Code plugins dialog with the marketplace and skill prefilled. Requires the Claude Code VS Code extension installed and signed in. Or paste the snippet below into .claude/settings.json for VS Code, JetBrains or any setup that prefers manual config.

{
  "extraKnownMarketplaces": {
    "igos-library": {
      "source": {
        "source": "url",
        "url": "https://www.infinitegameos.io/marketplace.json"
      }
    }
  },
  "enabledPlugins": {
    "daily-admin-orchestrator@igos-library": true
  }
}

Direct markdown URL (Claude Code, Cursor, Codex CLI)

https://www.infinitegameos.io/markdown/skills/daily-admin-orchestrator

Cursor (.mdc rules file)

curl -O https://www.infinitegameos.io/install/cursor/daily-admin-orchestrator.mdc

Aider, Cline, any agent with --read

curl -O https://www.infinitegameos.io/markdown/skills/daily-admin-orchestrator
aider --read daily-admin-orchestrator.md

Definition

Daily Admin Orchestrator runs Email Triage, Customer Follow-Up, Invoice and Payment Tracker and Quote Builder in sequence, reads each skill's handoff payload and routes action items between skills. Three variants calibrate depth per session: morning briefing skims each primitive for today's priorities in 5-10 minutes; end-of-day rolldown issues invoices for completed jobs and queues tomorrow's touchpoints in under 5 minutes; Friday weekly review runs every primitive to the bottom of its queue in 45-60 minutes. The Orchestrator holds no data of its own. It reads what the four primitives produce and sequences the reads. The load-bearing benefit is one thing: the practitioner does not decide where to start.

The four-step sequence

Step 2 runs Email Triage at the depth appropriate for the variant. Morning briefing: sort and surface today's action items, flag anything time-sensitive, skip drafts unless requested. End-of-day: triage new messages since morning and close the inbox for the day. Friday weekly: full bucket review including WAITING and READ LATER sweeps. The triage handoff payload routes to the three downstream steps.

Step 3 checks the Customer Follow-Up cadence queue against today's date. Any customer with a next_followup_date on or before today surfaces with their touchpoint type. Action items from the triage step merge here to prevent duplicate outreach on the same customer in the same session. Step 4 runs the Invoice and Payment Tracker sweep: overdue invoices, same-session invoicing for jobs that closed since the last run. Step 5 checks the open quote log for unsigned quotes past the 48-72h follow-up window.

Daily briefing summary and the three-action list

Step 6 consolidates outputs from Steps 2-5 into a single briefing document: email action items, customer touchpoints due today, invoice status and outstanding quotes. At the bottom: today's three actions, ranked by revenue or relationship urgency. The practitioner looks at the list for 45 seconds and knows exactly what to do before leaving the driveway.

The Orchestrator is a sequencer, not a cage. Practitioners who know their email is clear and their invoices are current can invoke any primitive directly without running the full briefing. The Orchestrator's value is the sequence. The briefing is orientation, not resolution. If the practitioner finishes the briefing and feels productive without having acted on any of the three priority items, the ritual has inverted. The three actions at the bottom are the work.

Use Cases

Monday morning briefing for a tree trimmer with four jobs scheduled

Joel runs the morning briefing at 7:15 AM before the first site. Three emails overnight. Two customer touchpoints due. One overdue invoice needs a phone call. One unsigned quote hit its 72h window. The briefing summary lands in under ten minutes. Three actions at the bottom. He looks at the list for 45 seconds, makes two calls on the way to the first job and sends one message at lunch.

End-of-day rolldown as the primary invoice ritual

A handyman sets end-of-day rolldown as his primary variant because invoicing avoidance is his real bottleneck, not email overload. The end-of-day variant puts Invoice and Payment Tracker as the primary ritual step. Every job that closed today gets an invoice before he puts the truck in the garage. No batch, no delay.

Friday weekly review as the business health snapshot

A freelance designer runs the Friday weekly review at 6:30 AM before her first meeting. Full triage sweep, full cadence audit, aged receivables analysis, open quote status decisions. The output saves to admin/weekly-reviews/YYYY-MM-DD-friday.md. She pulls it up Sunday night to orient Monday morning. She skips the step where she stares at the whiteboard trying to remember what was open.

Consolidated outreach for a customer who appears in both cadence queue and email triage

Sandra is due for a 90-day maintenance check-in and also sent an email this morning. The Orchestrator merges both in Step 3: one outreach message covers the maintenance check-in and replies to the email. Not two separate messages. The Orchestrator prevents duplicate outreach on the same customer in the same session.

Sequence override for a solopreneur whose bottleneck is cash flow

A plumber whose real problem is delayed invoicing moves Invoice and Payment Tracker to position 2 in the sequence, directly after Email Triage. The Orchestrator's default order (Triage, Follow-Up, Invoice, Quote) is a dial, not a rule. Tune the sequence to your actual bottleneck after the first week of reps.

FAQ

Do I need all four primitive skills installed to use this?

Yes. The Orchestrator is a sequencer; it delegates to the four primitives rather than re-implementing their logic. All four (Email Triage, Customer Follow-Up, Invoice and Payment Tracker, Quote Builder) need to be loaded in your session. The Orchestrator reads their handoff payloads and routes between them.

What if I only have one thing to deal with today?

Run the relevant primitive directly. The Orchestrator's value is the sequence for days when everything is in motion. A practitioner who knows their email is clear and their invoices are current can invoke Quote Builder or Customer Follow-Up directly without running the full briefing. The Orchestrator is not required for every session.

How long does each variant actually take?

Morning briefing: 5-10 minutes. Each primitive runs at shallow depth; the output is a prioritized list, not a full deep dive. End-of-day rolldown: under 5 minutes; the focus is invoice issuance for today's jobs and tomorrow's queue. Friday weekly: 45-60 minutes when the business has meaningful volume across all four primitives.

Can I change the order of the four steps?

Yes. The default order (Triage, Follow-Up, Invoice, Quote) reflects a specific bottleneck theory: clear inbound before running proactive outreach. If invoicing avoidance is your real problem, move Invoice to position 2. The primitives are independent. The sequence is a dial you tune after your first week of reps.

What does the Friday weekly review produce?

A complete business health snapshot saved to your admin folder: email backlog cleared, full cadence audit across all active customers, aged receivables analysis (0-30d, 31-60d, 60d+), open quote status decisions. Pull it up Sunday night to orient Monday morning. The document is the weekly snapshot of everything open in the business.

Related

Daily Admin Orchestrator is the entry point for the Solopreneur Admin Toolkit. The four primitives it sequences are Email Triage, Quote Builder, Invoice and Payment Tracker and Customer Follow-Up. The design frame for a service business that runs on systems rather than the practitioner's working memory is the Sovereign Life Playbook.

See the Sovereign Life Playbook