본문으로 건너뛰기
cccskills
무료GitHub에 공개

daily-prep

Prepare for an upcoming workday by combining Outlook meetings with open tasks and workspace context. Generate an HTML briefing with meeting preparation, scheduling conflicts, suggested priorities, and available time for learning and focused work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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 recommendations.

연동 도구Outlook
설치 방법 보기

이럴 때 유용합니다

  • Prepare for tomorrow's meetings
  • Spot overlapping meetings and scheduling issues
  • Find time for learning and focused work
  • Review priorities for a specified workday

포함된 파일(1)

  • SKILL.md8.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot4만2026년 10월 17일 업데이트

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot4만2026년 10월 17일 업데이트

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot4만2026년 10월 17일 업데이트

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot4만2026년 10월 17일 업데이트

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot4만2026년 10월 17일 업데이트

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot4만2026년 10월 17일 업데이트

github의 스킬 모두 보기

이 스킬의 문제 신고