
spark-recipe-multi-account-review
Review inbox status across multiple email accounts with per-account breakdown and cross-account priorities.
- Installs
- 353
- 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-multi-account-review- 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-multi-account-review 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: Multi-Account Review
For users with multiple email accounts, review each account's inbox status and present a unified summary with per-account breakdown.
Prerequisite: Read the use-spark base skill for command reference and filter syntax.
Access level required: read-only.
Steps
Step 1: Discover all accounts
spark accounts
Note each account email, its access level, and associated calendars and teams.
Step 2: Check folders per account
For each account, see the folder structure and message counts:
spark folders user@work.com
spark folders user@personal.com
spark folders user@sideproject.com
Step 3: Review unread mail per account
For each account, check unread across key categories:
spark emails user@work.com --filter "is:unread"
spark emails user@personal.com --filter "is:unread"
spark emails user@sideproject.com --filter "is:unread"
For a category-level breakdown on the most active account:
spark emails user@work.com --filter "category:priority is:unread"
spark emails user@work.com --filter "category:personal is:unread"
Step 4: Cross-account priority check
Check priority mail across all accounts at once:
spark emails Inbox --filter "category:priority is:unread"
This uses the unified inbox to surface priority items regardless of which account received them.
Step 5: Present the summary
Report per account:
- work@company.com: N unread (X priority, Y people)
- personal@gmail.com: M unread
- side@project.com: K unread
Highlight cross-account priorities and any account that needs immediate attention.
Tips
- Start with
spark accountsto discover all configured accounts and their access levels. - The unified inbox (
spark emails Inbox) aggregates across all accounts - use it for cross-account priority checks. - Per-account browsing (
spark emails user@example.com) keeps things separated when the user wants to focus on one context. - Use
spark folders <account>to understand each account's folder structure before browsing specific folders. - Some accounts may be read-only while others have triage access.
accountsshows the access level for each. - For users with work + personal accounts, suggest processing them separately to maintain mental context.
- Combine with
recipe-inbox-by-categoryfor a deep dive into the most active account.
FAQ
What does the spark-recipe-multi-account-review skill do?
Review inbox status across multiple email accounts with per-account breakdown and cross-account priorities.
How do I install spark-recipe-multi-account-review?
Run npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-multi-account-review 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-multi-account-review/ (personal) or .claude/skills/spark-recipe-multi-account-review/ (project).
Which AI agents can use spark-recipe-multi-account-review?
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-multi-account-review 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-multi-account-review?
It is published by readdle in readdle/spark-cli-skills. It has 353 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
Open the skill to read its SKILL.md instructions.
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
Open the skill to read its SKILL.md instructions.
spark-recipe-weekly-digest
readdle/spark-cli-skills
Open the skill to read its SKILL.md instructions.
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.