How do I install the Spark Recipe Inbox By Category skill?

Run npx skillmds@latest add readdle/spark-recipe-inbox-by-category 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 Inbox By Category safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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 Inbox By Category?

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 Inbox By Category free to use?

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

Who published Spark Recipe Inbox By Category?

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

Spark Recipe Inbox By Category by readdle

Name: Spark Recipe Inbox By Category
Rating: 4.5 (4 reviews)
Author: readdle

File contents

Recipe: Inbox by Category

Process the inbox in priority order using Spark's smart categories. This ensures the most important messages get attention first.

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

Access level required: read-only.

Steps

Step 1: Priority mail (highest priority)

spark emails Inbox --filter "category:priority is:unread"

Emails Spark auto-prioritized or that the user manually marked as priority. These are the most important items.

Step 2: People mail

spark emails Inbox --filter "category:personal is:unread"

Direct person-to-person emails. Real conversations that usually need a response.

Step 3: Pending invitations

spark emails Inbox --filter "category:invitation"

Calendar invitations waiting for a response. Time-sensitive by nature.

Step 4: Notifications

spark emails Inbox --filter "category:notification is:unread"

Service notifications, alerts, and receipts. Scan for anything actionable, then move on.

Step 5: Newsletters

spark emails Inbox --filter "category:newsletter newer_than:7d"

Subscriptions and digests from the past week. Skim for interest, skip the rest.

Step 6: Summarize

Report to the user:

N unread people emails (with subjects/senders for the most recent)
M unread priority emails
K pending invitations
Notification and newsletter counts (don't list unless asked)

Tips

This is the recommended default when the user asks "what's new" or "catch me up."
Skip steps 4 and 5 for a quick briefing - priority + people + invites covers the essentials.
For each category, only dig into spark thread <id> when the user asks about a specific email.
Combine with spark events --today for a full morning briefing.

--- name: spark-recipe-inbox-by-category description: >- Process inbox in priority order by Spark's smart categories: priority first, then people, invites, notifications, newsletters. metadata: version: 1.0.0 requires: skills: - use-spark accessLevel: read-only --- # Recipe: Inbox by Category Process the inbox in priority order using Spark's smart categories. This ensures the most important messages get attention first. **Prerequisite:** Read the `use-spark` base skill for command reference and filter syntax. **Access level required:** read-only. ## Steps ### Step 1: Priority mail (highest priority) ```bash spark emails Inbox --filter "category:priority is:unread" ``` Emails Spark auto-prioritized or that the user manually marked as priority. These are the most important items. ### Step 2: People mail ```bash spark emails Inbox --filter "category:personal is:unread" ``` Direct person-to-person emails. Real conversations that usually need a response. ### Step 3: Pending invitations ```bash spark emails Inbox --filter "category:invitation" ``` Calendar invitations waiting for a response. Time-sensitive by nature. ### Step 4: Notifications ```bash spark emails Inbox --filter "category:notification is:unread" ``` Service notifications, alerts, and receipts. Scan for anything actionable, then move on. ### Step 5: Newsletters ```bash spark emails Inbox --filter "category:newsletter newer_than:7d" ``` Subscriptions and digests from the past week. Skim for interest, skip the rest. ### Step 6: Summarize Report to the user: - N unread people emails (with subjects/senders for the most recent) - M unread priority emails - K pending invitations - Notification and newsletter counts (don't list unless asked) ## Tips - This is the recommended default when the user asks "what's new" or "catch me up." - Skip steps 4 and 5 for a quick briefing - priority + people + invites covers the essentials. - For each category, only dig into `spark thread <id>` when the user asks about a specific email. - Combine with `spark events --today` for a full morning briefing.

Frequently asked questions

Spark Recipe Inbox By Category