Agent skill

Spark Recipe Shared Inbox Triage

by readdle in readdle/spark-cli-skills

Process open items in shared inboxes: review, assign, respond, or mark done.

MITAuto-check passedProductivity & Automation

Install Spark Recipe Shared Inbox Triage

skills CLI
$ npx skills add readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install readdle/spark-cli-skills spark-recipe-shared-inbox-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/readdle/spark-cli-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/recipe-shared-inbox-triage .claude/skills/spark-recipe-shared-inbox-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spark-recipe-shared-inbox-triage
GitHub stars
149
Token cost
~573 tokens
SKILL.md length
208 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Process open items in shared inboxes: review, assign, respond, or mark done.

  • Works in 5 steps: List open items → Check unassigned items (highest priority) → Review each item → …
  • Tasks that involve Email management
  • SKILL.md covers Steps and Tips
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spark Recipe Shared Inbox Triage is an agent skill from readdle/spark-cli-skills. Process open items in shared inboxes: review, assign, respond, or mark done.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Email management. The licence is MIT.

When your agent uses it

  • Tasks that involve Email management

Example prompts

  • “/spark-recipe-shared-inbox-triage”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. List open items
  2. Check unassigned items (highest priority)
  3. Review each item
  4. Take action
  5. Review completed items

What it can do on your machine

Read from SKILL.md and the folder at commit cb20383. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spark Recipe Shared Inbox Triage loads about 573 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 208 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~573

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from readdle/spark-cli-skills at commit cb20383, republished under its MIT licence (© readdle). 208 words, ~573 tokens.

