
spark-recipe-shared-inbox-status
Review shared inbox health: open vs. done items, unassigned work, and per-member assignment breakdown.
- Installs
- 338
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-status- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads spark-recipe-shared-inbox-status automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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-workloadfor 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.
FAQ
What does the spark-recipe-shared-inbox-status skill do?
Review shared inbox health: open vs. done items, unassigned work, and per-member assignment breakdown.
How do I install spark-recipe-shared-inbox-status?
Run npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-status in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/spark-recipe-shared-inbox-status/ (personal) or .claude/skills/spark-recipe-shared-inbox-status/ (project).
Which AI agents can use spark-recipe-shared-inbox-status?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is spark-recipe-shared-inbox-status safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains spark-recipe-shared-inbox-status?
It is published by readdle in readdle/spark-cli-skills. It has 338 recorded installs.
More from readdle/spark-cli-skills
use-spark
readdle/spark-cli-skills
Use the spark CLI to access the user's Spark email data - list emails, search by topic, read threads, check calendar events, find availability, look up contacts, and view team info. Use when the user asks about their emails, calendar, contacts, meetings, or scheduling.
spark-recipe-morning-standup
readdle/spark-cli-skills
Morning standup briefing: today's events, unread people and priority mail, and team assignment status.
spark-recipe-inbox-by-category
readdle/spark-cli-skills
Process inbox in priority order by Spark's smart categories: priority first, then people, invites, notifications, newsletters.
spark-recipe-end-of-day
readdle/spark-cli-skills
End-of-day review: check for loose ends, review pinned items, and preview tomorrow's calendar.
spark-recipe-weekly-digest
readdle/spark-cli-skills
Weekly summary: this week's meetings, unread email breakdown by category, and team assignment status.
spark-recipe-meeting-prep
readdle/spark-cli-skills
Prepare for an upcoming meeting: check agenda, search for email context, look up attendee details, and flag open threads that should be raised.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.