calendar-audit_skill

Overview

This skill protects your deep work time by auditing every meeting on your calendar, scoring each event, and producing actionable recommendations to reclaim focus hours. Value-first: the first audit runs in about two minutes from a single screenshot so you see results immediately. It supports multiple calendar inputs and several scoring frameworks to fit your role and priorities.

How this skill works

Provide a calendar snapshot or connect an automated calendar source and the skill extracts events, computes meeting costs (including context-switch overhead), and calculates your deep work budget and gap. It scores each meeting using the configured framework (default: 5-Dimension), groups meetings into actionable zones (Red/Orange/Yellow/Green), and proposes concrete time to reclaim and slots for deep work. You can review, override scores with reasons, and the skill records decisions to meeting memory for future audits.

When to use it

• Weekly check (ideally Monday mornings) to protect maker days
• When meetings feel to have crept up and you need to reclaim focused hours
• Before a high-priority work sprint or quarterly planning
• To evaluate which recurring meetings to cut, delegate, or restructure
• When onboarding to set preferences and automated calendar access

Best practices

• Start with a screenshot for a quick first audit — no setup required
• Pick a target focus ratio (recommend 60/40) and a min daily contiguous focus block (default 4h)
• Prefer automated calendar access for hands-free, consistent weekly audits
• Use meeting overrides with a reason to build meeting memory and preserve context
• Batch meetings to manager days and protect 1–2 maker days per week

Example use cases

• Engineering leader audits weekly calendar to free 8–12 hours for coding work
• ICs verify they have one 4-hour contiguous deep work block per day during a product sprint
• Managers identify recurring meetings where they are only "informed" and delegate attendance
• Teams trial skipping a low-value recurring meeting for two weeks to validate impact
• Product teams restructure long recurring syncs into async updates to reduce meeting cost