Personal Agenda Secretary

The Problem

When tasks are scattered across chats, notes, or verbal requests, personal scheduling tends to create duplicates, lost status, and stale backlog. This skill focuses on task capture, not task execution: it turns “submit the report tomorrow” into a trackable item instead of writing the report for the user. It organizes input into searchable, replayable, archivable local files rather than a one-off conversation.

How It Works

The skill maintains a local structure around tasks/, index.md, log.md, and views/dashboard.html:
- Ingest: extracts multiple to-dos from inbox/ or pasted text, infers title, due, category, and priority, then writes tasks/YYYYMMDD-short-description.md.
- Update: changes frontmatter status, notes, and the index when the user says an item is done, cancelled, or needs a note.
- View: syncs task state into the embedded TASKS_DATA in dashboard.html, producing a double-clickable local dashboard.
Deadlines are inferred from cues such as today, tomorrow, this week, and this month; items without clear timing go to someday. The skill also maintains views/tasks.json and views/tasks.js archives, deduplicating completed tasks older than the first day of the month two months ago to keep the dashboard bounded.

Boundaries

It fits personal workflows that need structured to-dos, deadline inference, a local dashboard, and archive review; it does not replace calendar reminders, email sending, or complex project management. The dashboard uses embedded JSON and is read-only in the browser, with no online service or database dependency. If a task should be executed, the user should explicitly say “do XX for me”.