How do I install the Spark Recipe Weekly Digest skill?

Run npx skillmds add readdle/spark-recipe-weekly-digest in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spark Recipe Weekly Digest safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spark Recipe Weekly Digest?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spark Recipe Weekly Digest free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spark Recipe Weekly Digest?

readdle (@readdle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spark Recipe Weekly Digest by readdle

Name: Spark Recipe Weekly Digest
Rating: 4.2 (5 reviews)
Author: readdle

File contents

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.

---name: spark-recipe-weekly-digestdescription: Weekly summary: this week's meetings, unread email breakdown by category, and team assignment status.--- # 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 ```bash spark events --week ``` List all meetings and events for the week. ### Step 2: Unread email breakdown by category ```bash 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 ```bash spark team "Team Name" ``` Review assignment summary - open items per member, unassigned work. ### Step 4: Recent meeting transcripts ```bash 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.

Frequently asked questions