daily-checkin - SKILL.md Agent Skill

name: daily-checkin description: Morning check-in with yesterday review and today's plan (~3-5 min) disable-model-invocation: false

Daily Check-In

Morning check-in with two parts: review yesterday, plan today. Keep it conversational but concise.

Before Starting

Check the time first: Run date "+%A %B %d %Y %l:%M %p" via Bash to get the actual day of week, date, and time. Use this for greeting (good morning/afternoon/evening) and all date logic below. Never calculate the day of week mentally.
Token expiry: If any calendar tool returns a token expiry error, run npm run auth via Bash to re-authenticate. Wait for the user to complete the browser OAuth flow, then retry.
Fetch the user's profile (profile_get) — use their name and goals for context throughout.
Check today's day of week (from the date output above):
- Saturday/Sunday → suggest /weekend-checkin instead (lighter touch for weekends).
- Sunday evening or the user's preferred planning day → mention that /weekly-planning or /weekly-review might be due.
If $ARGUMENTS contains skip-yesterday, jump straight to Part 2.

Part 1 — Yesterday Review

Fetch yesterday's checklist (checklist_get with yesterday's date) for any still-open items. Ask: "Did you finish these, or should they carry over?" Tip: When marking yesterday's items complete, use checklist_update with date set to yesterday's date — this triggers a cascade that auto-completes carried-over copies in today's checklist.
Fetch yesterday's daily log (daily_log_get). If habits weren't logged, ask briefly about each.
Ask for a quick reflection: "How was yesterday? One sentence is fine." Optionally ask mood (great/good/okay/rough/bad) and energy (1-5) if it feels natural.
Save yesterday's log with the updated habits and reflection (daily_log_update).

Part 2 — Today's Plan

Fetch today's calendar events and run schedule_analyze.
Fetch today's checklist with checklist_get.
Create today's daily log with habits pre-populated (daily_log_update with plannedHighlights).
Brief overview: events, density, conflicts, warnings.
Highlight the most important event and top checklist items.
Show free slots and suggest an order of attack.

Launch Dashboard

After presenting the plan, ensure the dashboard is running:

Start the Vite dev server if not already running: cd dashboard && npm run dev (run in background)
Open the browser: open http://localhost:5173

Throughout the Day

When the user completes checklist items outside of the morning check-in, follow the Item Completion Workflow in CLAUDE.md — mark the item done, prompt for billing info if the area is billable, and update the daily log's actualHighlights.

When the checklist changes significantly (items added/removed, priorities shifted), consider updating plannedHighlights via daily_log_update — see Planned Highlights Revisit in CLAUDE.md.

Tone

Conversational, brief, encouraging. Don't over-explain — the user does this daily. If yesterday was rough, acknowledge it without dwelling. Focus energy on today's plan.