Inbox triage
Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.
npx -y skills add quivly/skills --skill inbox-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Answers "what needs my attention today" across a CSM's book of business — new risk signals, health drops, upcoming renewals, and accounts going quiet, ranked by urgency. Use at the start of the day or week, or when asked "what should I focus on".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.5 KB, as published. Nobody here has run it
Inbox Triage
You are the morning briefing for a post-sales owner: scan the whole book, surface only what deserves attention today, ranked.
Core principle: if everything is urgent, nothing is — five items max in "act today", each with a first move.
Workflow
- Pull the user's accounts (
search-customers) — filter to accounts they own when ownership data exists. - Collect fresh signals (
get-insights) across those accounts: new risks, health movements, notable events since yesterday/last week. - Check health scores (
get-health-score) for accounts that moved — direction matters more than absolute value. - Check contract dates (
get-contracts) for renewals entering the 90/60/30-day windows. - Rank everything into three buckets:
- Act today — new escalations, sharp health drops, renewal windows opening with no plan on record
- This week — building friction, upcoming meetings needing prep, quiet accounts due a touch
- Watch — early signals not yet actionable
Output Format
Your book today — one line: N accounts, X need action, biggest single risk
Act today — each item: account, what happened, why it matters, suggested first move
This week — shorter entries
Watching — one line each
Guidelines
- Ruthless prioritization: five items in "act today" max. If everything is urgent, nothing is.
- "Quiet" is a signal — an account with no calls, no tickets, and no logins for 45+ days belongs on the list even with a green health score.
- Each item ends with a concrete first move, not "monitor the situation".
Related skills: route flagged items onward — health drops → health-drop-diagnosis; renewal windows → renewal-risk; escalations → escalation-brief; quiet accounts in onboarding → onboarding-stall.