spark-recipe-morning-standup
>-
Works with
Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
--- name: spark-recipe-morning-standup description: >- license: MIT --- # Recipe: Morning Standup Start the day with a structured briefing: today's calendar, unread mail by category, and team assignment status. **Prerequisite:** Read the `use-spark` base skill for command reference and filter syntax. **Access level required:** read-only. ## Steps ### Step 1: Today's calendar ```bash spark events --today ``` List all meetings and events for today. Note any prep needed. ### Step 2: Unread priority mail ```bash spark emails Inbox --filter "category:priority is:unread" ``` Auto-prioritized or manually flagged items - the most important emails. ### Step 3: Unread people mail ```bash spark emails Inbox --filter "category:personal is:unread" ``` Direct conversations that likely need a response today. ### Step 4: Team assignment status ```bash spark team "Team Name" ``` Review the assignment summary - who has open items, any unassigned work. ### Step 5: Present the briefing Summarize for the user: - **Calendar:** N meetings today (list times and titles) - **People mail:** M unread (list senders and subjects) - **Priority mail:** K unread - **Team:** open assignments per member, any unassigned items ## Tips - This recipe works best first thing in the morning or at the start of a work session. - Skip step 4 if the user doesn't work with teams. - Add `spark emails Inbox --filter "category:invitation"` after step 3 if the user has pending invitations. - For a quicker briefing, just run steps 1-3 - calendar plus priority and people mail covers the essentials.
More Data Engineering skills
data-pipeline
claude-office-skills/skills
Data pipeline and ETL automation - extract, transform, load workflows for data integration and analytics
4.1k
ETL Pipeline
claude-office-skills/skills
Design and automate Extract, Transform, Load data pipelines for data integration and analytics
4.0k
data-throughput-accelerator
affaan-m/ecc
Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.
3.6k

