Daily Planner

Plan and manage your day with prioritized tasks, calendar blocking, energy-based scheduling, and automatic commitment tracking and reminders.

Security Scan

The skill's planning behavior is generally coherent, but it implicitly expects broad access to calendars, email, notifications, and conversational content (with automated logging/sending) without declaring or limiting those permissions — this mismatch raises privacy/control concerns.

Purpose & Capability

The name and description (daily planning, calendar blocking, commitment tracking) match the instructions: the agent reads calendar/events, schedules blocks, logs commitments, and writes plan files under ~/planner/. However, the runtime instructions assume the ability to read calendars, emails, notifications, and to send/reschedule calendar events and replies. The skill declares no required credentials or connectors — that omission is noteworthy (it may rely on platform-provided connectors, but the skill doesn't document or limit the scopes it needs).

Instruction Scope

SKILL.md instructs the agent to "pull calendar events," read "emails flagged as 'needs decision' (if email access)", extract commitments from conversations automatically, pause notifications, enable auto-replies, reschedule meetings, draft/send summaries and notifications, and share daily summaries with partners. Those actions can read and transmit sensitive data and perform outbound actions on the user's behalf. The instructions give broad discretion ("log automatically", "if agent has control", "after approval: reschedule and draft notifications") without explicit user-consent checkpoints or limiting rules, increasing risk of unwanted data exposure or automated outbound actions.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest-risk install model: nothing is downloaded or written by the installer beyond the normal skill metadata. The only persistent footprint is the described ~/planner/ directory written at runtime.

Credentials

The registry metadata lists no required environment variables or credentials, yet the skill implicitly needs access to calendar APIs, email, notification controls, and possibly contacts to send summaries/reminders. The absence of declared credentials isn't itself malicious (the platform may supply connectors) but the skill should explicitly document required integrations and the exact scopes (read calendar, write calendar, send email, access messages) so users can grant minimal permissions. Also, automatic extraction of commitments from conversations could capture unrelated sensitive content.

Persistence & Privilege

The skill writes persistent files under ~/planner/ (config, today, commitments, weekly, archive). That persistence is expected for a planner, but combined with autonomous invocation (model invocation allowed by default) and instructions to auto-log commitments and send/reschedule messages, there is potential for the agent to act without fine-grained user approval. always:false reduces immediate concern, but there are no explicit safeguards in the instructions (e.g., read-only mode, explicit approval flows, or audit logs) for outbound actions.

What to consider before installing

Before installing, confirm which integrations this skill will use (calendar, email, contacts, notifications) and require it to list exact scopes (read calendar, create events, send email, read messages). Ask the vendor/author to: (1) require explicit consent for automatic actions (auto-send, reschedule, auto-replies) and provide an opt-in toggle; (2) add a confirmation step before logging commitments extracted from conversations; (3) document where files in ~/planner/ are stored and how to delete them; (4) show an audit log of outbound actions; and (5) request least-privilege connectors (read-only where appropriate). If you cannot get clear, scoped permissions and explicit consent controls, treat this skill as high-risk for privacy and automated outbound actions and avoid granting it write/send permissions.

Quick Reference

File	Purpose
profiles.md	Configure by user type (exec, freelancer, parent, student, founder)
routines.md	Morning briefing, evening review, weekly planning
priorities.md	Top 3 system, urgent vs important matrix
calendar.md	Time blocking, deep work protection, conflict detection
tracking.md	Commitment tracking, follow-up reminders

Storage

Data stored in ~/planner/:

• config — Profile, energy windows, constraints
• today — Current day plan (regenerated daily)
• commitments — Open commitments and follow-ups
• weekly — Week overview with deadlines
• archive/ — Past plans for patterns

What the Agent Does

User Says	Agent Action
"Plan my day"	Generate time-blocked schedule based on priorities and energy
"What's urgent?"	Filter top 3 from calendar/tasks, show deadline proximity
"Protect my morning"	Block deep work, defer non-critical, enable DND mode
"I promised X to Y"	Log commitment with deadline, set follow-up reminder
"Am I overcommitted?"	Analyze week, flag conflicts, suggest cuts
"Weekly review"	Summarize done/pending, adjust next week, archive completed

Core Loop

Morning (configurable time):

1. Pull calendar events, pending tasks, open commitments
2. Apply profile rules (energy windows, constraints)
3. Generate Top 3 priorities (what MUST happen today)
4. Produce briefing: 5 bullets max, critical first

During day:

• Track new commitments from conversations
• Alert on deadline proximity (48h, 24h, 2h)
• Batch interruptions, filter by configured urgency

Evening:

• What got done, what moved forward
• Commitments made today logged
• Tomorrow's preview

See routines.md for full workflow details.

Priority Rules

• Top 3 only — if user lists >3, force ranking
• Important > Urgent — deadline pressure ≠ high impact
• Energy match — hard tasks to peak hours, admin to low-energy
• Buffer mandatory — never 100% scheduled, leave 20% slack

See priorities.md for prioritization framework.

Profile-Based Behavior

The agent adapts to user type. On first use, ask or infer profile:

• Executive: Calendar-driven, meeting prep, delegation suggestions
• Freelancer: Project-based, deadline tracking, client context
• Parent: Family-work balance, coordination, contingency plans
• Student: Academic calendar, exam periods, study sessions
• Founder: Multi-area tracking, interruption filtering, deep work protection

See profiles.md for profile-specific behaviors.

Commitment Tracking

Every promise made = logged automatically:

• Extract from conversations: "I'll send you X by Y"
• Add to commitments file with deadline
• Remind before deadline (configurable: 24h, 48h)
• Flag overdue until resolved

See tracking.md for commitment workflow.