reply-classification

Classify inbound email replies by intent using header checks and keyword scoring.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/chunkydotdev/email-skills --skill reply-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reply-classification
Source: https://github.com/chunkydotdev/email-skills/tree/main/skills/inbound/reply-classification
Command: npx skills add https://github.com/chunkydotdev/email-skills --skill reply-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually sorting through inbound email replies is slow, inconsistent, and risky for high-volume workflows like sales outreach, customer support, and transactional email. Failing to quickly identify hot leads, honor unsubscribe requests, or handle bounces can lead to lost revenue, CAN-SPAM compliance violations, and damaged sender reputation.

Core Features & Use Cases

  • Proven 9-category intent taxonomy: Maps common reply types (interested, not interested, out-of-office, bounce, unsubscribe, question, support, billing, unclassified) directly to actionable routing rules.
  • Near-perfect auto-reply and bounce detection: Uses RFC-standard header checks to identify automated responses and delivery status notifications without analyzing message content.
  • Weighted keyword intent scoring: Classifies non-automated replies with subject-weighted matching, density adjustment, and confidence thresholds to reduce false positives.
  • Built-in safety and compliance guardrails: Parallel safety classification blocks phishing and malicious content, while rules automatically honor unsubscribe requests and escalate high-risk intents like legal or security queries.
  • Use cases: Prioritize hot sales leads, triage support inboxes, manage transactional email opt-outs, and reduce manual triage time for high-volume inbound email flows.

Quick Start

Use the reply-classification skill to categorize the most recent inbound reply to your sales outreach email, then route it to the appropriate team or queue based on its classified intent and confidence level.

Frequently Asked Questions about reply-classification

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

FAQPage Schema
How do I automate email reply classification for inbound sales outreach?

Automate email reply classification by categorizing inbound messages into a 9-category intent taxonomy to enable automated routing. This process uses weighted keyword scoring and RFC-standard header checks to prioritize hot leads and filter out out-of-office replies.

What is the best way to detect email bounces and out-of-office replies without reading message content?

Email bounce and out-of-office detection is best handled using RFC-standard header checks to identify automated responses and delivery status notifications. This method accurately flags auto-replies without needing to analyze the message body content.

How can I ensure CAN-SPAM compliance when processing high-volume inbound email replies?

Ensure CAN-SPAM compliance by using parallel safety classification and automated rules to instantly honor unsubscribe requests within inbound email replies. This workflow also escalates high-risk legal or security intents to protect sender reputation.

How does keyword intent scoring reduce false positives in email routing workflows?

Keyword intent scoring reduces false positives by applying subject-weighted matching, density adjustment, and confidence thresholds to classify non-automated email replies. Conflict detection ensures accurate routing when ambiguous keywords appear.

Can I use this email triage skill for customer support inboxes?

You can use this email triage skill for customer support inboxes because it maps reply types like support, billing, and question directly to actionable routing rules. This allows you to separate support queries from sales outreach automatically.

What are the limitations of using header-based detection for email bounce classification?

Header-based detection for email bounce classification is limited to identifying RFC-standard automated responses and delivery status notifications. Non-standard or malformed bounce headers may fall through to unclassified categories, requiring manual triage.