skills/ github/awesome-copilot

daily-prep

Prepare for tomorrow''s meetings and tasks. Pulls calendar from Outlook via WorkIQ, cross-references open tasks and workspace context, classifies meetings, detects conflicts and day-fit issues, finds learning and deep-work slots, and generates a structured HTML prep file with productivity recommenda

0
Installs
—
Rating
—
Success rate
1
Files scanned
Scan passedfrontend
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

1 files scannedscanner v1.2.0Oct 10, 2026

Content sha256 3a9a12ee7c59fb9d… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

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

Files

1
8.4 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from github/awesome-copilot8

acquire-codebase-knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narr

Needs review 0
acreadiness-assess

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when

Scan passed 0
acreadiness-generate-instructions

Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in

Scan passed 0
acreadiness-policy

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights,

Scan passed 0
ad-campaign-analyzer

Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign plann

Scan passed 0
add-educational-comments

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

Scan passed 0
adobe-illustrator-scripting

Write, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model,

Scan passed 0
agent-architecture

Design AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.

Scan passed 0

Related frontend skillsscan passed

error-tracking-svelte

PostHog error tracking for Svelte

Scan passed 0
migrate-radix-to-base

Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.

Scan passed 0
trpc-router

Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.

Scan passed 0
frontend-ui-engineering

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-gene

Scan passed 0
motion-patterns

Production-ready animation patterns for React / Next.js — button, modal, toast, stagger, page transitions, exit animations, scroll, and layout — built on motion-foundations tokens and springs. Use when animating a specific UI element in React or Next.js — button, modal, toast, stagger, page transiti

Scan passed 0
metronome

Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepai

Scan passed 0