How do I install the Spark Recipe Shared Inbox Status skill?

Run npx skillmds add readdle/spark-recipe-shared-inbox-status 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 Shared Inbox Status 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 Shared Inbox Status?

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 Shared Inbox Status free to use?

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

Who published Spark Recipe Shared Inbox Status?

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

Spark Recipe Shared Inbox Status by readdle

Name: Spark Recipe Shared Inbox Status
Rating: 4.2 (5 reviews)
Author: readdle

File contents

Recipe: Shared Inbox Status

Review the health of one or more shared inboxes - open items, completed work, unassigned emails, and how assignments are distributed across team members.

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

Access level required: read-only.

Steps

Step 1: Discover shared inboxes

spark accounts

Note each shared inbox address and the team it belongs to.

Step 2: Check open items

For each shared inbox:

spark emails shared@co.com:Inbox --filter "is:shared_inbox_open"

These are active items that still need attention.

Step 3: Check unassigned items

spark emails shared@co.com:Inbox --filter "assigned_to:unassigned"

Unassigned items are falling through the cracks - no one owns them yet.

Step 4: Review per-member assignments

spark team "Team Name"

The assignment summary shows how work is distributed. For a deeper look at a specific member's load:

spark emails shared@co.com:Inbox --filter "assigned_to:alice@co.com"
spark emails shared@co.com:Inbox --filter "assigned_to:bob@co.com"

Step 5: Check completed items

spark emails shared@co.com:Inbox --filter "is:shared_inbox_done"

Review recently completed items for a sense of throughput.

Step 6: Present the status

Report per shared inbox:

Open: N items awaiting action
Unassigned: M items with no owner
Per member: assignment counts (flag anyone with significantly more or fewer)
Done: K items completed recently

If there are multiple shared inboxes, present each separately, then a combined summary.

Tips

Run this daily for active shared inboxes, weekly for quieter ones.
Unassigned items are the most actionable finding - they represent work that nobody is looking at.
Combine per-member counts with recipe-team-workload for a fuller picture of who has bandwidth.
If a shared inbox has high open count but low unassigned count, work is distributed but not being closed - look for stale assignments.
Use spark thread <id> to read any item that looks stale or unusual.
For teams with multiple shared inboxes, the total unassigned count across all inboxes is the key metric.

---name: spark-recipe-shared-inbox-statusdescription: Review shared inbox health: open vs. done items, unassigned work, and per-member assignment breakdown.--- # Recipe: Shared Inbox Status Review the health of one or more shared inboxes - open items, completed work, unassigned emails, and how assignments are distributed across team members. **Prerequisite:** Read the `use-spark` base skill for command reference and filter syntax. **Access level required:** read-only. ## Steps ### Step 1: Discover shared inboxes ```bash spark accounts ``` Note each shared inbox address and the team it belongs to. ### Step 2: Check open items For each shared inbox: ```bash spark emails shared@co.com:Inbox --filter "is:shared_inbox_open" ``` These are active items that still need attention. ### Step 3: Check unassigned items ```bash spark emails shared@co.com:Inbox --filter "assigned_to:unassigned" ``` Unassigned items are falling through the cracks - no one owns them yet. ### Step 4: Review per-member assignments ```bash spark team "Team Name" ``` The assignment summary shows how work is distributed. For a deeper look at a specific member's load: ```bash spark emails shared@co.com:Inbox --filter "assigned_to:alice@co.com" spark emails shared@co.com:Inbox --filter "assigned_to:bob@co.com" ``` ### Step 5: Check completed items ```bash spark emails shared@co.com:Inbox --filter "is:shared_inbox_done" ``` Review recently completed items for a sense of throughput. ### Step 6: Present the status Report per shared inbox: - **Open:** N items awaiting action - **Unassigned:** M items with no owner - **Per member:** assignment counts (flag anyone with significantly more or fewer) - **Done:** K items completed recently If there are multiple shared inboxes, present each separately, then a combined summary. ## Tips - Run this daily for active shared inboxes, weekly for quieter ones. - Unassigned items are the most actionable finding - they represent work that nobody is looking at. - Combine per-member counts with `recipe-team-workload` for a fuller picture of who has bandwidth. - If a shared inbox has high open count but low unassigned count, work is distributed but not being closed - look for stale assignments. - Use `spark thread <id>` to read any item that looks stale or unusual. - For teams with multiple shared inboxes, the total unassigned count across all inboxes is the key metric.

Frequently asked questions