Skip to content

ericrisco/rsc-harness / skills/cold-outreach

cold-outreach

Verified

Use when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits, the compliant opt-out footer. NOT SPF/DKIM/DMARC setup (that is email-deliverability), NOT sourcing the list (that is lead-gen), NOT life after a reply (that is sales-pipeline).

FileKindSize
SKILL.mdskill md16.1 KB
evals/README.mdmarkdown812 B
evals/cases.yamlconfig4.2 KB
references/compliance-footer.mdmarkdown3.4 KB
references/hook-derivation.mdmarkdown5.6 KB
references/templates.mdmarkdown3.0 KB
scripts/verify.shexecutablescript7.3 KB

references/hook-derivation.md

View on GitHub
# Hook derivation — worked OBSERVE → INFER → BRIDGE → PROVE chains

The four-line bridge (SKILL.md → "Deriving the hook") is the method. This file shows it executed across industries so you can pattern-match the *shape* of a good INFER line — the one step that separates a one-to-one email from a mail-merge wearing a name tag.

Read these for the INFER line specifically. Notice that in every good example the inference is something the recipient privately knows but didn't expect a stranger to. That recognition — not flattery, not a value prop — is what earns the reply.

## The test every chain must pass

After drafting the INFER line, ask: **"Would this sentence be FALSE for a competitor in the same situation?"**
- If it's true of everyone in the industry → it's a platitude. Go back, pick a sharper OBSERVE fact.
- If it's true only because of *this* specific signal → it's a hook. Ship it.

---

## 1. DevOps / infra tooling

- **OBSERVE:** 3 SRE roles open on their careers page for the full quarter.
- **INFER:** unfilled for a quarter means the current rotation is thin and absorbing the pages — recruiting isn't keeping up with on-call load.
- **BRIDGE:** we reduce page volume so a short-staffed rotation survives without the missing hires.
- **PROVE:** ~40% fewer alerts for two infra teams your size, month one.
- *Why it passes:* a competitor with a fully staffed team wouldn't feel this. The pain is specific to the unfilled-reqs signal.

## 2. B2B SaaS selling to RevOps

- **OBSERVE:** they just announced a Series B and a new VP of Sales on LinkedIn.
- **INFER:** post-B2 + new sales leader means the number tripled and the existing pipeline reporting won't survive the new board's scrutiny.
- **BRIDGE:** we make pipeline forecasts the new VP can defend in week one, not month three.
- **PROVE:** [named comparable] cut forecast variance from 30% to under 10% in a quarter.
- *Why it passes:* a flat company with a tenured VP doesn't have the "defend the number to a new board" pain. The funding + hire combination creates it.

## 3. E-commerce / DTC brand

- **OBSERVE:** their site runs a specific subscription app you can see in the page source / their checkout flow.
- **INFER:** that stack has a known involuntary-churn leak at card-expiry — they're losing ~5-8% of subscribers monthly to failed payments, not to cancellations.
- **BRIDGE:** we recover the failed-payment cohort before it churns.
- **PROVE:** [comparable DTC brand] recovered 6% of MRR that was bleeding to dunning failures.
- *Why it passes:* the inference is tied to a *detectable tech detail*, so it's true of them specifically, not "all DTC brands churn."

## 4. Professional services (agency → mid-market CMO)

- **OBSERVE:** they published a case study landing page but their blog hasn't shipped since Q3.
- **INFER:** the content engine stalled — likely the one person who owned it left or got pulled onto launches, and the pipeline that content fed is now thinning silently.
- **BRIDGE:** we keep the demand-gen content shipping without the headcount they just lost.
- **PROVE:** kept [comparable]'s organic pipeline flat through a content-team gap.
- *Why it passes:* the gap between "has case studies" and "blog stopped" is the specific, observable evidence of a stall — not a guess.

## 5. Fintech / regulated

- **OBSERVE:** a new compliance regulation with a known enforcement date hits their license type in 6 months.
- **INFER:** their compliance team is now triaging which controls to retrofit first, and the audit-trail gap is usually the one that surfaces late and panics legal.
- **BRIDGE:** we close the audit-trail gap so the deadline is a checkbox, not a fire drill.
- **PROVE:** [comparable] passed the equivalent audit with zero findings on first pass.
- *Why it passes:* the deadline is real and dated; the inference about *which* control bites last is the insider-grade detail that earns trust.

## 6. When the only signal is weak (the honest fallback)

Sometimes you genuinely cannot find a strong signal — the company is quiet, no hiring, no news. Do NOT fabricate. Two legitimate moves:

- **Use a category-level trigger honestly framed as a hypothesis, not a fake observation.** "Most [role]s at [company size] in [industry] are hitting [specific pain] right now — if that's you, [ask]. If not, ignore me." This is weaker than a real signal (expect reply rates at the low end of the band) but it's honest and still binary.
- **Kick it back to targeting.** If you keep landing on companies with no signal, the list is the problem, not the copy — that's a `lead-gen` ICP/timing gap. The fix is a better-segmented list with built-in triggers (recently funded, recently hiring, recently launched), not a cleverer sentence.

Never close the gap with an invented "I loved your recent post" — a signal the recipient knows is false destroys the contact on the first line.

## Anti-examples — INFER lines that FAIL the test

| Generic INFER (platitude) | Why it fails | Sharper version |
|---|---|---|
| "...so you probably want to grow revenue" | True of every company alive | Tie growth to the specific signal (new funding round → "defend a 3x number") |
| "...so you care about efficiency" | Vacuous; everyone claims this | Name the specific inefficiency the signal implies |
| "...AI is transforming your industry" | A trend, not a fact about *them* | Drop it; find a fact you can screenshot |
| "...I imagine scaling is a challenge" | Hedged guess, no observed basis | Only say it if a hiring/funding signal makes it observable |

The pattern: a failing INFER line is true regardless of the OBSERVE fact. A working one is true *because* of it.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall