intro-email-generator
Skill0 starsChanged 2 months agoMITView on GitHub
Generate warm, high-signal introduction emails connecting two people, drafted directly into Gmail. Use this skill whenever the user wants to introduce two people over email, says things like "intro email for X and Y", "connect these two people", "make an intro between", "draft an intro email", "write an email introduction", "double opt-in intro", or provides two LinkedIn profile URLs and asks to connect them. Works for any context — sales and partnership intros, recruiting and candidate referrals, investor and founder intros, mentor matches, vendor referrals, community connections. This skill researches both parties, formats a structured introduction with their names, titles, company hyperlinks, company descriptions, and social/web links, then drafts the email via the connected Gmail tools (or outputs copy-paste text if no email tool is available). Trigger even if the user just pastes two LinkedIn URLs without explicit instructions. Do NOT use for a full pre-meeting research note on one person — use the professional-profile-brief skill. Do NOT use for summarizing where an existing relationship stands — use the relationship-status-summarizer skill.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- hirefrank/network-jobstheir own version, first seen Nov 1, 2026
- latour-ai/skillsedited, first seen Oct 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- latour-ai/skills★ 6985% same
Wrote their own version · 1
- hirefrank/network-jobs★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- audit-request-binderSkill
- business-one-pagerSkill
- call-notes-followupSkill
- company-first-passSkill
- conference-prep-plannerSkill
- contract-obligations-extractorSkill
- counterparty-diligenceSkill
- decision-memo-drafterSkill
- document-redline-diffSkill
- executive-briefingSkill
- expert-interview-synthesisSkill
- hundred-day-plan-drafterSkill
- inbox-triageSkill
- linkedin-post-generatorSkill
- marketing-claims-prescreenSkill
- market-map-builderSkill
- meeting-minutes-generatorSkill
- nda-reviewSkill
- payout-reconciliation-checkerSkill
- performance-attribution-narratorSkill
- periodic-report-synthesizerSkill
- podcast-episode-analyzerSkill
- presentation-transcript-extractorSkill
- private-company-tear-sheetSkill
- professional-profile-briefSkill
- project-folder-organizerSkill
- proposal-first-passSkill
- questionnaire-red-flag-scannerSkill
- questionnaire-response-drafterSkill
- red-team-premortemSkill
- relationship-status-summarizerSkill
- side-letter-term-extractorSkill
- skill-idea-generatorSkill
- stakeholder-update-generatorSkill
- teach-meSkill
- unit-economics-memoSkill
- watchlist-news-alertSkill
- weekly-recap-writerSkill
- workflow-to-ai-solverSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
If the reason for connecting is missing, ask for it once before proceeding.
- Distinctive: line 54
Do not guess URLs — only include links that are confirmed through search.
- Distinctive: line 92
Do NOT fabricate any URLs — if a Twitter or personal site is not found, omit the line entirely
- Distinctive: line 93
Keep the company description to one sentence, focused on what the company does (not fluffy adjectives)
- Distinctive: line 101
Use the connected Gmail tools (the create-draft tool) to create the draft.
- Distinctive: line 108
After successfully creating the draft, tell the user:
- Distinctive: line 111
Never send the email — the user adds recipients and sends.
- Distinctive: line 132
Always sign off as:
- Distinctive: line 138
No title or company tagline needed for intro emails — keep it personal.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Intro Email Generator
Generate polished, warm introduction emails connecting two people. Researches both parties, assembles structured profiles, and drafts directly into Gmail.
Inputs Required
The user must provide:
- LinkedIn URLs for both Person A and Person B (or enough identifying detail — full name plus company — to find them reliably)
- Reason for connecting — a sentence or phrase explaining why this intro is valuable
If the reason for connecting is missing, ask for it once before proceeding. Do not invent one.
Step 1: Research Both Parties
For each person, use web search to gather:
| Field | Source |
| Full name | LinkedIn profile |
| Title | LinkedIn profile |
| Company name | LinkedIn profile |
| Company URL | Company website (for hyperlinking) |
| Company description | 1-sentence summary of what the company does |
| Twitter/X handle | Search "[Name] Twitter" or "[Name] X profile" |
| Personal website/homepage | Search "[Name] personal site" or check LinkedIn bio |
Do not guess URLs — only include links that are confirmed through search. If two people share a name, confirm the match against company and title before using anything.
Step 2: Assemble the Email
Subject Line
Intro: [Person A First Name] <> [Person B First Name]
Body Structure
Hi [Person A First Name] and [Person B First Name],
[One-sentence greeting that states WHY you're making this connection — tie it to a shared goal, mutual benefit, or opportunity.]
[Person A Full Name]
• [Title] at [Company Name as hyperlink to company URL]
• [1-sentence company description]
LinkedIn: [LinkedIn URL]
[Twitter: Twitter URL — only if confirmed]
[Web: Personal site URL — only if confirmed]
[Person B Full Name]
• [Title] at [Company Name as hyperlink to company URL]
• [1-sentence company description]
LinkedIn: [LinkedIn URL]
[Twitter: Twitter URL — only if confirmed]
[Web: Personal site URL — only if confirmed]
I'll let you two take it from here!
[sign-off]Formatting Rules
- Company name in the bullet must be a clickable hyperlink (use an HTML
<a>tag when drafting via the Gmail tools, or a standard markdown link[Company](URL)when composing plain text) - LinkedIn, Twitter, and personal site links appear as labeled bare URLs on their own lines (e.g.,
LinkedIn: [URL]) — only include links that were confirmed through research - Do NOT fabricate any URLs — if a Twitter or personal site is not found, omit the line entirely
- Keep the company description to one sentence, focused on what the company does (not fluffy adjectives)
- The greeting sentence should be specific and warm — reference the actual reason for connecting, not a generic "I think you two should meet"
- Match the user's context: an intro between a hiring manager and a candidate reads differently from one between two founders or a client and a contractor. The structure stays the same; the greeting sentence carries the context.
Step 3: Draft in Gmail
Use the connected Gmail tools (the create-draft tool) to create the draft.
Gmail Draft Parameters
to: Leave blank (or ask the user if they want to pre-populate recipients)subject:Intro: [Person A First Name] <> [Person B First Name]body: Full email body as composed above
After successfully creating the draft, tell the user:
"Draft created in Gmail — subject: Intro: [A] <> [B]. You can open it, add recipients, and send when ready."
Never send the email — the user adds recipients and sends. Creating a draft is the end of this skill's job.
Edge Cases
| Situation | Handling |
| Twitter not found | Omit the Twitter line entirely |
| Personal site not found | Omit the Web line entirely |
| Company URL not found | Use company name as plain text, not a hyperlink |
| LinkedIn URL is a vanity URL (not full profile) | Use as-is; it's still a valid link |
| Person is between roles / independent | Use the title they give themselves (e.g., "Independent consultant"); omit the company bullet or link the personal site instead |
| User doesn't provide reason for connecting | Ask before drafting: "What's the reason you're connecting these two?" |
| User hasn't said whether both parties agreed to the intro | Draft anyway, but mention once that a quick opt-in check with each person is the norm for cold intros |
| Gmail draft fails or no email tool is connected | Output the full email as formatted text so the user can copy-paste manually |
Sign-off
Always sign off as:
All the best,
[Your Name]No title or company tagline needed for intro emails — keep it personal.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