Download SKILL.mdSave it as .claude/skills/spark-recipe-shared-inbox-triage/SKILL.md (or your agent's skills folder).
name
spark-recipe-shared-inbox-triage
description
Process open items in shared inboxes: review, assign, respond, or mark done.
metadata.version
1.0.0

Recipe: Shared Inbox Triage

Process open items in shared inboxes. Review each item, assign to the right person, respond where possible, and mark resolved items as done.

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

Access level required: triage.

Steps

Step 1: List open items
bash
spark emails shared@company.com:Inbox --filter "is:shared_inbox_open"

Replace shared@company.com:Inbox with the actual shared inbox identifier from spark folders.

Step 2: Check unassigned items (highest priority)
bash
spark emails shared@company.com:Inbox --filter "is:shared_inbox_open assigned_to:unassigned"

These need someone to own them.

Step 3: Review each item
bash
spark thread <id>

Read the full conversation to understand the request.

Step 4: Take action

Assign to the right person:

bash
spark action assign <id> --assignee specialist@co.com --comment "Billing question, your area"

Respond directly if you can:

bash
spark draft --reply-to <id> --body "..."

Comment for internal coordination:

bash
spark comment <id> --body "I've contacted the vendor about this, waiting for their response"

Mark as done if resolved:

bash
spark action markAsDone <id>
Step 5: Review completed items
bash
spark emails shared@company.com:Inbox --filter "is:shared_inbox_done"

Periodically check that completed items are truly resolved.

Tips

  • Start with unassigned items - they're the most urgent because nobody is handling them.
  • Use spark team to see team members and their current assignment load before assigning.
  • Always add a --comment when assigning to explain why that person should handle it.
  • Process the queue in a batch: list all, review, assign, then move on - don't switch between inbox and individual items.
  • Mark items as done immediately after resolution to keep the queue accurate.
  • Use spark folders to find the exact shared inbox identifier (e.g., shared@company.com:Inbox).

© readdle, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/recipe-shared-inbox-triage of readdle/spark-cli-skills.

Open the folder on GitHubat commit cb20383

Compare with similar skills

Spark Recipe Shared Inbox Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spark Recipe Shared Inbox Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spark Recipe Shared Inbox Triage this skillreaddle/spark-cli-skills149—~573Automated safety check: PassMIT
Garden Inboxpaperclipai/paperclip100k—~1.1kAutomated safety check: PassMIT
Continuetelegramdesktop/tdesktop33k2 repos~9.4kAutomated safety check: PassGPL-3.0
Process Inboxtelegramdesktop/tdesktop33k1 repos~5.4kAutomated safety check: PassGPL-3.0
Process InboxTDesktop-x64/tdesktop3k—~4.3kAutomated safety check: PassGPL-3.0
Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops74k—~233Automated safety check: NotesMIT

Similar skills

  • Garden Inbox

    paperclipai/paperclip

    Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.

    100k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed
  • Process Inbox

    telegramdesktop/tdesktop

    Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.

    33k GitHub starsUsed in 1 repo~5.4k tokens
    Productivity & AutomationAuto-check passed
  • Process Inbox

    TDesktop-x64/tdesktop

    Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.

    3k GitHub stars~4.3k tokensUpdated 19 days ago
    Productivity & AutomationAuto-check passed
  • Career-Ops Gmail Lead Plugin

    career-ops-hq/career-ops

    Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.

    74k GitHub stars~233 tokensUpdated today
    Productivity & AutomationAuto-check: notes
  • Atomicmail

    Atomic-Mail/atomic-mail-agentic

    Read and write email through the Atomic Mail from an AI agent.

    266 GitHub starsUsed in 1 repo~2k tokens
    Productivity & AutomationAuto-check passed

More from readdle/spark-cli-skills

All 34 skills in this repo
  • Spark Persona Exec Assistant

    readdle/spark-cli-skills

    Executive assistant persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~775 tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Founder

    readdle/spark-cli-skills

    Founder / CEO persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • 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.

    149 GitHub stars~14k tokensUpdated 4 days ago
    Auto-check: warnings
  • Spark Persona Freelancer

    readdle/spark-cli-skills

    Freelancer / solo operator persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Meeting Manager

    readdle/spark-cli-skills

    Meeting manager persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed
  • Spark Persona Project Manager

    readdle/spark-cli-skills

    Project manager persona for Spark. An agent skill from readdle/spark-cli-skills.

    149 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

Questions about Spark Recipe Shared Inbox Triage

What does Spark Recipe Shared Inbox Triage do?

Process open items in shared inboxes: review, assign, respond, or mark done. Spark Recipe Shared Inbox Triage is an agent skill from readdle/spark-cli-skills. Process open items in shared inboxes: review, assign, respond, or mark done.

When should I use Spark Recipe Shared Inbox Triage?

Spark Recipe Shared Inbox Triage fits situations like: tasks that involve Email management.

How do I install Spark Recipe Shared Inbox Triage in Claude Code?

Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage -a claude-code`. Or copy the skill folder (skills/recipe-shared-inbox-triage in readdle/spark-cli-skills) into .claude/skills/spark-recipe-shared-inbox-triage in your project. Claude Code loads it when a task matches its description.

How do I install Spark Recipe Shared Inbox Triage in Codex?

Run `npx skills add readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage -a codex`. Or copy the skill folder (skills/recipe-shared-inbox-triage in readdle/spark-cli-skills) into .agents/skills/spark-recipe-shared-inbox-triage in your project. Codex loads it when a task matches its description.

Can I use Spark Recipe Shared Inbox Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spark-recipe-shared-inbox-triage, .gemini/skills/spark-recipe-shared-inbox-triage, .github/skills/spark-recipe-shared-inbox-triage and .opencode/skills/spark-recipe-shared-inbox-triage in your project.

What does Spark Recipe Shared Inbox Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Spark Recipe Shared Inbox Triage is instructions for the agent only.

Does Spark Recipe Shared Inbox Triage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spark Recipe Shared Inbox Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spark Recipe Shared Inbox Triage use?

Spark Recipe Shared Inbox Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spark Recipe Shared Inbox Triage use?

About 573 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spark Recipe Shared Inbox Triage?

Skills that share tags, products or a category with Spark Recipe Shared Inbox Triage: Garden Inbox (paperclipai/paperclip, 100k stars), Continue (telegramdesktop/tdesktop, 33k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Process Inbox (TDesktop-x64/tdesktop, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spark Recipe Shared Inbox Triage?

readdle (a GitHub organization) maintains it in readdle/spark-cli-skills, which has 149 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: readdle/spark-cli-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.