luckiest-co 1.0.38 → 1.0.40

package/skills/luckiest-cold-email/CHANGELOG.md

@@ -1,24 +0,0 @@
-# Changelog — luckiest-cold-email
-
-## 1.1.0 — 2026-07-06
-Skill updater pass: analytics integration.
-
-### Analytics (report_usage)
-- Updated `report_usage` call to `skill_version: "1.1.0"` and `check_updates`
-  `installedSemver: "1.1.0"`. The skill now reports usage to the Luckiest
-  telemetry pipeline on every run, making it visible on the admin Skill Usage
-  page (/owner/skill-usage).
-
-## 1.0.0 — 2026-07-01
-Rebranded from cold-email (marketingskills, MIT).
-
-### Improve pass (/refract)
-- Added a "Handling the Reply" section — objection/response guidance for "not interested," "send info," "who are you," "bad timing," and positive signals. The source skill stopped at getting the reply.
-- Added a "Deliverability" section — plain-text sending, link minimization, spam-trigger phrasing, and domain warmup. Great copy that lands in spam gets zero replies.
-- Added a "Compliance" section — CAN-SPAM and GDPR/PECR guardrails for outbound (identify yourself, physical address, lawful basis, honor opt-outs).
-
-### Network hook
-- One OFFER-only "Share with your tribe" section. Never auto-posts, never touches credentials; offers to share a finished draft/playbook with the Luckiest tribe and stops on decline.
-
-### Trend pass (/newsjack + /luckiest-trends)
-- No actionable signal. The luckiest-trends engine requires an interactive first-run setup (browser-cookie extraction and tool installs) that is unavailable in this non-interactive session, and its config store is out of scope to probe. No trend data was fabricated.

package/skills/luckiest-cold-email/SKILL.md

