<< All versions
Skill v1.0.1
currentAutomated scan100/100lightspeedwp/.github/google-calendar-free-up-time
+8 new
──Details
PublishedNovember 6, 2026 at 07:44 PM
Content Hashsha256:306710389a956b9c...
Git SHA29dd52ed4a83
Bump Typepatch
──Files
Files (1 file, 2.7 KB)
SKILL.md2.7 KBactive
SKILL.md · 45 lines · 2.7 KB
name: google-calendar-free-up-time description: Find ways to open up meaningful free time in a connected Google Calendar. Use when the user wants to clear up their day, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back. metadata: version: "1.0.1"
Google Calendar Free Up Time
Use this skill when the goal is to create time, not just inspect time.
Relevant Actions
- Use
search_eventsto map the day's current fragmentation and identify movable candidates. - Use
read_eventorread_event_all_fieldswhen one candidate meeting needs a closer look before proposing a move. - Use
create_eventwhen the user explicitly wants a temporary hold or focus block once the target slot is grounded. - Use
update_eventonly after the proposal is clear and setupdate_scopetothis_instance,entire_series, orthis_and_followingonce the correct scope of change is grounded.
Workflow
- Start by identifying the target: today, tomorrow, this afternoon, a specific day, or a broader window. If the user already gave a concrete window or duration, work inside it before asking follow-up questions.
- Optimize for contiguous free blocks, not raw free-minute totals.
- Identify which meetings are likely fixed and which are more movable before proposing changes.
- If the user explicitly wants a temporary hold or focus block rather than a reschedule plan, choose the best qualifying free slot and create the hold once the slot is clear.
- Look for the smallest edit set that creates a meaningful uninterrupted block.
- Prefer solutions that reduce fragmentation across the rest of the day, not just one local gap.
- If no clean block exists, show the best partial win and what tradeoff it requires.
Prioritization Heuristics
- Protect hard anchors such as external meetings, major reviews, commute buffers, or lunch if it is already a stable part of the day.
- Move lower-cost meetings first, such as optional events, transparent holds, lightweight internal syncs, or self-created placeholders.
- Favor one or two coherent shifts over a chain of many tiny moves.
- Prefer creating one useful block over scattering a few small openings.
Output Conventions
- Show the before-and-after effect of the proposal.
- Name the block of time created and the minimum meetings that would need to move.
- When creating a hold, state the exact slot and whether the hold is transparent or busy.
- If suggesting multiple options, keep them short and explain the tradeoff for each.
_Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!_ Contributors