mcpField
S
spark-recipe-weekly-digest

spark-recipe-weekly-digest

github.com/readdleProductivity154359 installsUpdated 6d ago
Repository

About spark-recipe-weekly-digest

spark-recipe-weekly-digest is a read-only Spark skill for producing a weekly overview of events, unread email, team assignments, and meeting transcripts. It is intended for users who want a concise view of upcoming or recent work.

Key features

  1. 01List the week’s calendar events
  2. 02Count unread email by category
  3. 03Review team assignments and unassigned work
  4. 04Find recent meetings with transcripts

Use cases

  1. 01Review the week ahead on Monday
  2. 02Summarize the week on Friday
  3. 03Spot open assignments and team bottlenecks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-weekly-digest

After installing, type/spark-recipe-weekly-digestin Claude Code to confirm it loaded.

Details

From the project README

Recipe: Weekly Digest

Generate a weekly summary covering calendar events, unread email by category, and team status.

Prerequisite: Read the use-spark base skill for command reference and filter syntax.

Access level required: read-only.

Steps

Step 1: This week's calendar
spark events --week

List all meetings and events for the week.

Step 2: Unread email breakdown by category
spark emails Inbox --filter "category:priority is:unread newer_than:7d"
spark emails Inbox --filter "category:personal is:unread newer_than:7d"
spark emails Inbox --filter "category:notification is:unread newer_than:7d"
spark emails Inbox --filter "category:newsletter newer_than:7d"

Count items in each category for the summary.

Step 3: Team status
spark team "Team Name"

Review assignment summary - open items per member, unassigned work.

Step 4: Recent meeting transcripts
spark meetings --filter "newer_than:7d"

List meetings that have transcripts available for review.

Step 5: Present the digest

Summarize for the user:

  • Calendar: N events this week (highlight important ones)
  • Email: unread counts by category (people: M, priority: K, notifications: L, newsletters: J)
  • Team: open assignments, any bottlenecks
  • Meetings: transcripts available for review

Tips

  • Run this recipe on Monday morning for a forward-looking view, or Friday afternoon for a retrospective.
  • Skip the team step if the user doesn't work with teams.
  • For the email breakdown, just report counts - don't list individual emails unless asked.
  • If the user has multiple accounts, run spark accounts first and report per-account.
  • Combine with recipe-inbox-by-category to process the most active categories first.

Comments

Markdown supported