cold-emaillisted
Install: claude install-skill shiarauzo/skills
# Sponsor Outreach
Write cold emails that get replies from DevRel, partnerships, and marketing leads.
The core insight: these emails do not sell a sponsorship. They hand the recipient a
ready-made way to hit a goal they already have (developer adoption, employer brand,
LatAm presence) and make the event the vehicle. Generic pitches get ignored; a pitch
that names what their specific users will build gets a reply.
## Workflow
Run these four steps in order. Do not skip step 2 — research is what separates a reply
from a template.
### Step 1 — Intake
Collect the event facts. Never invent a number, date, city, or partner name. If a
required field is missing, ask for it before drafting.
**Never invent the recipient's name.** A plausible-sounding placeholder is the one
fabrication that survives review, because it does not look fabricated. When the address
is a role inbox and no name is known, leave an obvious slot — `[NOMBRE]` — say so when
delivering, and name who can supply it.
**Required:**
- Event name, date, format (e.g. "12-hour in-person", "48-hour global")
- Cities or "global/remote"
- Headcount and how attendees are selected ("300 selected builders")
- Audience composition (product engineers, AI builders, founders, indie hackers, PMs, designers)
- Sender: first name + the organization they represent
- Recipient: first name + company + their role/team
**Required if it exists:**
- Deck URL — always prefer the per-prospect path (`/deck/acme`, `/deck/globex`). Ask for