← ClaudeAtlas

cold-emaillisted

Write cold outreach emails asking a company to sponsor or partner on an event (hackathon, summit, conference, community program). Use when the user wants to pitch a sponsor, write a cold email to a company, contact DevRel/partnerships/marketing about an event, ask for credits or prizes, reach out about a Main Partner or Gold/Silver tier, follow up on an unanswered sponsor email, or produce a batch of personalized pitches for a prospect list. Triggers include "cold email", "sponsor", "sponsorship", "patrocinio", "partnership pitch", "reach out to a company about the hackathon", "email para conseguir sponsors".
shiarauzo/skills · ★ 1 · AI & Automation · score 72
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