task-pulselisted

Answer ad-hoc questions about the user's Notion Tasks DB. Query by project, type, due date, status, or staleness and return a concise readout. Use whenever the user asks "what's open for X", "what's due Friday", "anything stale", "what did I finish this week", "any P0 tasks", or similar status checks against the unified Tasks DB. Read-only — never writes, never marks done, never reschedules.
ericluo04/claude-academic-workflow · ★ 3 · AI & Automation · score 66

Install: claude install-skill ericluo04/claude-academic-workflow

# /task-pulse — read-only status checks against the Tasks DB ## Personalization This skill resolves placeholders against `~/.claude/state/personal_config.json`. See `_config/README.md` and `_config/personal_config.example.json` for setup. If the config is missing or a needed field is unset, the skill must surface an error to the user and refuse to proceed rather than guess. Required config fields: - `personal_config.notion.tasks_data_source_id` - `personal_config.projects[].name` and optional `aliases` (used for project-name shortcuts) ## Purpose The user wants quick on-demand visibility into the task pipeline without opening Notion. This skill takes a free-text question, builds one or two filtered queries against the Tasks data source, and returns a concise bulleted readout. It is **strictly read-only**. Never call any tool that mutates Notion. To change a task, use `/capture` (via Telegram) or edit Notion directly. ## Live IDs - Tasks data source: `{{personal_config.notion.tasks_data_source_id}}` - Use URL form `collection://{{personal_config.notion.tasks_data_source_id}}` with `mcp__notion__notion-fetch`, or pass the bare UUID to query tools. ## Schema (case-sensitive) | Property | Type | Values | |---|---|---| | Task | title | — | | Status | select | To-do / In progress / Waiting / Done / Dropped | | Priority | select | P0 / P1 / P2 / P3 | | Due | date | — | | Est min | number | — | | Type | select | Research / Teaching / Admin / Personal / Health / Travel / Soc