competitor-email-teardown
Skill1 starsChanged 16 days agoMITView on GitHub
Benchmarks rival email programs from inbox exports, measuring welcome speed, frequency, signup offers, discounts, subject lines and sale timing against your Klaviyo or Mailchimp program, with three sized tests. Use when asked to analyze, track or tear down competitor emails or welcome series.
In this repository19 other files it gives its agents.
- cancel-flow-dunning-plannerSkill
- churn-risk-winback-plannerSkill
- customer-segmentation-rfmSkill
- email-campaign-analystSkill
- email-campaign-calendarSkill
- email-deliverability-auditorSkill
- email-lifecycle-strategySkill
- email-list-cleanerSkill
- email-list-growth-optimizerSkill
- email-platform-setup-migrationSkill
- email-send-checkSkill
- email-sequence-builderSkill
- html-email-template-builderSkill
- klaviyo-flow-auditorSkill
- loyalty-vip-program-designerSkill
- newsletterSkill
- push-inapp-message-plannerSkill
- retention-cohort-analystSkill
- sms-whatsapp-plannerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask whether the user already has rival emails with dates.
- Distinctive: line 19
Leave the inboxes alone. Don't buy anything and don't enter payment details.
- Distinctive: line 20
Wait 56 days if you can, ideally across one sale event (a holiday, a seasonal sale).
- Distinctive: line 21
When the teardown is done, unsubscribe the research addresses.
- Distinctive: line 28
The window and time zone: Default: day 0 is the signup date, through day 55, in the user's time zone.
- Distinctive: line 35
Ask for every email each inbox received in the window, as a paste, a CSV, or a mailbox export (Gmail: put each rival under its own label, …
- Very specific: line 46
Call query_contexts with request="accounts" for klaviyo or mailchimp.
- Very specific: line 47
Call query_contexts with request="actions_details" for the actions below and follow the body shapes it returns.
- Very specific: line 49
Every read goes through query_data.
- Distinctive: line 53
If a call fails, mark that part unknown, name the call, and never fill the gap with a guess.
- Distinctive: line 76
No seed inbox export?: Read what your own seed profile received instead:
- Very specific: line 80
Don't pass fields[event] with profile_id.
- Distinctive: line 148
Frequency is not a test here: When your regular emails a week are 0.5 or more away from the rival median, list it as a handoff: a frequency …
- Distinctive: line 171
Never sign up, subscribe or create an inbox for the user, and never use a real person's details for research.
- Distinctive: line 174
Every number in the report comes from the inboxes or from a call this skill made.
- Distinctive: line 175
No em or en dashes in the report.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitor Email Teardown
Turns a few weeks of rival emails into numbers you can set beside your own program. Every measure has one fixed definition, so a rival's inbox and yours are counted the same way. Your own side adds what no inbox can show: your click and order rates and your signup volume, which decide which gaps are worth a test and how long each test takes.
Before you start
The research inboxes (the user does this, never Claude)
Ask whether the user already has rival emails with dates. If not, give them this setup and stop until they have at least 28 days of mail:
- Make one address per rival on a domain or mailbox the business owns, for example
research+rivalname@yourbrand.com. Never use a person's private address, a colleague's name, or anyone else's details. - Sign up to every rival on the same day, from their own signup form, and write down the exact time of each signup and the offer the form showed.
- Sign your own seed address up to your own list the same day, the same way. Your program is then measured exactly like theirs.
- Leave the inboxes alone. Don't buy anything and don't enter payment details. Starting a cart with the research address is optional; if the user does it, note which rival and when, because that triggers cart emails the comparison would otherwise miss.
- Wait 56 days if you can, ideally across one sale event (a holiday, a seasonal sale). 28 days is the minimum.
- When the teardown is done, unsubscribe the research addresses.
Claude never fills in a signup form, never creates an inbox and never subscribes anyone.
What to ask
- The rivals. Two to five, with their sites.
- The window and time zone. Default: day 0 is the signup date, through day 55, in the user's time zone.
- The sale event inside the window, with its date. Default: none; the sale rows are then "not graded".
- The discount ceiling: the deepest discount the business will ever give. Default: the deepest % off in the user's own emails in the window.
- The smallest lift worth detecting in a test. Default: 20% relative.
The emails, without a connection
Ask for every email each inbox received in the window, as a paste, a CSV, or a mailbox export (Gmail: put each rival under its own label, then export with Google Takeout as MBOX; Outlook: export the folder). Each email needs:
- received date and time, with the time zone
- sender name
- subject and preview text
- the body text, or the first lines of it
Plus, per program: the signup time and the offer the signup form showed. For the user's own results without a connection, ask for the welcome or onboarding report for the last 90 days (recipients, click rate, orders or conversions per email) and the campaign report for the same 90 days.
How to run the queries
With the InsightfulPipe MCP connected:
- Call
query_contextswithrequest="accounts"forklaviyoormailchimp. Noteworkspace_id,brand_idand the account. If there are several, ask which one is the user's own. - Call
query_contextswithrequest="actions_details"for the actions below and follow the body shapes it returns.
Every read goes through query_data. Rules found on a live account:
- An empty answer is not an error. An account with no flows or campaigns answers
successwith an empty list. Say "no history" for that part. - Klaviyo rates are fractions (0.0125 is 1.25%).
- Never fire calls in parallel. On a 429, wait the
retry_afterseconds and retry once. - If a call fails, mark that part unknown, name the call, and never fill the gap with a guess.
Your own program: Klaviyo
Which automations exist:
{"action": "get_flows", "fields[flow]": "name,status,trigger_type", "auto_paginate": true}Welcome and other flow results per email, last 90 days:
{"action": "get_flow_report", "body": {"data": {"type": "flow-values-report", "attributes": {"timeframe": {"key": "last_90_days"}, "filter": "equals(send_channel,\"email\")", "group_by": ["flow_id", "flow_message_id", "flow_name", "flow_message_name"], "statistics": ["recipients", "click_rate", "unsubscribe_rate", "conversions", "conversion_rate"]}}}}Campaigns sent, and their results for the same 90 days:
{"action": "get_campaigns", "filter": "and(equals(messages.channel,'email'),equals(status,'Sent'))", "fields[campaign]": "name,send_time", "sort": "-created_at", "auto_paginate": true}{"action": "get_campaign_report", "body": {"data": {"type": "campaign-values-report", "attributes": {"timeframe": {"key": "last_90_days"}, "group_by": ["campaign_id", "campaign_message_id", "send_channel"], "statistics": ["recipients", "click_rate", "unsubscribe_rate", "conversion_rate"]}}}}get_campaignsfails without the channel filter, and status values are Title Case.- The report actions count conversions on the account's
Placed Ordermetric unless you passconversion_metric_id;meta.report.conversion_metricnames the one used. - Flow delays are not in these actions. Your welcome timing comes from the seed inbox.
No seed inbox export? Read what your own seed profile received instead:
get_metrics(auto_paginate: true), and keep the id ofReceived Email.get_profileswith"filter": "equals(email,'<SEED_ADDRESS>')". Use only the user's own test address, never a customer's.get_eventswith"filter": "and(equals(metric_id,\"<RECEIVED_EMAIL_ID>\"),equals(profile_id,\"<PROFILE_ID>\"))","sort": "datetime","auto_paginate": true.
- Don't pass
fields[event]withprofile_id; the call fails (allowed fields aredatetime,event_properties,id,timestamp,uuid). An unknown profile id returns "does not exist". - Each event gives the time, and its
event_propertiescarry the subject (Klaviyo names itSubject; check the first event's keys). Preview text and body are not there, so offers inside the body need the inbox export. Say so in "Not captured".
Your own program: Mailchimp (untested until a Mailchimp account is connected)
list_automations, thenlist_automation_emailswith eachworkflow_id: each email's delay and subject.list_campaignswithstatussentandsince_send_time90 days back:send_time,settings.subject_line,settings.preview_text,recipients.recipient_count.list_reportswith the samesince_send_time:emails_sent,clicks.click_rate,unsubscribed.- Customer Journeys built in Mailchimp's newer editor may not appear in
list_automations. Then the seed inbox is the only timing source.
The rivals' public signals
Signup offer on the page. The site crawler's text checkers return nothing on many storefronts (bot walls, popups drawn by scripts), so take a picture instead:
{"platform": "screenshot", "action": "capture", "url": "https://www.rival.example", "include_desktop": false, "include_mobile": true, "modes": ["mobile"]}It returns data.captures.mobile.public_url, a full-page image. Read the signup offer from it. The capture can render in another country's currency and may not show a popup; if no offer is visible, use what the user saw when they signed up.
Signup offer in paid ads (optional). ads-libraries:
facebook_search_companieswithquery(the rival's name) andcountryUS, to get thepage_id. Pick the verified page that matches the site.facebook_company_adswithpage_id,country,max_ads30 andtrimtrue. Rows are underdata.results;start_dateis in Unix seconds. Catalog ads have emptybody_text, and the call can return more rows thanmax_ads.- Count the active ads whose text offers something on the first order. A rival paying to advertise its signup offer is telling you the offer earns its keep.
The measures
Count every program the same way. Day numbers are calendar days after the signup date in the window's time zone; the signup day is day 0.
| Measure | Definition |
| Minutes to first email | first received time minus the signup time |
| Emails in the first 14 days | every email received on days 0 to 13 |
| Regular emails a week | emails on days 14 to the window's last day that don't name the sale event, divided by the number of weeks in that span |
| Offer | the email offers N% off, $N off, free shipping, a free sample, a free gift, 2 for 1 or buy one get one, anywhere in the subject, preview or body |
| Type | promotional if it has an offer; otherwise product if it announces something new, back in stock, a new harvest or now available; otherwise content |
| Signup offer | the offer in the first email: a % off, a non-discount offer (such as a free sample), or none |
| Deepest % off | the highest % off in any email in the window |
| Climbing welcome offer | among days 0 to 13, the emails that carry a % off and mention a code or the first order: yes when a later one offers more than an earlier one |
| Subject patterns | median length in characters, and the share of subjects with a number, an offer, an urgency word (end, ends, ending, last chance, tonight, final hours, today only, hours left), a question mark, an emoji |
| Sale timing | for emails naming the sale event: how many days before the event the first one arrived, how many there were, the most in one day, the deepest offer, and whether one said "extended" after an earlier sale subject used an urgency word |
| Usual send | the most common weekday and the most common send time, sale emails left out |
The rival median is the median across rivals; the user's own program is never part of it.
Decisions
Adopt
Adopt only a change that costs no margin, adds no regular sends, and that at least 2 rivals share:
- Welcome speed. Your first email takes more than 60 minutes and at least 2 rivals send theirs within 10: send email 1 on signup.
- Sale lead time. Your first sale email arrives less than 2 days before the event and at least 2 rivals start 2 or more days ahead: announce the next sale to subscribers at least 2 days before.
Avoid
List a rival pattern under "avoid" when the inbox shows:
- A deceptive subject: starts with
Re:orFwd:with no earlier thread, or claims an order or account action that never happened. US CAN-SPAM forbids deceptive subject lines. - A deadline that moves: a sale said it was ending, then came back as extended.
- A discount above the user's ceiling, with the climbing welcome offer named when there is one.
Test candidates
| Gap | Becomes a candidate when | Metric | Unit and volume |
| Subject style | your median subject length is 10 or more characters away from the rival median | campaign click rate | one campaign recipient; half the average campaign recipients per arm per send |
| Welcome length | you send at least 2 fewer emails in the first 14 days than the rival median | welcome orders per new subscriber (welcome flow conversions ÷ welcome email 1 recipients) | one new subscriber; half the weekly new subscribers per arm |
| Signup offer depth | your signup % off is 5 or more points away from the rival median (a rival with no discount counts as 0) | welcome email 1 placed-order rate, then margin per new subscriber | one new subscriber; half the weekly new subscribers per arm |
New subscribers a week = welcome email 1 recipients over the last 90 days ÷ (90 ÷ 7), rounded. Use click rate, not open rate: Apple Mail Privacy Protection opens almost every email it receives.
Frequency is not a test here. When your regular emails a week are 0.5 or more away from the rival median, list it as a handoff: a frequency change plays out per person over weeks, and it needs your own unsubscribe and complaint history.
Size each test: n per arm = ⌈(1.959964 + 0.841621)² × (p1(1 − p1) + p2(1 − p2)) ÷ (p2 − p1)²⌉, with p1 the baseline from your own data and p2 = p1 × (1 + the smallest lift). That is 5% significance, two-sided, at 80% power. Time to read = n ÷ your volume per arm, rounded up to whole sends or weeks. A test that needs more than 12 weeks is marked slow; say what lift it could read in 12 weeks instead.
Pick three. Rank candidates by how many rivals sit on the other side of your value, then by the units affected each week. The top three are the tests; the rest are "later".
The report
- Summary: the window, the emails read per program, and the two biggest gaps.
- Side by side: one row per measure, a column per program, and the rival median.
- Rival profiles: per rival, its signup offer, what the signup page said, how many active ads push the signup offer, its usual send, its sale timing, and a two-line read of its program.
- Your results: live and draft flows, new subscribers a week, welcome and campaign click and order rates.
- Adopt, avoid, three tests and handoffs, each with the numbers behind it.
- Not captured: what the inboxes couldn't see, such as cart flows that were never triggered and every rival's own results.
Rival patterns show what rivals do, not that it works for them. Say so once, and let the tests decide.
What this skill changes
Nothing. It reads, measures and recommends. It never edits a flow, a campaign or a signup form, and never sends or schedules an email.
Rules
- Never sign up, subscribe or create an inbox for the user, and never use a real person's details for research.
- Quote rival subject lines as evidence; never republish a rival's email body or images.
- Count every program with the same definitions and the same window.
- Every number in the report comes from the inboxes or from a call this skill made.
- No em or en dashes in the report.
Go deeper
- klaviyo-flow-auditor, if installed: audit your own flows end to end.
- email-sequence-builder, if installed: write the extra welcome emails a test calls for.
- email-campaign-calendar, if installed: set a send frequency from your own fatigue history.
- competitor-swot-analyzer and competitor-ad-research, if installed: the rest of each rival's marketing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

