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.
Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences.
Install Suede Cold Email
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-cold-email --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/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-cold-email .claude/skills/suede-cold-email && 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 "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .claude/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-emailType 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 JasonColapietro/suede-creator-skills --skill suede-cold-email -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-cold-email --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/suede-cold-email .agents/skills/suede-cold-email && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .agents/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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 JasonColapietro/suede-creator-skills --skill suede-cold-email -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-cold-email --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/suede-cold-email .cursor/skills/suede-cold-email && 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 "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .cursor/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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/JasonColapietro/suede-creator-skills.git --path skills/suede-cold-email--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 JasonColapietro/suede-creator-skills --skill suede-cold-email -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-cold-email --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/suede-cold-email .gemini/skills/suede-cold-email && 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 "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .gemini/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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 JasonColapietro/suede-creator-skills suede-cold-emailInstalls 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 JasonColapietro/suede-creator-skills --skill suede-cold-email -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/suede-cold-email .github/skills/suede-cold-email && 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 "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .github/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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 JasonColapietro/suede-creator-skills --skill suede-cold-email -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-cold-email --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/suede-cold-email .opencode/skills/suede-cold-email && 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 "suede-cold-email" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-cold-email into .opencode/skills/suede-cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-cold-email", 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.
Facts
- Skill name
suede-cold-email- GitHub stars
- 127
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,115 words
- Files
- 9 (incl. references)
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences.
- Works in 5 steps: Who are you writing to? Role, company,… → What do you want? The outcome (meeting,… → What's the value? The specific problem… → …
- Repairing outbound email to qualified prospects
- SKILL.md covers Before Writing, Writing Principles, Voice & Tone and Structure, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Suede Cold Email is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).
It sits in Sales & Support, covering Cold outreach and Sales enablement. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.
When your agent uses it
- Repairing outbound email to qualified prospects
- Tasks that involve Cold outreach
- Tasks that involve Sales enablement
Example prompts
- “/suede-cold-email”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Who are you writing to? Role, company, why them specifically
- What do you want? The outcome (meeting, reply, intro, demo)
- What's the value? The specific problem you solve for people like them
- What's your proof? A result, case study, or credibility signal
- Any research signals? Funding, hiring, LinkedIn posts, company news, tech stack changes
What it can do on your machine
Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Suede Cold Email loads about 2.2k tokens when it runs, and up to ~7.8k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 1,115 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 1,115 words, ~2,226 tokens.
Download SKILL.mdSave it as
.claude/skills/suede-cold-email/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- suede-cold-email
- description
- Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).
- metadata.version
- 2.0.0
Suede Cold Email Writing
Use this Suede cold-email playbook to write concise, evidence-grounded outreach that sounds human and respects the recipient.
Before Writing
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Understand the situation (ask if not provided):
- Who are you writing to? Role, company, why them specifically
- What do you want? The outcome (meeting, reply, intro, demo)
- What's the value? The specific problem you solve for people like them
- What's your proof? A result, case study, or credibility signal
- Any research signals? Funding, hiring, LinkedIn posts, company news, tech stack changes
Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs: use what you have and note what would make it stronger.
Writing Principles
Write like a peer, not a vendor
The email should read like it came from someone who understands their world: not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
Every sentence must earn its place
Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
Personalization must connect to the problem
If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
See personalization.md for the 4-level system and research signals.
Lead with their world, not yours
The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
One ask, low friction
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
Voice & Tone
The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
Calibrate to the audience:
- C-suite: ultra-brief, peer-level, understated
- Mid-level: more specific value, slightly more detail
- Technical: precise, no fluff, respect their intelligence
What it should NOT sound like:
- A template with fields swapped in
- A pitch deck compressed into paragraph form
- A LinkedIn DM from someone you've never met
- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
Structure
There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
Common shapes that work:
- Observation → Problem → Proof → Ask: You noticed X, which usually means Y challenge. We helped Z with that. Interested?
- Question → Value → Ask: Struggling with X? We do Y. Company Z saw [result]. Worth a look?
- Trigger → Insight → Ask: Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
- Story → Bridge → Ask: [Similar company] had [problem]. They [solved it this way]. Relevant to you?
For the full catalog of frameworks with examples, see frameworks.md.
Subject Lines
Short, boring, internal-looking. The subject line's only job is to get the email opened: not to sell.
- 2-4 words, lowercase, no punctuation tricks
- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
- No product pitches, no urgency, no emojis, no prospect's first name
See subject-lines.md for the full data.
Follow-Up Sequences
Each follow-up should add something new: a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
- 3-5 total emails, increasing gaps between them
- Each email should stand alone (they may not have read the previous ones)
- The breakup email is your last touch: honor it
See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.
Show full SKILL.md (450 more words)Show less
Quality Check
Run this pass on the draft before presenting it. Every item resolves to something you can observe in the text, not a feeling about it.
- "You/your" outnumbers "I/we" in the body
- Deleting the personalization sentence breaks the sentence that follows it
- Exactly one ask, answerable with a one-line reply
- Body is under 75 words
- Zero strings from What to Avoid appear in the draft: check that list term by term, not by impression
- Read aloud it uses contractions, and no sentence reads as marketing copy
Any item that fails means rewrite before presenting. Do not hand over a draft with a caveat attached to it.
Output Format
Deliver every email in this shape, with these field labels verbatim.
Subject: [2-4 words, lowercase]
Body: (NN words, target under 75)
[the email exactly as it would be pasted into the send tool]
CTA: [the single ask, quoted from the body]
Personalization source: [the specific signal this email traces to (the post, the filing,
the job ad, the release) with enough detail that the user can confirm it is real]Personalization source: is required on every email. It is what makes the "do not invent personalization" boundary auditable. If you cannot name a real source, you do not have personalization, and the opening line has to change.
Emit the follow-up table only when the user asked for a sequence rather than a single message:
| # | Send day | New angle it carries | Subject |
|---|---|---|---|
| 1 | 0 | ... | ... |
| 2 | +3 | ... | ... |
3-5 emails total: see follow-up-sequences.md for cadence and angle rotation. Omit the table entirely for a single-message request.
What to Avoid
- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
- Feature dumps: one proof point beats ten features
- HTML, images, or multiple links
- Fake "Re:" or "Fwd:" subject lines
- Identical templates with only {{FirstName}} swapped
- Asking for 30-minute calls in first touch
- "Just checking in" follow-ups
Data & Benchmarks
The references contain performance data if you need to make informed choices:
- benchmarks.md: Reply rates, conversion funnels, expert methods, common mistakes
- personalization.md: 4-level personalization system, research signals
- subject-lines.md: Subject line data and optimization
- follow-up-sequences.md: Cadence, angles, breakup emails
- frameworks.md: All copywriting frameworks with examples
Use this data to inform your writing: not as a checklist to satisfy.
Boundaries
- Do not invent personalization, mutual connections, customer facts, results, urgency, or prior contact.
- Do not scrape prohibited data, expose sensitive personal information, or advise evasion of consent, spam, or platform rules.
- Do not send, schedule, enroll, or follow up with anyone without explicit authorization for the exact recipients and sequence.
- Do not decide that silence means consent; honor opt-outs and suppression lists before any execution.
Routing
- Need a qualified prospect list -> use
suede-prospecting. - Need lifecycle or nurture email -> use
suede-emails. - Need positioning context or collateral -> use
suede-product-marketingorsuede-sales-enablement. - Need CRM stages, lead routing, or suppression operations -> use
suede-revops. - Before anything goes to a real recipient -> use
suede-deslop. - From those skills, route cold outbound message and follow-up writing back to
suede-cold-email.
© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (references) in skills/suede-cold-email of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- evals/evals.json
- references/benchmarks.md
- references/follow-up-sequences.md
- references/frameworks.md
- references/personalization.md
- references/subject-lines.md
Open the folder on GitHubat commit e5f94d7
Compare with similar skills
Suede Cold Email 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 |
|---|---|---|---|---|---|---|
| Suede Cold Email this skillJasonColapietro/suede-creator-skills | 127 | — | ~2.2k | Automated safety check: Pass | MIT | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Msp SalesRTFM-IT-Services-LLC/msp-claude-skills | 115 | — | ~7.8k | Automated safety check: Pass | Custom licence | |
| Deal Playbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Sales Enablement Kitaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| 33 B2b Lead Genminhnv0807/ai-business-skills | 609 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Msp Sales
RTFM-IT-Services-LLC/msp-claude-skills
A skill your agent uses whenever the user wants sales documents, content, or procedures for their managed IT services (MSP) business: cold outreach emails or sequences, call scripts or talk tracks…
Deal Playbook
jeremylongshore/tons-of-skills-marketplace
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
Sales Enablement Kit
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch…
33 B2b Lead Gen
minhnv0807/ai-business-skills
Dung khi can tim va tiep can khach hang doanh nghiep — xac dinh ICP, dung danh sach prospect co nguon va ngay verify, cham diem Hot/Warm/Cold, va viet outreach qua Zalo, dien thoai, email.
Cold Outbound Optimizer
ericosiu/ai-marketing-skills
Design, analyze, and optimize cold outbound email campaigns for Instantly.
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede Release Linter
JasonColapietro/suede-creator-skills
Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.
Creator Rights Passport
JasonColapietro/suede-creator-skills
Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.
Suede Clip to Guide
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
Suede MCP Release QA
JasonColapietro/suede-creator-skills
Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.
Android App Factory
JasonColapietro/suede-creator-skills
Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.
Suede Ad Creative
JasonColapietro/suede-creator-skills
Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.
Related
Categories
Questions about Suede Cold Email
What does Suede Cold Email do?
Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Suede Cold Email is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences.
When should I use Suede Cold Email?
Suede Cold Email fits situations like: repairing outbound email to qualified prospects; tasks that involve Cold outreach; tasks that involve Sales enablement.
How do I install Suede Cold Email in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email -a claude-code`. Or copy the skill folder (skills/suede-cold-email in JasonColapietro/suede-creator-skills) into .claude/skills/suede-cold-email in your project. Claude Code loads it when a task matches its description.
How do I install Suede Cold Email in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email -a codex`. Or copy the skill folder (skills/suede-cold-email in JasonColapietro/suede-creator-skills) into .agents/skills/suede-cold-email in your project. Codex loads it when a task matches its description.
Can I use Suede Cold Email in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-cold-email, .gemini/skills/suede-cold-email, .github/skills/suede-cold-email and .opencode/skills/suede-cold-email in your project.
What does Suede Cold Email need to run?
SKILL.md names no scripts, command-line tools or credentials: Suede Cold Email is instructions for the agent only.
Does Suede Cold Email access the network?
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.
Is Suede Cold Email safe to install?
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.
What licence does Suede Cold Email use?
Suede Cold Email is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Suede Cold Email use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.
What are the alternatives to Suede Cold Email?
Skills that share tags, products or a category with Suede Cold Email: B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Msp Sales (RTFM-IT-Services-LLC/msp-claude-skills, 115 stars), Deal Playbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Sales Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Suede Cold Email?
JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.
Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.