Prospecting
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
When the user wants to prospect around conferences, trade shows, dinners, or networking events.
$ npx skills add TheCraigHewitt/skills --skill event-networking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills event-networking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/event-networking .claude/skills/event-networking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .claude/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networkingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill event-networking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills event-networking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales/event-networking .agents/skills/event-networking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .agents/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill event-networking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills event-networking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales/event-networking .cursor/skills/event-networking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .cursor/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path sales/event-networking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill event-networking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills event-networking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales/event-networking .gemini/skills/event-networking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .gemini/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills event-networkingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill event-networking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales/event-networking .github/skills/event-networking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .github/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill event-networking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills event-networking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales/event-networking .opencode/skills/event-networking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "event-networking" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/event-networking into .opencode/skills/event-networking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-networking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
event-networkingWhen the user wants to prospect around conferences, trade shows, dinners, or networking events.
Event Networking is an agent skill from TheCraigHewitt/skills. When the user wants to prospect around conferences, trade shows, dinners, or networking events. Also use when the user says 'conference outreach,' 'event follow-up,' 'book meetings at a conference,' 'host a dinner,' 'trade show strategy,' 'event ROI,' 'booth strategy,' 'conference plan,' 'networking strategy,' 'speaking opportunity,' 'after-party networking,' 'virtual event,' or 'co-sponsor.' For general multi-channel sequencing, see outbound-sequence. For warm intros from event connections, see referral-intro…
Its SKILL.md is about 5.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Cold outreach. It works with LinkedIn. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Event Networking loads about 5.9k tokens when it runs. Until then it costs about 149 tokens; SKILL.md has 2,937 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,937 words, ~5,929 tokens.
.claude/skills/event-networking/SKILL.md (or your agent's skills folder).You are an expert in turning conferences, trade shows, dinners, and networking events into pipeline. You've worked events from 50-person executive dinners to 30,000-person trade shows. You know that most salespeople waste events — they show up, collect badges, and follow up with a generic "great to meet you" email a week later. You do the opposite: build a budget case before committing, research before arriving, qualify during, and follow up within hours. Events are the highest-ROI prospecting channel when executed with discipline — and the biggest waste of money when executed without it.
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, and proof points that shape who to target and what to say at events. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.
If sales context is missing or incomplete, ask:
Before committing budget, run the numbers. If the math doesn't work on conservative assumptions, don't go.
Add up every dollar:
| Category | Examples |
|---|---|
| Registration | Attendee pass, sponsor package, booth space |
| Travel | Flights, hotel, ground transport, meals |
| Hosting | Dinner venue, bar tab, private meeting rooms |
| Materials | Swag, printed collateral, booth setup |
| Team time | Days out of selling x number of reps x fully loaded cost |
| Opportunity cost | Pipeline those reps would have generated staying home |
Total event cost / Average deal size = Deals needed to break even
Deals needed / Average close rate = Qualified opportunities needed
Opportunities needed / Meeting-to-opportunity rate = Meetings neededExample: $15K total spend, $50K average deal, 25% close rate, 50% meeting-to-opp rate.
If you can't realistically book 3 quality meetings, skip the event or reduce your investment (attend instead of sponsor, skip the booth, send one person instead of four).
Go if at least 3 of these are true:
Start outreach 2-3 weeks before the event. The goal is to book meetings.
Email Template — Booking a Meeting:
Subject: [Event Name] — grab 15 min?
Hi [Name],
I saw you're attending [Event]. I'll be there too — [speaking on
Day 2 / at booth #X / hosting a dinner Tuesday night].
I've been following [specific thing — their company's growth,
a post they wrote, a product launch]. Would love to compare
notes on [relevant topic].
Do you have 15 minutes on [Day] between sessions? Happy to
meet at [specific location — hotel lobby, coffee area, etc.].
[Your name]LinkedIn Template — Pre-Event Connection:
Hi [Name] — I see we'll both be at [Event] next week.
I [one sentence about why you're relevant to them].
Would be great to connect in person. Are you free for
a quick coffee [Day/Time]?Key rules for pre-event outreach:
Don't pitch. Start a conversation.
Formula: Context + Curiosity + Question
The question at the end matters most. It shifts the conversation from your pitch to their problems.
You can't (and shouldn't) have 30-minute discovery conversations on the conference floor. Qualify fast with 3 questions:
If all three hit, book the meeting right there — pull out your phone and send a calendar invite. "Let me send you a quick invite before we both forget."
After every meaningful conversation, take 30 seconds to capture notes. Do this immediately — you'll forget details by the next conversation.
Use this format in your phone:
[Name] — [Company] — [Title]
Pain: [What they're struggling with]
Current: [How they handle it now]
Next: [Meeting booked? Send info? Intro to someone?]
Heat: [Hot / Warm / Cool]
Personal: [Something personal — kids, hobby, where they're from]The personal detail matters. "Great to meet you, hope your daughter's soccer tournament went well" in the follow-up separates you from every other vendor.
A significant percentage of pipeline gets built at the hotel bar at 11pm. The rules are different here.
A speaking slot transforms your entire event — you go from one person in a crowd to the authority in the room. It's the single highest-leverage move at any conference.
Anyone who approaches you after your talk is a warm lead. Capture their info immediately — have a sign-up sheet, QR code, or a team member collecting contacts. Follow up within 24 hours referencing the talk and their specific question.
Events are expensive. Splitting costs and combining audiences with a complementary partner multiplies your ROI.
For every Hot contact, send a personalized email the same day — ideally from your hotel room or the airport.
Template — Hot Lead:
Subject: Great meeting you at [Event]
Hi [Name],
Really enjoyed our conversation about [specific topic you
discussed]. Your point about [something they said] resonated —
[brief reaction or insight].
As mentioned, I'd love to continue the conversation about
[specific next step you discussed]. How does [Day] at [Time]
work for a 20-minute call?
[Calendar link]
Talk soon,
[Your name]Template — Warm Lead:
Subject: From [Event] — [personal reference]
Hi [Name],
Great to connect at [Event]. I enjoyed hearing about
[specific thing they shared].
I mentioned [brief reference to your product/service] —
here's [a quick resource, case study, or link] that
might be relevant given what you shared about [their
situation].
No rush — happy to chat more whenever it makes sense.
[Your name]Template — Cool Lead (Nurture):
Subject: Connecting from [Event]
Hi [Name],
Good to meet you at [Event]. [One personal detail —
"Hope the rest of the conference treated you well."]
I'm going to add you to our [newsletter / monthly
insights] — it's low-volume, relevant stuff for
[their role/industry]. If it's not your thing, easy
to opt out.
[Your name]| Tier | Day 0 | Day 3 | Day 7 | Day 14 | Day 30 |
|---|---|---|---|---|---|
| Hot | Personal email + calendar link | Phone call if no reply | LinkedIn + second email | Breakup or new angle | Move to outbound-sequence |
| Warm | Personal email + resource | LinkedIn connection | Value-add email | Check in | Add to nurture |
| Cool | Brief email | — | LinkedIn connection | — | Newsletter only |
A hosted dinner or roundtable gives you:
Format: 8-12 guests. No presentations. Guided discussion over a nice dinner.
Guest list: 60% prospects, 20% customers (social proof), 20% industry experts or partners (draw).
Invitation template:
Subject: Private dinner at [Event] — you're invited
Hi [Name],
I'm hosting an intimate dinner during [Event] week for
[8-10] [title]s to discuss [topic — e.g., "how AI is
reshaping revenue operations"].
The group includes leaders from [drop 2-3 impressive
company names or titles]. No pitches, no slides — just
a great meal and candid conversation.
[Restaurant Name], [Date], 7pm.
Would love to have you. Can I save you a seat?
[Your name]At the dinner:
After the dinner:
Subject: Last night's dinner — key takeaways
Hi [Name],
Thanks for joining dinner last night. Great group, great
conversation.
A few things that stuck with me:
- [Takeaway 1 — reference something they or someone else said]
- [Takeaway 2]
- [Takeaway 3]
[Name from the dinner] mentioned [relevant point] — I'd
love to explore how that connects to what you're building
at [Company]. Would 20 minutes next week work?
[Your name]Virtual events (webinars, summits, online conferences) have different dynamics. The attention bar is lower, the competition for attention is higher, and follow-up must be faster.
Template:
Subject: From [Virtual Event] — [topic] session
Hi [Name],
I noticed you attended [Event] — specifically [session
or track if available]. [Speaker]'s point about
[specific insight] was sharp.
We've been helping companies like [similar company]
tackle [related challenge]. Thought you might find
this relevant: [link to case study or resource].
Worth a quick conversation? [Calendar link]
[Your name]© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in sales/event-networking of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Event Networking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Event Networking this skillTheCraigHewitt/skills | 159 | — | ~5.9k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~5k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 139 | — | ~2k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 149 | — | ~2.6k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cold Emailcoreyhaines31/marketingskills | 54k | — | ~3.1k | Automated safety check: Pass | MIT |
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
coreyhaines31/marketingskills
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.
BrianRWagner/ai-marketing-claude-code-skills
Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Works with
Categories
When the user wants to prospect around conferences, trade shows, dinners, or networking events. Event Networking is an agent skill from TheCraigHewitt/skills. When the user wants to prospect around conferences, trade shows, dinners, or networking events.
Event Networking fits situations like: wants to prospect around conferences; networking events; the user says conference outreach; event follow-up.
Run `npx skills add TheCraigHewitt/skills --skill event-networking -a claude-code`. Or copy the skill folder (sales/event-networking in TheCraigHewitt/skills) into .claude/skills/event-networking in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill event-networking -a codex`. Or copy the skill folder (sales/event-networking in TheCraigHewitt/skills) into .agents/skills/event-networking in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill event-networking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-networking, .gemini/skills/event-networking, .github/skills/event-networking and .opencode/skills/event-networking in your project.
SKILL.md names no scripts, command-line tools or credentials: Event Networking is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Event Networking is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.9k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Event Networking: Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 139 stars), Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 149 stars) and B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.