cowork-inbox-triage
Daily inbox triage using Cowork's email write tools (Microsoft 365 or Gmail) -- classifies unread mail, drafts replies in your voice, flags what needs a decision, and schedules follow-ups. Built to run as a recurring Cowork scheduled task.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/cowork-inbox-triage && cp -r /tmp/cowork-inbox-triage/cowork-inbox-triage ~/.claude/skills/cowork-inbox-triageSKILL.md
# Cowork Inbox Triage Work an inbox the way a good chief of staff does: everything gets a disposition, nothing gets sent without approval, and the owner ends the run with a short list of real decisions instead of 80 unread threads. Uses the connected mail tools (Microsoft 365 or Gmail MCP connectors) for reading, labeling, and drafting. ## Setup On first run, learn the owner's voice: read 10-15 sent replies and note greeting style, sign-off, sentence length, and formality. Store the profile in the conversation and reuse it for every draft. Ask once which categories matter (default set below) and what the auto-archive rules are. ## Workflow 1. **Sweep.** Pull unread and flagged threads from the last cycle (default: 24 hours). Group by thread, not message. 2. **Classify** every thread into exactly one bucket: - `NEEDS DECISION` -- only the owner can answer (pricing, commitments, personnel) - `DRAFT READY` -- routine reply Claude can write for approval - `WAITING ON THEM` -- owner already replied; schedule a follow-up check - `FYI` -- no response needed; summarize in the digest - `NOISE` -- newsletters, notifications, cold outreach; label/archive per the standing rules 3. **Draft.** For every `DRAFT READY` thread, write the reply in the owner's voice as a draft -- never send. Keep drafts shorter than the email being answered. 4. **Follow-ups.** For `WAITING ON THEM` threads past their expected response window (default 3 business days), draft a polite bump. For threads with dates in them, propose calendar holds via the calendar write tools. 5. **Digest.** Post one summary: decisions needed (with one-line context and a recommended answer each), drafts awaiting approval, follow-ups queued, and a one-line count of what was archived. ## Rules - Never send email. Create drafts only; the human sends. - Never archive anything that mentions money, contracts, legal matters, or a specific person's problem -- misclassified noise is recoverable, a missed client email is not. - A recommended answer accompanies every `NEEDS DECISION` item. Surfacing a question without a recommendation is half the job. - Quote the sender's actual ask in the digest -- do not paraphrase requests into vagueness. - Respect confidentiality: HR, health, and personal matters get flagged privately, never summarized in a shared channel. - If the connector lacks write scope, degrade gracefully: produce the digest and paste-ready reply texts instead of drafts. ## Scheduled Mode As a Cowork scheduled task (weekday mornings), run the full workflow unattended in a cloud session and deliver the digest before the workday starts. Track threads across runs so a bump is never drafted twice for the same silence. ## Quick Commands - "Triage my inbox" -- full run, last 24h - "Catch me up" -- sweep and digest only, no drafts - "Draft replies to everything easy" -- classification + drafts only - "Who am I waiting on?" -- the `WAITING ON THEM` ledger with days elapsed
Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.