Claude Marketplaces
SkillsMCP serversMarketplacesDigestTools
Submit

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP servers by category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control
Claude Marketplaces

An independent directory of skills, plugins and MCP servers for Claude Code. Not affiliated with Anthropic.

Browse

  • Skills
  • MCP servers
  • Marketplaces
  • Weekly digest
  • Skill index
  • MCP index
  • Marketplace index

Site

  • About
  • Tools
  • Submit
  • Feedback
  • Privacy
  • llms.txt
  • Plugins reference

Maker

  • Snug
  • Agent Caffeine
  • knobs
  • Wax
  • Vectoys
  • mertduzgun.com
Crafted at
Skills/Frontend Development
github avatar

Daily Prep

github/awesome-copilotOfficial

This pulls your Outlook calendar through WorkIQ, classifies each meeting by type (customer, internal, optional), flags conflicts and bad timing, then generates a structured HTML prep file with actionable bullets for each event. The real utility is in the day fit analysis: it scores your schedule against an ideal structure (protected morning learning time, customer calls before noon, deep work 1-3:30pm, nothing after 3:30pm unless you scheduled it), automatically identifies decline candidates, and finds gaps for focus work. It's opinionated about when meetings should happen and who gets to claim your after-hours, which makes it genuinely useful if you're constantly fighting calendar creep. Best run at end of day or Sunday evening for the week ahead.

installs
1.3K
GitHub stars
40.5K
last updated
Aug 21, 2026
View on GitHubSave

Install

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

Installs into .claude/skills of the current project.

Files

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
SKILL.md on GitHub

Sponsors

SnugThe clipboard manager you and your agent can use, safelyAgent CaffeineClose your lid, come back to finished workWaxBlock anything with supervision, without erasing your iPhoneOpen StepsSponsoredFree and open-source skills that make AI coding agents easier to understand, verify, and control.

Details

Repository
github.com/github/awesome-copilot
Categories
Frontend Development, Git & Pull Requests, AI & Agent Building
First seen
Apr 16, 2026

More from github/awesome-copilot

All 318
  • Roundup1.3K
  • Roundup Setup1.3K
  • Freecad Scripts1.2K
  • React19 Test Patterns1.2K
  • Arize Prompt Optimization1.1K
  • Lsp Setup1.1K
  • Arize Ai Provider Integration1.1K
  • Arize Evaluator1.1K
  • Agent Supply Chain1.1K
  • Mcp Security Audit1.1K
  • Arize Dataset1.1K
  • Arize Annotation1.1K
  • Arize Instrumentation1.1K
  • Integrate Context Matic1.1K
  • Arize Experiment1.1K
  • Arize Trace1.1K
  • Arize Link1.1K
  • React19 Concurrent Patterns1.1K
  • Phoenix Evals1K
  • Phoenix Tracing1K
  • Onboard Context Matic1K
  • Phoenix Cli1K
  • React19 Source Patterns968
  • Python Pypi Package Builder945

Recommended

More Frontend Development
1kostja94 avatarcarouselkostja94/marketing-skillsWhen the user wants to design, optimize, or audit carousel/slider layouts for content display. Also use when the user mentions "carousel," "slider," "carousel l1.3Kinstalls
2davila7 avatar3d-web-experiencedavila7/claude-code-templatesExpert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfoli1.3Kinstalls
3hyva-themes avatarhyva-child-themehyva-themes/hyva-ai-toolsCreate a Hyvä child theme in a Magento 2 project. This skill should be used when the user wants to create a new Hyvä child theme, set up a custom theme based on1.3Kinstalls
4joeseesun avatardefuddlejoeseesun/defuddle-skillExtract clean article content from web pages or local HTML files. Removes clutter (ads, sidebars, nav) and returns readable content with metadata.1.3Kinstalls
5arjitj2 avatarswiftui-design-principlesarjitj2/swiftui-design-principlesDesign principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKi1.3Kinstalls
6hyperb1iss avatartui-designhyperb1iss/hyperskillsThis skill should be used when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building 1.3Kinstalls