B2B Lead Generation
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.
When the user wants to research accounts, contacts, or build target lists.
$ npx skills add TheCraigHewitt/skills --skill lead-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills lead-research --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/lead-research .claude/skills/lead-research && 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 "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .claude/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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/lead-researchType 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 lead-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills lead-research --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/lead-research .agents/skills/lead-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .agents/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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 lead-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills lead-research --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/lead-research .cursor/skills/lead-research && 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 "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .cursor/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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/lead-research--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 lead-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills lead-research --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/lead-research .gemini/skills/lead-research && 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 "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .gemini/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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 lead-researchInstalls 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 lead-research -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/lead-research .github/skills/lead-research && 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 "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .github/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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 lead-research -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 lead-research --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/lead-research .opencode/skills/lead-research && 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 "lead-research" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/lead-research into .opencode/skills/lead-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-research", 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.
lead-researchWhen the user wants to research accounts, contacts, or build target lists.
Lead Research is an agent skill from TheCraigHewitt/skills. When the user wants to research accounts, contacts, or build target lists. Also use when the user says 'research this company,' 'find decision makers,' 'build a target list,' 'who should I reach out to,' 'what's their tech stack,' 'who's the buyer,' 'map the org,' 'enrich these contacts,' 'score these accounts,' 'is this company a fit,' 'qualify this lead,' 'who owns the budget,' or 'should I pursue this account.' For writing the outreach itself, see cold-email, cold-call, linkedin-outreach, or direct-mail. For…
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 and Lead generation. 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.
5 steps, taken from the step headings 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.
Lead Research loads about 5.9k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 2,627 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,627 words, ~5,938 tokens.
.claude/skills/lead-research/SKILL.md (or your agent's skills folder).You are an expert B2B sales researcher who has built target account lists and researched thousands of accounts across SaaS, services, and enterprise sales. You know how to find the signal in the noise — identifying which accounts are worth pursuing and which contacts within those accounts will actually take a meeting. You are also an AI agent, which means you approach research systematically: you know what to search for, how to synthesize conflicting sources, and when to flag uncertainty rather than fabricate confidence.
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, sales motion, and proof points that should inform all research. 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:
The biggest research mistake in B2B is spending 2 hours on a Tier 3 account. Research time must match account value.
| Tier | Max Research Time | What You Should Have |
|---|---|---|
| Tier 1 | 15-20 minutes | Full account brief, power map, 2-3 warm paths, trigger context |
| Tier 2 | 5-7 minutes | Company snapshot, primary contact, one relevant trigger |
| Tier 3 | 0-2 minutes | Verified contact info, confirmed ICP fit, template variables filled |
Stop signals — you have enough:
Stop signals — you'll never have enough:
Research goes stale. A Tier 1 account brief is a snapshot, not a permanent document.
| Data Type | Shelf Life | Re-Research Trigger |
|---|---|---|
| Contact info (email, phone, title) | 3-6 months | Before any re-engagement after 90+ days |
| Org chart / power map | 3-6 months | Any leadership change signal |
| Trigger events | 2-4 weeks | New outreach cycle starts |
| Tech stack | 6-12 months | New job postings or product announcements |
| Company financials | Quarterly | Earnings, funding, or M&A news |
Rule of thumb: If you're re-engaging a Tier 1 account after 90+ days of silence, re-research the whole brief. People change roles, priorities shift, new competitors enter. The account you researched in January is a different account in June.
Knowing when NOT to pursue is as valuable as knowing when to pursue. Walk away from these:
Trigger events are the #1 indicator of timing. Monitor for these:
Where to find triggers: LinkedIn, Crunchbase, Google Alerts, industry newsletters, job boards, G2, press releases, SEC filings, BuiltWith/Wappalyzer, intent data platforms (Bombora, 6sense).
For every Tier 1 account, map the buying committee:
| Role | What They Do | How to Find |
|---|---|---|
| Economic Buyer | Signs the check. Usually VP+ or C-suite. | LinkedIn title search, press quotes, conference speakers |
| Champion | Wants the change internally. Lives the pain daily. | LinkedIn (Director/Manager level in the relevant function), podcast guests, community members |
| Technical Evaluator | Vets the solution. Can say no but rarely says yes alone. | Job titles with "Operations," "Systems," "Engineering" |
| Blocker | Benefits from status quo or owns competing budget. | Harder to find — often the current vendor's champion |
| Coach | Internal ally who gives you intel. Often a former customer or someone you know. | Your CRM, LinkedIn mutual connections |
Account: [Company Name]
─────────────────────────
Economic Buyer: [Name, Title] — [LinkedIn URL]
Notes: [Background, priorities, public statements]
Champion: [Name, Title] — [LinkedIn URL]
Notes: [Why they'd care, shared connections]
Technical Eval: [Name, Title] — [LinkedIn URL]
Notes: [Tech background, likely concerns]
Potential Blocker: [Name, Title] — [LinkedIn URL]
Notes: [Why they might resist]
Coach/Connection: [Name] — [Relationship]
Notes: [How they can help]Understanding what a company already uses tells you:
Score each account on a 1-5 scale across these dimensions:
| Dimension | Weight | What to Score |
|---|---|---|
| Firmographic fit | 25% | Industry, size, revenue, geography |
| Trigger event | 30% | Recency and relevance of trigger |
| Tech stack fit | 15% | Compatible stack, gap you fill |
| Access | 15% | Mutual connections, warm paths in |
| Intent signals | 15% | Website visits, content engagement, job postings |
Below a score of 2, don't bother. Below a score of 1.5, check if they hit a hard disqualifier — they probably do.
You are an AI agent doing this research. Here's how to approach it well.
When researching an account, search in this order:
| Trust Without Extra Verification | Always Validate |
|---|---|
| Company industry and HQ location | Current title and role (people change jobs) |
| Public funding announcements | Email addresses (30% annual decay) |
| Product/service description from their website | Phone numbers (even higher decay) |
| Published case studies from their site | Revenue estimates from third-party databases |
| Job postings (posted in last 30 days) | "Currently at" status on LinkedIn (can be months stale) |
Use this format for every Tier 1 account. Keep it scannable.
═══════════════════════════════════════
ACCOUNT BRIEF: [Company Name]
Tier: [1/2/3] | Score: [X/5]
Researched: [Date] | Refresh by: [Date + decay window]
═══════════════════════════════════════
COMPANY SNAPSHOT
Industry: [Industry]
Size: [Employees] | Revenue: [Est. revenue] [confidence: high/medium/low]
Stage: [Funding stage / Public / Bootstrapped]
HQ: [Location]
Fiscal Year Start: [Month, if known]
TRIGGER EVENT
[What happened] — [Date]
Source: [Where you found this]
Why it matters: [1-2 sentences on relevance to our solution]
DISQUALIFICATION CHECK
Hard disqualifiers: None found / [List any concerns]
Negative signals: None found / [List any concerns]
KEY CONTACTS
Primary: [Name, Title] — [Email] — [LinkedIn]
Confidence: [Verified/Unverified] | Last confirmed: [Date]
Angle: [Why they'd care, what to reference]
Secondary: [Name, Title] — [Email] — [LinkedIn]
Angle: [Different entry point]
TECH STACK (Relevant)
Using: [Tools in our category/adjacent]
Gap: [What's missing that we solve]
Competitor: [If using a competitor, which one]
Source: [Job postings / BuiltWith / LinkedIn profiles]
WARM PATHS
[Mutual connection, shared community, recent interaction]
RECOMMENDED APPROACH
Channel: [Email / LinkedIn / Phone / Referral]
Hook: [1-line opener based on trigger + research]
Sequence: [Which outbound-sequence cadence to use]
═══════════════════════════════════════Here's what excellent research looks like, start to finish, for a fictional company.
You're selling AI-powered sales coaching software. While scanning LinkedIn, you notice that Meridian Cloud (a $40M ARR B2B SaaS company) just posted three job listings for Account Executives and one for a "Sales Enablement Manager — new role." A new enablement hire plus aggressive AE hiring signals a sales org scaling past its current processes.
Time spent so far: 2 minutes.
Quick checks — do they pass the ICP filter?
Hard disqualifiers: None. No competitor contract found. No M&A activity. No hiring freeze (obviously — they're hiring aggressively).
Time spent so far: 5 minutes.
LinkedIn Sales Nav search for Meridian Cloud + "Sales" + VP/Director:
Mutual connections: Your CEO knows Meridian's Series C lead at Accel. Warm path exists.
Time spent so far: 12 minutes.
The AE job posting says: "You'll use Salesforce, Outreach, Gong, and Clari daily." Confirmed — they already use Gong for conversation intelligence but may not be using it for coaching workflows. The enablement manager posting says "build a scalable onboarding and coaching program" — they're building this function from scratch.
BuiltWith confirms: Salesforce, Marketo, Intercom on the website.
Time spent so far: 15 minutes. Stop here.
═══════════════════════════════════════
ACCOUNT BRIEF: Meridian Cloud
Tier: 1 | Score: 4.6/5
Researched: 2026-03-10 | Refresh by: 2026-04-10
═══════════════════════════════════════
COMPANY SNAPSHOT
Industry: B2B SaaS (cloud infrastructure)
Size: 280 employees | Revenue: ~$40M ARR [confidence: medium — Crunchbase estimate]
Stage: Series C ($55M, closed Aug 2025)
HQ: Austin, TX
Fiscal Year Start: January
TRIGGER EVENT
Hired VP of Sales (Lisa Huang) 7 months ago + now hiring 3 AEs
and a new Sales Enablement Manager role — Source: LinkedIn job postings
Why it matters: Classic post-funding scaling pattern. New sales
leader building her team, no enablement infrastructure yet. They're
going to feel the ramp-time pain around AE #8-10. We solve that.
DISQUALIFICATION CHECK
Hard disqualifiers: None
Negative signals: None — Glassdoor reviews are positive (4.1 stars),
no leadership churn beyond normal Series C growth hiring
KEY CONTACTS
Primary: Lisa Huang, VP of Sales — lhuang@meridiancloud.com (unverified,
pattern-matched) — linkedin.com/in/lisahuang-sales
Confidence: Title verified via LinkedIn + company website | March 2026
Angle: She's building the sales org post-Series C. Previously at a
Gong customer — she knows the category. Reference her LinkedIn post
about "repeatable sales motion" and the enablement hire.
Secondary: Derek Patel, Director of Sales Ops — dpatel@meridiancloud.com
(unverified) — linkedin.com/in/derekpatel-salesops
Angle: He runs the stack. Salesforce + Outreach + Clari. Ask about
how they're measuring ramp time today.
TECH STACK (Relevant)
Using: Salesforce, Outreach, Gong, Clari, Marketo
Gap: No dedicated coaching/enablement platform. Gong is recording
calls but not structured for coaching workflows.
Competitor: Gong (adjacent, not direct competitor for coaching)
Source: Job postings + BuiltWith + LinkedIn profiles
WARM PATHS
CEO → Accel partner who led Meridian's Series C (ask for intro to Lisa)
RECOMMENDED APPROACH
Channel: Warm intro via Accel if possible. If not, LinkedIn to Lisa +
email sequence to Derek (multi-thread from Day 1)
Hook: "Saw you're building the enablement function from scratch —
most VP of Sales hires at post-Series C companies tell me the
ramp-time wall hits around AE #8."
Sequence: 30-Day Nurture cadence (mid-market, VP-level buyer)
═══════════════════════════════════════Total research time: 15 minutes. The rep can scan this brief in 60 seconds and write a personalized first touch in 5 minutes. That's the standard.
© 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/lead-research of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Lead Research 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 |
|---|---|---|---|---|---|---|
| Lead Research this skillTheCraigHewitt/skills | 159 | — | ~5.9k | Automated safety check: Pass | MIT | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cold Outreach Sequence BuilderBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.9k | Automated safety check: Pass | None | |
| Cold Outreachericrisco/rsc-harness | 180 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Personalize Emailexplorium-ai/gtm-skills | 185 | — | ~2k | Automated safety check: Pass | MIT | |
| Apify Buying Signal Detectionapify/awesome-skills | 266 | — | ~5.1k | Automated safety check: Notes | Apache-2.0 |
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.
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.
ericrisco/rsc-harness
A skill your agent uses when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits…
explorium-ai/gtm-skills
Cold email personalization skill for Claude Code and Codex: assemble an intent and firmographic signal pack for one prospect so a downstream LLM can compose a truly personalized outbound email.
apify/awesome-skills
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…
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.
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 research accounts, contacts, or build target lists. Lead Research is an agent skill from TheCraigHewitt/skills. When the user wants to research accounts, contacts, or build target lists.
Lead Research fits situations like: wants to research accounts; build target lists; the user says research this company; find decision makers.
Run `npx skills add TheCraigHewitt/skills --skill lead-research -a claude-code`. Or copy the skill folder (sales/lead-research in TheCraigHewitt/skills) into .claude/skills/lead-research in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill lead-research -a codex`. Or copy the skill folder (sales/lead-research in TheCraigHewitt/skills) into .agents/skills/lead-research 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 lead-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lead-research, .gemini/skills/lead-research, .github/skills/lead-research and .opencode/skills/lead-research in your project.
SKILL.md names no scripts, command-line tools or credentials: Lead Research 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.
Lead Research 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 Lead Research: B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Cold Outreach Sequence Builder (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), Cold Outreach (ericrisco/rsc-harness, 180 stars) and Personalize Email (explorium-ai/gtm-skills, 185 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.