spark-recipe-shared-inbox-triage

Process open shared inbox items by assigning ownership and marking resolutions done.

136|6|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spark-recipe-shared-inbox-triage
Source: https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-shared-inbox-triage
Command: npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires use-spark.

What problem does it solve?

Shared inboxes can accumulate open items that no one owns, making it hard to route requests correctly and keep resolutions accurate.

Core Features & Use Cases

  • Open-item processing: Reviews shared inbox items end-to-end by listing open and then drilling into each thread.
  • Routing and resolution actions: Assigns unassigned work to the right owner, drafts replies when possible, and adds internal coordination comments.
  • Queue hygiene: Marks resolved items as done and re-checks completed items to confirm they’re truly finished, for example after a team rotates shifts.

Quick Start

Use the shared inbox triage recipe to list open items for a shared inbox, assign them to the right people, respond or comment as needed, and mark resolved items done.

Frequently Asked Questions about spark-recipe-shared-inbox-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage unassigned items in a shared email inbox?

To triage unassigned items in a shared email inbox, you can review open threads, assign ownership to the right team members, draft replies, add internal comments, and mark resolved items as done.

What is the best way to manage shared inbox routing and task assignment for a team?

The best way to manage shared inbox routing and task assignment is by listing open items, drilling into each thread to assign ownership, and adding internal coordination comments to ensure accurate resolutions.

Do I need Spark to process open shared inbox items and track email resolutions?

Yes, you need the use-spark skill to provide command references for processing open shared inbox items, applying filters, enforcing triage access permissions, and tracking email resolutions.

Can I re-check completed shared inbox items to confirm they are truly finished after a shift rotation?

Yes, you can maintain queue hygiene by re-checking completed shared inbox items to confirm they are truly finished, which is especially useful for verifying resolution accuracy after a team rotates shifts.

How does shared inbox triage handle access-level permissions when routing email responses?

Shared inbox triage enforces triage access-level permissions when routing email responses, ensuring only authorized users can assign unassigned work, draft replies, and mark items done.

What are the limitations of using automated recipes for shared inbox triage?

A limitation of automated shared inbox triage is that it requires the use-spark dependency for command execution and depends on existing shared inbox filters to accurately separate open versus done items.