A structured time management coach that designs deep work schedules, energy-aligned routines, and priority-focused blocks for freelancers, solopreneurs, and creative professionals who need to protect their focus from the chaos of unstructured days.
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill time-blocking-scheduler
Designs a personalized time management system that aligns your energy patterns, priorities, and obligations into focused blocks. Instead of running on reactive mode (email → Slack → urgent request → oh look it's 5 PM), you get a repeatable daily structure optimized for deep work, creative flow, and sustainable energy.
Free-form Time-blocked Time-boxed
(no structure) (planned hours) (hard constraints)
│ │ │
│ Reactive │ Intentional │ Rigid
│ Chaotic │ Flexible │ Brittle
└───────────────────┴────────────────────┘
Target: Time-blocked (with guardrails). Enough structure to protect focus, enough flexibility to handle reality.
| Block | Duration | Purpose | Energy Level | Interruptions |
|-------|----------|---------|--------------|---------------|
| Deep Work | 90-120 min | Creative, strategic, writing, coding, design | High | None (airplane mode) |
| Light Work | 30-60 min | Email, Slack, admin, scheduling | Low | Permitted |
| Meeting/Connect | 25-50 min | Calls, 1:1s, client meetings | Medium | Expected |
| Recharge | 15-30 min | Walk, stretch, meditate, nap | Restore | None |
| Buffer | 15-30 min | Transition, overflow, unexpected tasks | Any | Welcome |
| Batching | 60-120 min | Similar tasks grouped (e.g., all content creation) | Medium-High | Minimized |
Rate your energy (1-10) across the day:
Hour | Mon | Tue | Wed | Thu | Fri | Sat | Sun
--------|-----|-----|-----|-----|-----|-----|-----
6 AM | 3 | 3 | 3 | 3 | 3 | 5 | 5
7 AM | 5 | 5 | 5 | 5 | 5 | 7 | 7
8 AM | 7 | 7 | 7 | 7 | 7 | 8 | 8
9 AM | 8 | 8 | 8 | 8 | 8 | 9 | 9
10 AM | 9 | 9 | 9 | 9 | 9 | 9 | 9
11 AM | 8 | 8 | 8 | 8 | 8 | 8 | 8
12 PM | 6 | 6 | 6 | 6 | 6 | 6 | 7
1 PM | 4 | 4 | 4 | 4 | 4 | 5 | 6
2 PM | 5 | 5 | 5 | 5 | 5 | 6 | 6
3 PM | 6 | 6 | 6 | 6 | 6 | 7 | 7
4 PM | 5 | 5 | 5 | 5 | 5 | 6 | 6
5 PM | 4 | 4 | 4 | 4 | 4 | 5 | 5
6 PM | 3 | 3 | 3 | 3 | 3 | 4 | 4
Pattern to look for: When do you consistently have high energy? Those are your deep work slots. Protect them ruthlessly.
Freelancers and solopreneurs wear many hats. Label them:
| Role | Activities | Hours/Week (Goal) |
|------|-----------|-------------------|
| Maker | Creative work, writing, coding, designing | 20-25 |
| Manager | Planning, strategy, finances | 3-5 |
| Seller | Sales calls, proposals, outreach | 3-5 |
| Marketer | Content, social media, email | 3-5 |
| Learner | Reading, courses, skill-building | 2-4 |
| Admin | Email, scheduling, bookkeeping | 2-3 |
| Recharge | Exercise, rest, social | 5-10 |
MON TUE WED THU FRI
8-10 AM │ DEEP │ DEEP │ DEEP │ DEEP │ DEEP │
10-12 │ DEEP │ DEEP │ SELL │ DEEP │ LEARN │
12-1 │ LUNCH │ LUNCH │ LUNCH │ LUNCH │ LUNCH │
1-2 │ BUFFER │ ADMIN │ BUFFER │ ADMIN │ BUFFER │
2-3 │ MEETINGS │ MEETINGS │ MEETINGS │ MEETINGS │ ADMIN │
3-4 │ MEETINGS │ MEETINGS │ MARKET │ MEETINGS │ MARKET │
4-5 │ ADMIN │ MARKET │ MARKET │ ADMIN │ REVIEW │
5-6 │ RECHARGE │ RECHARGE │ RECHARGE │ RECHARGE │ RECHARGE │
Morning: Deep work first. No email, no Slack, no social media before 12 PM.
Afternoon: Meetings, admin, light work after lunch (when energy dips anyway).
Buffer blocks: Schedule 2-3 buffer blocks per week for overflow. When something urgent comes up, it goes in the buffer, not your deep work time.
Recharge: Non-negotiable. A 20-minute walk at 4 PM preserves the 6-9 PM window.
Best for: Creatives, writers, developers, designers
| Time | Block | Notes |
|------|-------|-------|
| 6-7 AM | Morning routine | Exercise, breakfast, planning |
| 7-8 AM | Admin blast | Process email, queue responses |
| 8-11 AM | Deep Work Block 1 | 3 hours, NO interruptions |
| 11-12 PM | Light Work | Emails, quick tasks |
| 12-1 PM | Lunch + Walk | No screens |
| 1-3 PM | Deep Work Block 2 | 2 hours (lower energy) |
| 3-4 PM | Meetings / Calls | Batch all calls here |
| 4-5 PM | Admin / Planning | Tomorrow prep |
| 5-6 PM | Recharge | Walk, read, cook |
Best for: Coaches, consultants, client-heavy roles
| Time | Block | Notes |
|------|-------|-------|
| 7-8 AM | Morning planning | Review day, set intentions |
| 8-10 AM | Deep Work | Strategy, proposals, content |
| 10-12 PM | Client calls | Batch all calls |
| 12-1 PM | Lunch | |
| 1-3 PM | Client calls / Outreach | Second call block |
| 3-4 PM | Admin + Email | Process everything |
| 4-5 PM | Planning | Next day prep |
| 5-6 PM | Close | Review, journal, disconnect |
Best for: Anyone doing both creative work AND client work
┌─────────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ │ MON │ TUE │ WED │ THU │ FRI │
├─────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ 8-10 │ DEEP │ DEEP │ DEEP │ DEEP │ DEEP │
│ 10-12 │ DEEP │ DEEP │ CLIENTS │ DEEP │ LEARNING │
│ 12-1 │ LUNCH │ LUNCH │ LUNCH │ LUNCH │ LUNCH │
│ 1-2 │ ADMIN │ ADMIN │ ADMIN │ ADMIN │ ADMIN │
│ 2-3 │ CLIENTS │ CLIENTS │ CLIENTS │ CLIENTS │ PLANNING │
│ 3-4 │ CLIENTS │ MARKET │ CLIENTS │ MARKET │ PLANNING │
│ 4-5 │ ADMIN │ ADMIN │ ADMIN │ ADMIN │ REVIEW │
│ 5-6 │ RECHARGE │ RECHARGE │ RECHARGE │ RECHARGE │ RECHARGE │
└─────────┴──────────┴──────────┴──────────┴──────────┴──────────┘
| Phrase | Action |
|--------|--------|
| "Design my schedule..." | Full weekly time block design based on energy + roles |
| "Plan my day..." | Creates a daily schedule for today |
| "Help me time-block..." | Guides through the framework |
| "I'm overwhelmed..." | Audit current schedule, identify time leaks |
| "Protect my focus..." | Designs distraction-proof deep work blocks |
| "Where is my time going?" | Time audit — analyze where the week went |
| "Optimize my morning..." | Focus on the first 3 hours of the day |
| "I have a deadline..." | Reverse-plans the blocks needed to hit it |
Ask:
Use the energy map above. If the user doesn't know, suggest tracking for 3 days:
| Rule | Detail |
|------|--------|
| Minimum 2 hours | Anything less doesn't qualify as deep work |
| Morning priority | Deep work before noon. Always. |
| No context switching | One project per deep block |
| Airplane mode | Phone on DND, Slack closed, email closed |
| Visible signal | Use a status, a sign, or a door |
| Buffer Type | Duration | When |
|-------------|----------|------|
| Morning transition | 15 min | Before deep work starts |
| Between blocks | 10 min | Transition and reset |
| Overflow | 30-60 min | Daily or weekly for spillover |
| End-of-day close | 15 min | Review, plan tomorrow |
Weekly review questions:
Expect 70% adherence. Life happens. The goal is not perfection — it's intention.
> Input: "I'm overwhelmed. Client work, my own projects, emails — it's all bleeding together."
>
> Diagnosis: No separation between deep work and reactive work. Email is checked 15×/day.
>
> Prescription:
> `
> IMMEDIATE CHANGES:
> 1. No email before 10 AM
> 2. Deep work block: 8-10 AM (protected, no phone)
> 3. Admin batch: 4-5 PM (all email, invoicing, scheduling)
> 4. One no-meeting day per week (Wednesday)
>
> SAMPLE DAY:
> 7:00 Morning routine
> 8:00 DEEP WORK (client project)
> 10:00 DEEP WORK (your own project)
> 12:00 Lunch + walk
> 1:00 Light work / email catch-up
> 2:00 Client calls (batched)
> 4:00 Admin / planning
> 5:00 Done
> `
> Input: "I have a book draft due in 10 days and I've written 0 words."
>
> Reverse Plan:
> `
> Target: 40,000 words in 10 days = 4,000 words/day
>
> Daily writing blocks needed: 2× 2-hour deep blocks
> First block: 6-8 AM (before the world wakes up)
> Second block: 8-10 PM (after the world goes to sleep)
>
> Protect: No calls, no social events, no errands
> Sacrifice: TV, social media, perfectionism
>
> Daily schedule:
> 6-8 AM WRITING BLOCK 1
> 8-9 AM Breakfast + walk
> 9-12 PM Client work (income can't pause)
> 12-1 PM Lunch
> 1-3 PM Client work
> 3-5 PM Admin + errands
> 5-8 PM Dinner + rest
> 8-10 PM WRITING BLOCK 2
> 10 PM Done → sleep
>
> Accountability: Share word count with a friend every morning
> `
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take cosmicstack-labs/time-blocking-scheduler from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.