mcpbeat Sign in

Cowork Calendar Defrag Skill for Claude

Audit your calendar with Cowork's calendar tools -- measure meeting load and fragmentation, identify which recurring meetings earn their slot, propose consolidations and focus blocks, and draft the diplomatic messages that reclaim your week.

877 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill cowork-calendar-defrag

The instruction itself

5 sections, as written by the author

Cowork Calendar Defrag

Treat the calendar like a disk that needs defragmenting: measure what is actually there, identify waste, consolidate, and carve out contiguous space for real work. Uses the connected calendar tools (Microsoft 365 / Google Calendar) to read events; every change is proposed, and the human approves before anything is created, moved, or declined.

Workflow

  • Measure. Pull the last 4 weeks and the next 2. Compute: hours in meetings per week, longest uninterrupted block per day, fragmentation score (count of gaps under 45 minutes -- too short to do real work, long enough to lose), meetings by type (recurring vs. ad hoc, internal vs. external), and after-hours creep.
  • Score the recurring load. For each recurring meeting: duration x frequency x attendee count = weekly cost. Flag candidates against the classic tells -- no agenda in the invite, attendance optional-in-practice, could-be-async status updates, double-booked slots the user routinely skips. External and client meetings are measured but never flagged for cuts without explicit instruction.
  • Propose the defrag. A specific plan, not principles: which recurrings to shorten (60 -> 25), consolidate (three 1:1s into office hours), make async, or leave alone; where the 2-3 weekly focus blocks go (matched to when the calendar shows the user actually has energy-adjacent free space, e.g. mornings); and which small gaps to close by nudging meetings adjacent.
  • Draft the messages. For each proposed change involving other people: a short, warm, blame-free draft ("I'm consolidating my recurring syncs -- can we fold this into..."). The awkward message is the real barrier to a better calendar; remove it.
  • Execute on approval. Create the focus blocks (marked busy, named for the work), send nothing -- updated invites and messages remain drafts for the human to send. Output calendar-defrag-report.md with before/after metrics: meeting hours reclaimed, longest block gained.

Rules

  • Read freely, write only what was approved, send nothing. Calendars are shared surfaces; a wrong move is publicly visible.
  • Never propose cutting external, client, or 1:1-with-manager meetings unless the user asked for a full-scope review.
  • Fragmentation is the enemy, not meetings. Six hours of meetings in two blocks beats four hours scattered across nine slots.
  • Focus blocks get names ("Proposal writing") -- anonymous "Busy" blocks get scheduled over within two weeks.
  • Respect the user's stated no-touch zones (school pickup, gym, standing personal events) as hard constraints.
  • Re-run comparisons honestly: if the defrag did not hold (blocks got booked over), report it and diagnose which changes stuck.

Scheduled Mode

As a monthly Cowork scheduled task: re-measure, compare against the last report, flag regression (creeping recurrings, eroded focus blocks), and propose the next round of cuts.

Quick Commands

  • "Audit my calendar" -- steps 1-2, the measurement and scorecard
  • "Defrag my week" -- full workflow
  • "Where can I fit 3 hours of deep work?" -- focus-block placement only
  • "Draft the decline for [meeting]" -- one diplomatic message

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

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.

4k tokens
File Organizer
by frostant
×10

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.

3k tokens
Domain Name Brainstormer
by frostant
×8

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.

1k tokens
Brainstorming
by ZhanlinCui
×4

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.

626 tokens
Planning With Files
by ZhanlinCui
×3

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.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

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.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

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".

3k tokens

How to use it

Copy the folder

Take onewave-ai/cowork-calendar-defrag from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.