skills.rest
readdle
readdleOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spark-recipe-shared-inbox-status

Count open, unassigned, completed, and per-member assigned work items in shared inboxes.

136|6|Updated Apr 22, 2026
Search Tags:#triage#workload distribution#team productivity#shared inbox#assignment tracking#email operations#backlog health
One-click install
npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spark-recipe-shared-inbox-status
Source: https://github.com/readdle/spark-cli-skills/tree/main/skills/recipe-shared-inbox-status
Command: npx skills add https://github.com/readdle/spark-cli-skills --skill spark-recipe-shared-inbox-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared inboxes can quietly fall out of balance, leaving open items unowned and team workload uneven, which leads to missed follow-ups and delayed responses.

Core Features & Use Cases

  • Shared inbox health overview: Summarizes open items, completed throughput, and unassigned work so you know what needs attention first.
  • Assignment distribution visibility: Breaks down how work is assigned across team members and highlights uneven ownership patterns.
  • Operational focus for triage: Helps managers and leads identify backlog risk (too many open items) and execution gaps (unassigned items).

Quick Start

Use the skill to review one shared inbox by asking: "Review [email protected] for open, unassigned, per-member assignment counts, and recently done items."

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

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

FAQPage Schema
How do I check shared inbox health and workload distribution for my team?▼

To check shared inbox health, you can review open items, unassigned work, completed throughput, and per-member assignment counts to identify workload imbalances and backlog risks quickly.

What is the best way to track unassigned emails in a shared inbox?▼

Tracking unassigned emails involves highlighting unowned work items alongside per-member assignment counts, which reveals execution gaps and uneven ownership patterns within team email operations.

Can I use this shared inbox triage analysis for multiple inboxes on a weekly basis?▼

Yes, the read-only analysis applies to both daily and weekly team workflows, supporting email triage and shared inbox management across teams and multiple inboxes without modifying mailbox state.

How do I identify backlog risk and missed follow-ups in team email operations?▼

Identifying backlog risk requires summarizing open items and completed throughput, while spotting execution gaps means checking for unassigned work that can lead to missed follow-ups and delayed responses.

Do I need a specific base skill to analyze assignment tracking in Spark shared inboxes?▼

Yes, you need the use-spark base skill to provide command reference and filter syntax for the read-only analysis that counts open, unassigned, completed, and per-member assigned work items.

Does running shared inbox operational analysis modify my mailbox state?▼

No, the shared inbox operational analysis is strictly read-only, meaning it counts open, completed, and assigned items to assess workload distribution without modifying your mailbox state.

Related Skills

Explore More Product & Management Skills→
readdlereaddle
136

spark-persona-founder

Filters and action priority/personal inbox items for founder-level triage in Spark.

Official
Intermediate
readdlereaddle
136

spark-recipe-team-workload

Audit team email assignments to reveal per-member workload distribution.

Official
Intermediate
phoenixvcphoenixvc

sync-backlog

Synchronize local backlog items with GitHub or Linear issue trackers.

Official
Advanced
Jia-Hong-PengJia-Hong-Peng

setup-deploy

Detects and configures deployment settings for platforms like Vercel, Netlify, and AWS, then persists them to CLAUDE.md for automated future use.

Community
Advanced