Individual skill
pre-conference-outreach
Use this skill when you have a conference attendee list and the goal is meetings booked before or during the event, not generic warm-up. Every row is researched first, routed to the teammate whose lens matches the contact's real job, and staged as a tight 4-step sequence: a sub-250-character email that names the conference plus one verified angle, a blank connection request, a verbatim side-door offer (exec dinner or a hands-on session), and a short LinkedIn nudge. Scoring tier never skips anyone. Nothing auto-sends.
skills/jeremy-hurst/pre-conference-outreach/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 236
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 17,382 bytesreferences/setup-customization-checklist.mddoc · 3,456 bytes
Read excerpt
# Pre-conference outreach
## Template placeholders
Replace every `{{...}}` before enabling. See the setup checklist reference for the full setup list.
- `{{EVENT_NAME}}` - The conference as people say it in a DM (e.g. "GTM2026", "SaaStr")
- `{{EVENT_CITY}}` - Host city, used to pick "hitting the conf?" vs "Making the trip?"
- `{{EVENT_DATES}}` - Date range, used to pick "this week" vs "next week" at send time
- `{{EXEC_SIDE_EVENT}}` - Your executive side-door offer, as it reads in a sentence (e.g. "an exec dinner on Tuesday night")
- `{{PRACTITIONER_SIDE_EVENT}}` - Your hands-on side-door offer (e.g. "a skills hackathon during the conference", "a build session")
- `{{EXEC_SENDER}}` - Teammate with the authority lens: talks to whoever owns the problem and its budget
- `{{SALES_LEADER_SENDER}}` - Teammate with the seller-management lens: talks to people who manage sellers
- `{{PRACTITIONER_SENDER}}` - Teammate with the practitioner lens: talks to hands-on operators of the GTM stack