@@ -1,213 +0,0 @@
----
-name: luckiest-cold-email
-description: Writes B2B cold emails and follow-up sequences that get replies, and helps land them in the inbox and stay compliant. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, multi-touch follow-up sequences, reply handling, deliverability, and outbound compliance. For warm/lifecycle email sequences, see luckiest-emails. For sales collateral beyond emails, see luckiest-sales-enablement.
-license: See ATTRIBUTION.md
-metadata:
-  version: "1.1.0"
-  listing_id: luckiest-cold-email
-  author: luckiest
----
-
-# Cold Email Writing
-
-The assistant acts as an expert cold email writer. The goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
-
-## Staying current
-
-On activation, call the Luckiest MCP check_updates tool with { listingId: "0a9558ab-50e1-44fd-bf5a-63661542c9c2", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
-
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-cold-email", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
-
-## Before Writing
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Understand the situation (ask if not provided):
-
-1. **Who are you writing to?** — Role, company, why them specifically
-2. **What do you want?** — The outcome (meeting, reply, intro, demo)
-3. **What's the value?** — The specific problem you solve for people like them
-4. **What's your proof?** — A result, case study, or credibility signal
-5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes
-
-Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
-
----
-
-## Writing Principles
-
-### Write like a peer, not a vendor
-
-The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
-
-### Every sentence must earn its place
-
-Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
-
-### Personalization must connect to the problem
-
-If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
-
-See [personalization.md](references/personalization.md) for the 4-level system and research signals.
-
-### Lead with their world, not yours
-
-The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
-
-### One ask, low friction
-
-Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
-
----
-
-## Voice & Tone
-
-**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
-
-**Calibrate to the audience:**
-
-- C-suite: ultra-brief, peer-level, understated
-- Mid-level: more specific value, slightly more detail
-- Technical: precise, no fluff, respect their intelligence
-
-**What it should NOT sound like:**
-
-- A template with fields swapped in
-- A pitch deck compressed into paragraph form
-- A LinkedIn DM from someone you've never met
-- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
-
----
-
-## Structure
-
-There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
-
-**Common shapes that work:**
-
-- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
-- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
-- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
-- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
-
-For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md).
-
----
-
-## Subject Lines
-
-Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
-
-- 2-4 words, lowercase, no punctuation tricks
-- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
-- No product pitches, no urgency, no emojis, no prospect's first name
-
-See [subject-lines.md](references/subject-lines.md) for the full data.
-
----
-
-## Follow-Up Sequences
-
-Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
-
-- 3-5 total emails, increasing gaps between them
-- Each email should stand alone (they may not have read the previous ones)
-- The breakup email is your last touch — honor it
-
-See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates.
-
----
-
-## Handling the Reply
-
-The highest-leverage moment is the reply, and most outreach guidance stops before it. When the user has a response to work with, help them keep it moving without breaking the peer tone:
-
-- **"Not interested"** — Don't argue. Acknowledge, leave one narrow door open, exit gracefully. One short line beats a rebuttal.
-- **"Send me more info"** — Often a soft no. Answer the underlying question in two sentences and propose the smallest next step, rather than dumping a deck.
-- **"Who are you / how did you get this?"** — Answer plainly and briefly, then reconnect to the reason you reached out. Defensiveness reads as spam.
-- **"Not now / bad timing"** — Agree, confirm the specific later moment, and stop. Set a reminder rather than pushing.
-- **Any positive signal** — Match their energy, make the next step one click, and get out of the way.
-
-Keep replies as short as the first touch. The goal of each reply is the next reply, not to close in the thread.
-
----
-
-## Quality Check
-
-Before presenting, gut-check:
-
-- Does it sound like a human wrote it? (Read it aloud)
-- Would YOU reply to this if you received it?
-- Does every sentence serve the reader, not the sender?
-- Is the personalization connected to the problem?
-- Is there one clear, low-friction ask?
-
----
-
-## Deliverability
-
-A great email that lands in spam gets zero replies. Copy craft and inbox placement are two different problems — flag placement basics when they matter:
-
-- **Send plain text.** No HTML templates, tracking-heavy signatures, or embedded images in cold outreach. Plain text looks personal and lands better.
-- **Minimize links.** Zero or one link. Multiple links, link shorteners, and image-only emails trip spam filters.
-- **Watch spam-trigger phrasing.** "Free," "guarantee," "act now," ALL CAPS, and excessive punctuation hurt placement — the same salesy language the voice principles already reject.
-- **Warm the sending domain.** Brand-new domains and sudden volume spikes get filtered. Ramp gradually and keep complaint rates low (Google's threshold is 0.1%).
-
-Deliverability is infrastructure, not copy — if a user reports "everything goes to spam," point them at domain authentication (SPF/DKIM/DMARC) and warmup, not another rewrite.
-
----
-
-## Compliance
-
-Outbound email is regulated. Keep the user on the right side of it without turning the email into legalese:
-
-- **CAN-SPAM (US):** identify who you are, include a real physical mailing address, and honor opt-out requests promptly. No deceptive subject lines or "From" fields.
-- **GDPR / PECR (EU/UK):** cold B2B outreach needs a lawful basis (usually legitimate interest), must be relevant to the recipient's role, and must offer an easy opt-out.
-- Never fabricate a prior relationship, use fake "Re:" / "Fwd:" subjects, or hide the sender's identity.
-
-If a user is sending at scale into regulated regions, note that this is a legal question and suggest they confirm their approach with counsel.
-
----
-
-## What to Avoid
-
-- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
-- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
-- Feature dumps — one proof point beats ten features
-- HTML, images, or multiple links
-- Fake "Re:" or "Fwd:" subject lines
-- Identical templates with only {{FirstName}} swapped
-- Asking for 30-minute calls in first touch
-- "Just checking in" follow-ups
-
----
-
-## Data & Benchmarks
-
-The references contain performance data if you need to make informed choices:
-
-- [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes
-- [personalization.md](references/personalization.md) — 4-level personalization system, research signals
-- [subject-lines.md](references/subject-lines.md) — Subject line data and optimization
-- [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails
-- [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples
-
-Use this data to inform your writing — not as a checklist to satisfy.
-
----
-
-## Share with your tribe
-
-After delivering a strong email or sequence, the assistant may OFFER (never auto-send, never post anything, never touch credentials): "Want me to share this cold-email playbook with your Luckiest tribe? Anyone who asked for help writing outreach to a similar audience would see what worked here." If the user accepts, hand off the finished draft to the tribe-share flow. If they decline, stop. Never share drafts that name specific private prospects without an explicit ask.
-
----
-
-## Related Skills
-
-- **luckiest-prospecting**: For building and qualifying the prospect list that this skill writes outreach against — the natural upstream step before luckiest-cold-email
-- **luckiest-copywriting**: For landing pages and web copy
-- **luckiest-emails**: For lifecycle/nurture email sequences (not cold outreach)
-- **luckiest-social**: For LinkedIn and social posts
-- **luckiest-product-marketing**: For establishing foundational positioning
-- **luckiest-revops**: For lead scoring, routing, and pipeline management

package/skills/luckiest-cold-email/references/follow-up-sequences.md

@@ -1,81 +0,0 @@
-# Follow-Up Sequences
-
-55% of replies come from follow-ups, not the initial email. Yet 48% of salespeople never follow up even once.
-
-## How Many: 3–5 Total Emails
-
-- Highest single-email reply rate: **8.4%** (Belkins).
-- 4–7 email campaigns achieve **27% reply rates** vs 9% for 1–3 emails (Woodpecker, 20M emails).
-- By 4th follow-up, response rates drop **55%** and spam complaints **triple**.
-- Resolution: longer sequences catch different timing windows. Cap at 4 follow-ups (5 total emails). Each must add genuinely new value.
-
-## Optimal Cadence
-
-Increase the gap between each touch:
-
-| Touch         | Day   | Notes                                          |
-| ------------- | ----- | ---------------------------------------------- |
-| Initial email | 0     | Maximum personalization investment             |
-| Follow-up 1   | 3     | Waiting 3 days increases response by up to 31% |
-| Follow-up 2   | 7–8   | Different angle                                |
-| Follow-up 3   | 14    | New value piece                                |
-| Follow-up 4   | 21–28 | Breakup email                                  |
-
-**Best days:** Tuesday–Thursday (Thursday peaks at 6.87% reply rate).
-**Best times:** 9–11 AM or 1–3 PM in prospect's local time.
-**Avoid:** Monday mornings (inbox overload), Friday afternoons (checked out).
-
-## Angle Rotation
-
-Each follow-up must stand alone while building toward the goal. Never just "bump this up."
-
-| Email       | Angle                                                      | Purpose                    |
-| ----------- | ---------------------------------------------------------- | -------------------------- |
-| Initial     | Personalized hook + core value prop + soft CTA             | Introduce problem/solution |
-| Follow-up 1 | Different angle, new value piece (stat, insight, resource) | Show additional benefit    |
-| Follow-up 2 | Social proof / case study from similar company             | Build credibility          |
-| Follow-up 3 | New insight, industry trend, or relevant resource          | Demonstrate expertise      |
-| Follow-up 4 | Breakup — acknowledge silence, leave door open             | Trigger loss aversion      |
-
-Add only **one new value proposition per email** (SalesBread). This naturally forces different angles.
-
-## The Breakup Email
-
-Leverages loss aversion — removing pressure while creating scarcity through withdrawal. Close.com reports **10–15% response rates** from breakup emails with cold prospects.
-
-**Structure:**
-
-1. Acknowledge you've reached out multiple times
-2. Validate their potential lack of interest
-3. State this is your final email for now
-4. Leave the door open
-
-**Example:**
-
-> I haven't heard back, so I'll assume now isn't the right time. Before I close the loop: [1-sentence insight or resource]. If that changes things, feel free to reply. Otherwise, no hard feelings — good luck with [their goal].
-
-**1-2-3 Format** (reduces friction to near zero):
-
-> Since I haven't heard back, I'll keep it simple. Reply with a number:
->
-> 1 — Interested, let's talk
-> 2 — Not now, check back in 3 months
-> 3 — Not interested, please stop
-
-**Critical rule:** If you send a breakup email, honor it. Do not contact the prospect again.
-
-## Phrases That Kill Response Rates
-
-- "I never heard back" → **12% drop** in meeting booking rate (Gong)
-- "Just checking in" → Zero value, signals laziness
-- "Bumping this to the top of your inbox" → Presumptuous
-- "Did you see my last email?" → Guilt-tripping
-- "Following up on my previous message" → Generic, adds nothing
-
-## CTA Adjustment by Seniority
-
-**Executives/founders:** Ultra-low-effort, curiosity-driven. "Curious?" or "Worth 2 min?"
-
-**Mid-level managers:** More specific value. "Want me to walk through how [Company] saved 15 hours/week?"
-
-Higher in the org chart = less friction you can ask for.

package/skills/luckiest-cold-email/references/frameworks.md

@@ -1,90 +0,0 @@
-# Cold Email Copywriting Frameworks
-
-Frameworks beat templates — they teach thinking patterns, not copy-paste shortcuts.
-
-## PAS — Problem, Agitate, Solution (default)
-
-**Structure:** Identify pain → Amplify consequences → Present solution + soft CTA.
-**Best for:** Problem-aware but not solution-aware prospects. The workhorse framework.
-
-> Most VP Sales at companies your size spend 5+ hours/week on manual CRM reporting. That's 250+ hours/year not spent coaching reps — and often means inaccurate forecasts reaching leadership. We built a tool that auto-generates CRM reports in real time. Teams like Datadog reduced reporting time by 80%. Would it make sense to see how?
-
-## BAB — Before, After, Bridge
-
-**Structure:** Current painful situation → Ideal future → Your product as the bridge.
-**Best for:** Transformation-driven offers with clear before/after. Emotional decision-makers.
-
-> Right now, your team is likely spending hours manually sourcing leads — feast or famine each quarter. Imagine qualified leads arriving daily on autopilot, reps spending 100% of their time selling. That's what our platform does. Companies like HubSpot saw a 40% pipeline increase within 90 days. Can I show you how?
-
-## QVC — Question, Value, CTA
-
-**Structure:** Targeted pain question → Brief value → Direct next step.
-**Best for:** C-suite prospects who prefer brevity. Qualify interest immediately.
-
-> Are your SDRs spending more time researching than selling? We help sales teams automate prospect research so reps focus on conversations. Clients see 3x more meetings per rep per week. Worth a 10-minute demo?
-
-## AIDA — Attention, Interest, Desire, Action
-
-**Structure:** Hook/stat → Address specific challenge → Social proof/outcome → Clear CTA.
-**Best for:** Data-driven prospects, high-ticket pitches with strong stats.
-
-> Companies in pharma lose 30% of leads due to manual outreach. Given {{Company}}'s growth this quarter, pipeline velocity is likely top of mind. Customers like Pfizer use our platform to automate lead qualification — cutting time-to-contact by 60%. Worth a 15-minute call?
-
-## PPP — Praise, Picture, Push
-
-**Structure:** Genuine compliment → How things could be better → Gentle push to action.
-**Best for:** Senior prospects who respond to relationship-building. Requires genuine trigger.
-
-> Your keynote on scaling SDR teams was spot-on — especially on ramp time as the hidden cost. What if you could cut that in half? Our in-inbox coach helps new reps write effective emails from day one with real-time scoring. Open to a quick chat about how this could support your growth?
-
-## Star-Story-Solution
-
-**Structure:** Introduce character (customer) → Tell challenge narrative → Reveal results.
-**Best for:** Strong customer success stories. Humanizes the pitch.
-
-> Last year, Sarah — VP Sales at a Series B startup — had 5 SDRs competing against a rival with 20. Her team was getting crushed on volume. They adopted our AI prospecting tool and sent hyper-personalized emails at 3x pace without losing quality. Within 90 days, they booked more meetings than their competitor's entire team. Happy to share how this could work for {{Company}}.
-
-## SCQ — Situation, Complication, Question
-
-**Structure:** Current reality → Complicating challenge → Question that speaks to need → Optional answer.
-**Best for:** Consultative selling. Mirrors how professionals present to leadership.
-
-> Your team doubled this year. That usually means onboarding is eating into selling time. How are you handling ramp for new hires?
-
-## ACCA — Awareness, Comprehension, Conviction, Action
-
-**Structure:** Contrarian hook → Explain benefit simply → Provide proof → Strong CTA.
-**Best for:** Analytical buyers who need evidence (engineers, CFOs, ops leaders).
-
-> Most sales teams measure rep activity. The top 5% measure rep efficiency instead. When Acme switched, they booked 40% more meetings with fewer emails. Worth seeing how?
-
-## 3C's (Alex Berman)
-
-**Structure:** Compliment → Case Study → CTA.
-**Best for:** Agency/services cold outreach. Case study does the heavy lifting.
-
-> Big fan of [Company]. We just built an app for [Competitor] that does XYZ. I have a few more ideas. Interested?
-
-## Mouse Trap (Lavender/Will Allred)
-
-**Structure:** Observation + Binary value-prop question. 1–2 sentences total.
-**Best for:** Maximum brevity. Impulsive reply based on curiosity.
-
-> Looks like you're hiring reps. Would it be helpful to get a more granular look at how they're ramping on email?
-
-## Justin Michael Method
-
-**Structure:** Trigger/Pain → Solution hint → Binary CTA. 1–3 sentences, no intro.
-**Best for:** High-velocity SDR teams. Mobile-optimized. Deliberately polarizing.
-
-Spend max 1 minute on personalization. Use industry/persona-level signals. For top-tier prospects, quote their own words from interviews — they almost always respond.
-
-## Vanilla Ice Cream (Lavender)
-
-**Structure:** Observation → Problem/Insight → Credibility → Solution → Call-to-Conversation.
-**Best for:** Universal "base" framework that works everywhere. Five parts.
-
-## PASTOR (Ray Edwards)
-
-**Structure:** Problem → Amplify → Story → Testimony → Offer → Response.
-**Best for:** Longer-form or multi-email sequences. Consulting, education, complex B2B services. Each element can be developed across separate touches.

package/skills/luckiest-cold-email/references/personalization.md

@@ -1,79 +0,0 @@
-# Personalization at Scale
-
-Personalization drives **50–250% more replies** (Lavender). The key insight: **if your personalization has nothing to do with the problem you solve, it's just an attention hack** (Clay).
-
-## Four Levels of Personalization
-
-### Level 1 — Basic (merge tags)
-
-First name, company name, job title. Table stakes, no longer differentiating. ~5% lift.
-
-### Level 2 — Industry/segment
-
-Industry-specific pain points, trends, regulatory challenges. Scalable via micro-segmentation.
-
-> Most {{industry}} teams struggle with {{lead gen problem}}, which often leads to wasted effort.
-
-### Level 3 — Role-level
-
-Challenges specific to their role and seniority.
-
-> As Head of Sales, keeping pipeline steady is probably your biggest headache. Your RevOps team is small, so you're likely wearing multiple hats during scaling.
-
-### Level 4 — Individual (gold standard)
-
-Specific, timely observations about that person connected to the problem you solve.
-
-> Noticed you're hiring 3 SDRs — sounds like you're scaling outbound fast. Most teams hit follow-up fatigue during onboarding.
-
-## Research Signal Stack
-
-| Signal            | Where to find it                   | How to use it                                                                |
-| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
-| Recent funding    | Crunchbase, LinkedIn, press        | "Congrats on Series B — scaling teams fast usually creates X challenge"      |
-| Job postings      | LinkedIn Jobs, careers page        | "Noticed you're hiring 3 SDRs — sounds like you're scaling outbound"         |
-| Tech stack        | BuiltWith, Wappalyzer, HG Insights | "I see you're using HubSpot — most teams at your stage hit a ceiling with X" |
-| LinkedIn activity | Posts, comments, job changes       | "Really enjoyed your post about X"                                           |
-| Company news      | Google News, press releases        | "Congrats on acquiring X — integrating teams usually creates Y challenge"    |
-| Podcast/talks     | Google, YouTube, podcasts          | "Caught your talk at SaaStr on X — really insightful"                        |
-| Website changes   | Manual review                      | "Your new pricing page caught my eye — curious how it's converting"          |
-
-## The 3-Minute Personalization System
-
-From "30 Minutes to President's Club":
-
-**Step 1:** Build a research stack of top 10 buying signals — 5 company triggers, 5 person triggers. Stack-rank by relevance.
-
-**Step 2:** Build a 3x3 template: (1) personalization attached to a problem, (2) problem you solve, (3) one-sentence solution + low-friction CTA.
-
-**Step 3:** Create 5 "trigger templates" — pre-written personalization paragraphs for each trigger, with a smooth segue into the problem.
-
-The personalization must logically connect to the problem. This creates 5 reusable triggers with the rest of the email constant. A top SDR writes a personalized email in **under 3 minutes**.
-
-## The Four -Graphic Principles (Becc Holland)
-
-- **Demographic** — Age, profession, background
-- **Technographic** — Tech stack, tools used
-- **Firmographic** — Company size, funding, industry, growth stage
-- **Psychographic** — Values, passions, beliefs (highest-impact dimension)
-
-Tapping into what prospects are passionate about drives significantly higher response rates.
-
-## Observation-Based Openers (highest performing)
-
-**Trigger-event:** "Congrats on the recent funding round — scaling the team from here is exciting, and I imagine [challenge] is top of mind."
-
-**Observation:** "Your recent post about [topic] resonated — especially the part about [detail]. Got me thinking about how that applies to [challenge]."
-
-**Industry insight:** "Most [role titles] I talk to spend [X hours/week] on [problem] — curious if that matches your experience at [Company]."
-
-## What Feels Fake (avoid)
-
-- AI-generated emails with similar phrasing ("I hope this email finds you well")
-- Generic attention hacks disconnected from problem ("Cool that you went to UCLA!" → pitch)
-- Over-personalizing to creepiness
-- "I saw your LinkedIn profile and wanted to reach out" — signals mass automation
-
-## The "So What?" Test
-
-After writing any opening line, read from prospect's perspective: "So what? Why would I care?" If the answer is nothing, rewrite.