claude/plugins/local/todoist-flow/skills/todoist/SKILL.md
Todoist dashboard and router. Shows inbox count, overdue count, project health, and routes to the right sub-skill. Use when the user says 'todoist', 'check my tasks', 'task overview', 'what's on my plate', 'show me my todos', or any general Todoist inquiry that doesn't clearly map to triage/organize/update/extract.
npx skillsauth add paulnsorensen/dotfiles todoistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Entry point for the todoist-flow suite. Show the user where things stand, then route them to the right tool.
Spawn todoist-fetch to gather dashboard data in a fresh context window:
Agent(subagent_type: "todoist-fetch", prompt: "Fetch dashboard data: 1) get-overview for inbox count and project summary, 2) find-tasks with filter 'overdue' for overdue count — flag any 3+ weeks stale, 3) get-productivity-stats for completion trends. Return structured overview with counts.")
Format as a concise status board:
## Todoist Status
| Metric | Count |
|--------|-------|
| Inbox | X tasks |
| Overdue | X tasks (Y are 3+ weeks stale) |
| Due today | X tasks |
| Active projects | X |
### Health Signals
- [good/warn/critical] Overdue debt: X tasks
- [good/warn/critical] Inbox backlog: X tasks
- [good/warn/critical] P1 inflation: X tasks at P1
Based on the state, suggest the most impactful next action:
| Signal | Recommendation |
|--------|---------------|
| Overdue > 10 | "Run /triage to process overdue tasks" |
| Inbox > 20 | "Run /triage to clear inbox backlog" |
| P1 count > 5 | "Run /update to review priority inflation" |
| Projects > 15 or empty projects exist | "Run /organize to restructure projects" |
| Many noun-only or URL tasks | "Run /extract to pull out reference material" |
| Everything looks healthy | "Looking good. Run /update for routine hygiene." |
Present the suggestion but let the user decide. Don't auto-invoke sub-skills.
If the user asks for deeper context on their productivity patterns, invoke the research skill:
Skill(skill="todoist-flow:research", args="[specific topic the user asked about]")
This is opt-in — only when the user explicitly asks for research.
tools
Reconstruct what a past coding-agent session was doing so you can resume it — goal, files touched, last verified state, and the next step — by querying the session logs. Use when the user says "what was I working on", "recover that session", "reconstruct where I left off", "resume my last session", "what did that session change", "rebuild context from logs", or invokes /work-recovery. Report-only — it never scores or judges. Do NOT use for usage scoring (that is /skill-improver, /tool-efficiency, /prompt-analytics) or one-off interactive log queries (that is /session-analytics).
development
Curate this repo's hallouminate wiki (.hallouminate/wiki/, the repo:dotfiles:wiki corpus) — add or update architecture pages, per-harness docs, and gotchas. Use when the user says "update the wiki", "document this in the wiki", "refresh the harness docs", "add a wiki page", "curate the wiki", "the wiki is stale", or invokes /wiki-curator. Also use at session end to write back a non-obvious decision or gotcha worth preserving. Grounds the existing wiki first, follows one-topic-per-file conventions, verifies every external doc URL before writing, and reindexes. Do NOT use for general code search (that is cheez-search) or for editing AGENTS.md command reference.
tools
Audit how a tool, command, or MCP server is actually used across coding-agent sessions and produce calibrated recommendations — tool-vs-task fit, error forensics, fix recommendations, permission friction, MCP health, and token economics. Use when the user says "tool efficiency", "am I using X efficiently", "audit tool usage", "why does X keep failing", "how do I fix this error", "what should I change", "permission friction", "is this MCP worth it", "tool error rate", "fix recommendations", or invokes /tool-efficiency. Do NOT use for auditing a skill or agent definition (that is /skill-improver) or for one-off interactive log queries (that is /session-analytics).
tools
Analyze how prompts and skill routing behave across coding-agent sessions and produce calibrated recommendations — prompt-pattern analysis, routing accuracy, and knowledge gaps. Use when the user says "analyze my prompts", "prompt patterns", "is routing working", "which skill should have fired", "knowledge gaps", "what do I keep asking", or invokes /prompt-analytics. Do NOT use for auditing a single skill/agent definition (that is /skill-improver), tool/MCP efficiency (that is /tool-efficiency), or one-off interactive log queries (that is /session-analytics).