outreach-replies

Solid

Triage the replies your Emelia campaigns received, and only those: the API exposes a campaign activity feed and a reply endpoint, it has no endpoint that lists a mailbox, so this is campaign reply handling and not an inbox client. Paginates the activity feed, sorts every reply by intent (interested, meeting request, not now with the follow up date extracted, out of office with the stand in contact extracted, wrong person with the referral, unsubscribe, negative), drafts an answer in the sender's own voice, blacklists every opt out immediately, and lists the manual tasks waiting on a human. Writes outreach/replies.md with one block per contact and the exact call to send each answer. It prepares, you send. Triggers on: replies, reply handling, campaign replies, answer, respond, triage, inbox, out of office, unsubscribe, opt out, blacklist, not interested, meeting request, follow up date, wrong person, referral, manual task, bounce, response rate.

AI & Automation 12 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
37
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Triage the replies to your campaigns ## What this does Reads the replies your campaigns received, sorts them by what the person actually wants, writes a draft answer for each one in the voice of the person who sent the campaign, and handles the opt outs immediately and without asking. It writes everything to `outreach/replies.md` and stops there. **The perimeter is your campaigns, not your mailbox.** Emelia's API gives you the activity feed of a campaign, which contains the replies it received, and one endpoint to answer a reply. There is no endpoint that lists a mailbox. So a message that arrived outside a campaign, or that Emelia could not attach to a contact, does not exist as far as this skill is concerned. Say that to the user the first time rather than letting them assume their inbox is being read. **It prepares, you send.** No message reaches a real person without an explicit yes from you, one message at a time. The only action taken without asking is honouring an unsubscribe, because that is an obligation, not a decision. ## When to use it Run it daily while a campaign is running, and once more a week after it ends: late replies are often the good ones. Use a different skill when you want the numbers rather than the messages (`outreach-audit` gives rates per step and per variant), when you want to fix the copy that produced these replies (`outreach-write`), or when the campaign is not sending at all, which is a deliverability question. Do not reach for it as...

Details

Author
emelia-io
Repository
emelia-io/claude-outreach
Created
3 days ago
Last Updated
2 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

outreach-campaign

Creates the campaign in Emelia and gets it launched: finds or creates the contact list, loads the contacts in bulk with their custom variables, creates the email or LinkedIn campaign, attaches the list so new contacts flow in automatically, sets the cadence, the sending window and the sending accounts, runs a pre-flight checklist (deliverability green, list verified, unsubscribe link present, every variable resolved, test email read), asks for an explicit yes, then starts it. Writes outreach/campaign.json with the real Emelia identifiers. Triggers on: campaign, launch, launch campaign, create campaign, start sending, send the sequence, go live, attach list, contact list, cadence, daily limit, sending accounts, identities, schedule, pre-flight, sequence steps, multichannel campaign.

12 Updated 2 days ago
emelia-io
AI & Automation Solid

outreach-sequence

Designs the multichannel flow of a campaign, starting from one of Emelia's five real campaign templates (Pure Cold Email, Pure Linkedin basic, Pure Linkedin Premium with InMail, LinkedIn then Email, Email then LinkedIn) rather than from a blank tree, and picking the template mechanically from the email and LinkedIn coverage the enrichment actually produced. Then: which steps exist in Emelia (email, LinkedIn visit, invitation, message, InMail, manual call task), how conditions and branches work (invitation accepted, email bounced, link clicked, reply received, contact fields such as the email and the LinkedIn profile URL), the delays that work and why, a clean A/B test with a sample size that makes the result mean something, what goes in the body of an email step (the message or its custom variable, then the signature, then a real unsubscribe link from step 2 on), and the conditions that stop a contact or stop the campaign. Produces outreach/campaign.json, the spec that outreach-campaign turns into a real camp

12 Updated 2 days ago
emelia-io
AI & Automation Solid

outreach-deliverability

Audits the sending setup before a campaign goes out: SPF, DKIM, DMARC and MX records read with dig, domain and tracking domain age, warmup state per mailbox, blacklist and health flags from Emelia, safe daily volume per mailbox and a week by week ramp plan, mailbox rotation, and the content patterns that push a cold email into spam. Returns one verdict, READY, READY WITH LIMITS or BLOCKED, with the exact list of things to fix, and writes outreach/deliverability.md. This skill is a gate: it is expected to say no. Triggers on: deliverability, spam, SPF, DKIM, DMARC, DNS, warmup, warm up, sender reputation, bounce, blacklist, inbox placement, landing in spam, daily limit, sending volume, ramp up, tracking domain, mailbox rotation, email health.

12 Updated 2 days ago
emelia-io