Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chunkydotdev/reply-classification
Classify inbound email replies by intent and route them appropriately.
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 11 more in the full report
10 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An inbound email arrives with header 'X-Auto-Response-Suppress: OOF' and subject 'Re: Quick question'. How should header inspection classify this email?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the message as an auto-reply due to the X-Auto-Response-Suppress header. | Missed | Passed |
The instructions your model reads when the skill loads.
Classify inbound email replies so your system knows what happened and what to do next.
inbound-processing - receiving and parsing incoming email before classificationthread-management - maintaining conversation context across reply chainsbounce-handling - processing hard/soft bounces and retry strategiessuppression-lists - managing bounces, complaints, and opt-outs after classificationemail-compliance - legal requirements for honoring unsubscribe repliesStart with a taxonomy that maps cleanly to actions. Too many categories creates ambiguity; too few misses important signals. Here is a proven set of 9 categories that covers the vast majority of reply types:
| Intent | Description | Typical action |
|---|---|---|
interested | Positive engagement - wants to learn more, book a meeting, see pricing | Notify owner immediately (5-min SLA) |
not_now | Timing is wrong but not a hard no - "maybe next quarter", "circle back later" | Auto-archive, schedule follow-up |
objection | Hard no - "not interested", "remove me", "stop emailing" | Auto-archive, suppress from sequence |
out_of_office | Vacation, leave, or away auto-reply | Auto-archive, note return date if present |
unsubscribe | Explicit opt-out request | Honor immediately, add to suppression list |
question | Asks a question without clear positive/negative signal | Route to owner for manual response |
support | Reports a problem, bug, or needs help | Route to support queue |
billing | Invoice, payment, refund, or subscription topic | Route for approval (60-min SLA) |
unclassified | No clear signal - short replies, ambiguous content | Route to owner with low-confidence flag |
Some systems add referral (forwarded to a colleague), meeting_booked (calendar confirmation), or legal/security for sensitive intents. Add these only when you have distinct actions for them - categories without actions just create noise.
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.