Agent skill
morning-routine
Orchestrates a full morning sweep of pending items (email, tasks, Slack, WhatsApp, X). Use when the user asks for a sweep, morning routine, inbox sweep, or all pending items.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/morning-routine
SKILL.md
Morning Routine (sweep)
Goal
Deliver a complete summary of active pending items in a single response. Omit any source with no results.
Sources
- Email (skill: email)
- Tasks (justdoit)
- Slack (skill: slack)
- WhatsApp (skill: whatsapp-evo)
Flow
- Run ALL sources in parallel (use parallel Bash tool calls or background tasks). Do NOT run them sequentially.
- Email: run
scripts/email-inbox(from the email skill folder) and render the output exactly using the email skill's format/triage (includes rules and emojis). Do not reinterpret or change its rules. - Tasks: run
justdoit next --idsand show the full output without the suffixes(due YYYY-MM-DD)or[id: ...]. Keep sections (Today/This week/Backlog) and calendar lines. - Slack: run
scripts/slack-inbox --json-out /tmp/slack-inbox.jsonand show only the clean list. Save metadata. Use a 60-second timeout. - WhatsApp: run
scripts/whatsapp-inbox --json-out /tmp/whatsapp-inbox.jsonand show only the clean list. Save metadata. - Wait for all parallel calls to finish, then assemble the output in order: Email, Tasks, Slack, WhatsApp.
- If a source returns no results, omit it from the output.
- If a source times out, include it in the Incidents section instead of blocking the whole sweep.
- Do not propose actions or replies (except the email triage emojis). Only report.
- If there are errors or missing credentials, include an "Incidents" section with the exact error.
Output format
- Include sections only for sources with results.
- Do not truncate lists.
- Suggested format:
Tasks <full justdoit output without due/ids>
Slack
Incidents
Extensibility
To add a new source:
- Add it to the order in "Flow".
- Define the base command and where it stores metadata.
- Include its section in "Output format".
- Keep the rule of omitting sources with no results.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?