New to Claude Skills? Learn how to install them →

github on GitHub

Daily Prep

OfficialFree

Streamline your next day's meetings and tasks.

by github37.7k stars on github/awesome-copilot
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Daily Prep does

Daily Prep is designed to help professionals prepare effectively for their upcoming workdays by generating a structured HTML prep file that consolidates meeting details, tasks, and productivity recommendations. By utilizing the WorkIQ MCP tool, Daily Prep pulls calendar information, cross-references open tasks, and assesses workspace context to create a comprehensive overview of the next day's schedule. This skill is particularly useful for individuals who want to enhance their productivity and ensure they are well-prepared for meetings and tasks ahead.

The process begins by determining the target date for preparation, defaulting to tomorrow unless specified otherwise. Daily Prep then fetches calendar events for that date, classifying meetings based on their nature and attendees. This classification helps users quickly identify high-priority meetings, potential conflicts, and the overall structure of their day. The skill also flags any scheduling issues, such as early or after-hours meetings, ensuring that users can make informed decisions about their time.

In addition to meeting details, Daily Prep identifies available time slots for learning and focused work. It analyzes the day's schedule to find gaps suitable for upskilling or deep work, providing users with actionable insights on how to allocate their time effectively. The final output is a well-organized prep file that not only lists meetings and tasks but also includes recommendations for optimizing productivity throughout the day.

This skill is ideal for professionals looking to enhance their daily planning routine, ensuring they make the most of their time and are prepared for the challenges of the workday. Whether used at the end of the day or for weekly planning, Daily Prep offers a structured approach to managing one's schedule and tasks efficiently.

When to use it

Use Daily Prep at the end of the workday to prepare for tomorrow or at any time to check a specific future date.

When not to use it

This skill may not be suitable for users who do not rely on structured meeting preparation or those who prefer a more spontaneous approach to their workday.

What you can build with it

End of Day Preparation

At the end of the workday, use Daily Prep to generate a structured overview of meetings and tasks for the following day.

Weekly Planning

Run Daily Prep at the start of the week to prepare for multiple days ahead, ensuring a well-organized schedule.

Conflict Detection

Utilize Daily Prep to identify potential scheduling conflicts and make adjustments to your calendar proactively.

How to install Daily Prep

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/daily-prep --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by github

Daily Prep

Generate a structured prep file for the next working day with meeting details, prep bullets, linked tasks, and productivity recommendations.

When to Use

  • End of day: "prepare me for tomorrow"
  • Any time: "prep me for Friday" or "what does March 25 look like?"
  • Weekly planning: run for multiple days

Procedure

1. Determine Target Date

If the user specifies a date, use it. Otherwise, default to tomorrow (current date + 1 day). If tomorrow is Saturday, default to Monday. If Sunday, default to Monday. Compute the output path: outputs/YYYY/MM/YYYY-MM-DD-prep.html

2. Pull Calendar via WorkIQ

Use the WorkIQ MCP tool to fetch the calendar. Ask WorkIQ:

"What meetings do I have on {target date}? For each meeting, include: subject, start time, end time, organizer, all attendees with their email addresses, location, whether it's online, and whether I've accepted or declined."

If the response is insufficient, make a follow-up query:

"For the meetings on {target date}, which ones are marked as optional or tentative? Which ones are recurring?"

3. Classify Each Meeting

Apply these labels based on attendee domains and subject:

LabelCriteria
[Customer · HIGH]External attendees from customer/partner domains, or subject matches a known customer name
[Internal]Only internal company domain attendees
[Community]CoP, community, guild, learning sessions
[Upskilling]Training, workshop, certification, learning
[Optional · skip]Tentative, low importance, or known recurring optional (e.g., "Office Hours", "Open Q&A")
[Personal]Private events, non-work

Zone Markers

For every meeting, check the organizer field and apply these additional markers:

ConditionMarkerAction
Starts ≥ 15:30 and < 16:00 (any organizer)⚠️ After-hoursRecommend decline
Starts ≥ 16:00 and not self-organized⚠️ After-hoursRecommend decline
Starts ≥ 16:00 and self-organized(no flag)OK — you chose to schedule it
Before 09:00 and not self-organized⚠️ EarlyRecommend decline — intrudes on learning window
Before 09:00 and self-organized(no flag)OK — you chose to schedule it
Overlaps 12:00–13:00🍽️ Lunch conflictNote in Calendar Notes

"Self-organized" means you are the meeting organizer (check the organizer field from WorkIQ).

4. Ideal Day Structure

Use this as the decision framework for all analysis steps. Every meeting must be evaluated against these zones. Users should adapt these times and targets to their personal routine.

ZoneTimePurposeRules
Morning FocusBefore 09:00Admin, learning, personal workProtect from others' meetings. Flag external events.
Customer Zone09:00–12:00Customer / external meetingsMax 2 customer meetings. Prefer mornings for external calls.
Lunch12:00–13:00BreakProtected. Flag any overlap.
Deep Work13:00–15:30Deliverables, focused coding/writingMinimize meetings. Flag non-essential meetings as deep work disruption.
Protected (strict)15:30–16:00End of day wind-downFlag all meetings regardless of organizer.
Protected (flex)16:00+End of dayFlag others' meetings only. Self-organized OK.

Targets per day:

  • Learning hours: 1.5h (from morning focus + gap time)
  • Deep work hours: 2.5h (13:00–15:30 zone)
  • Customer meetings: max 2 (preferably in 09:00–12:00)

5. Detect Conflicts & Day Fit Issues

Compare event time windows. Flag overlaps in a Conflicts table with a recommendation for each — prioritize customer meetings over internal/optional.

Also detect these day fit issues (report in a separate "Day Fit Issues" table):

CheckConditionFlag
Customer overload>2 [Customer · HIGH] meetingsFlag 3rd+ as "Consider rescheduling to another day"
Deep work disruptionNon-essential meetings in 13:00–15:30 zone"Disrupts deep work — consider moving to morning"
Non-ideal placementCustomer meetings outside 09:00–12:00"Customer meeting outside preferred morning zone"
Early intrusionOthers' meetings before 09:00"Intrudes on learning window — recommend decline"
Lunch conflictMeeting overlaps 12:00–13:00"Conflicts with lunch break"

6. Gather Context from Workspace

  1. Read open task files for tasks related to customer names or attendees in tomorrow's meetings
  2. Search workspace folders for recent files related to those customers or topics
  3. Check recent meeting summaries or plans for relevant prep context
  4. Use this to generate actionable prep bullets per meeting

7. Generate Prep per Meeting

For each meeting (chronological), include:

  • Time, subject, organizer
  • Attendee list (first name, company if external)
  • 3–5 actionable prep bullets based on open tasks, recent summaries, and meeting subject
  • If no context available, note what to ask/clarify in the meeting

8. Find Learning & Focus Slots

After generating prep per meeting, analyze the day's schedule to find open slots:

  1. Morning Focus confirmation — Verify the morning focus window is clear. If any non-self-organized event exists there, flag it.

  2. Learning Slots — Find gaps ≥ 30 min in the morning window and any other free slots suitable for upskilling. Target: 1.5h/day. For each slot: time range, duration, suggested activity.

  3. Deep Work Blocks — Find continuous free gaps in the 13:00–15:30 zone for deliverables. For each block: time range, duration, suggested task from open tasks.

  4. Report totals:

    • Learning hours found vs. 1.5h target (e.g., "1.0h / 1.5h target — 0.5h short")
    • Deep work hours available in 13:00–15:30 (e.g., "2.0h / 2.5h available")

9. Productivity Recommendations

Analyze the full day and provide:

SectionWhat to Include
Day Fit ScoreRate 0–100% how well the day matches the Ideal Day Structure. Criteria: (1) morning focus clear (+20%), (2) ≤2 customer meetings in 09:00–12:00 (+20%), (3) lunch 12:00–13:00 protected (+15%), (4) deep work 13:00–15:30 intact (+20%), (5) nothing after 15:30 or only self-organized after 16:00 (+15%), (6) ≥1h learning slots found (+10%). Show as: 🟢 ≥80%, 🟡 50–79%, 🔴 <50%.
Day ShapeTotal meeting hours, focus time available, learning hours, deep work hours, heavy/moderate/light assessment
Decline CandidatesAuto-include: (1) all meetings 15:30–16:00, (2) others' meetings ≥16:00, (3) others' meetings <09:00, (4) 3rd+ customer meeting, (5) optional meetings during deep work zone. Show "Reclaim" column with minutes recovered. Self-organized meetings before 09:00 or after 16:00 are excluded from auto-decline.
Conflict ResolutionSpecific recommendation for each overlap
Learning SlotsGaps for upskilling — from Step 8. Table: Window, Duration, Suggested Activity. Show total vs. 1.5h target.
Deep Work BlocksFree gaps in 13:00–15:30 for deliverables — from Step 8. Table: Window, Duration, Suggested Task.
Energy ManagementFlag if >3h back-to-back customer meetings without a break
Top 3 PrioritiesThe 3 most impactful things to accomplish (meetings + tasks combined)

10. Write the File

Create the output file at outputs/YYYY/MM/YYYY-MM-DD-prep.html as a self-contained HTML file with embedded CSS (dark theme, color-coded timeline, responsive layout).

If a file already exists for that date, read it first and update rather than overwrite — the user may have added manual notes.

Example Prompts

  • "Prepare me for tomorrow"
  • "What does Friday look like?"
  • "Daily prep for March 28"
  • "Prep me for next Monday — focus on customer meetings"

Requirements

  • WorkIQ MCP tool must be available for calendar access (Microsoft 365 / Outlook)
  • A workspace with task files and customer/project folders for context enrichment
  • Output is self-contained HTML — no external dependencies

Frequently asked questions about Daily Prep

Similar skills