New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Suede Emails

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences.

MITAuto-check passedMarketing & SEO

Install Suede Emails

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-emails -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-emails --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-emails .claude/skills/suede-emails && rm -rf skills-src

Use ~/.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/

Facts

Skill name
suede-emails
GitHub stars
127
Token cost
~2.5k tokens
SKILL.md length
1,200 words
Files
7 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences.

  • Works in 3 steps: Sequence Type → Audience Context → Goals
  • The user needs a multi-email flow with entry criteria
  • SKILL.md covers Initial Assessment, Core Principle, Email Sequence Strategy and Sequence Types Overview, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Emails is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences. Use when the user needs a multi-email flow with entry criteria, cadence, message roles, and a measurement plan: drip campaigns, welcome series, win-back flows, or trigger-based automations. NOT FOR: cold prospecting (use suede-cold-email), SMS as part of the same lifecycle program (use suede-sms), in-product activation flows (use suede-onboarding), or lifecycle-stage operations beyond…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).

It sits in Marketing & SEO, covering Email marketing and Cold outreach. 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

  • The user needs a multi-email flow with entry criteria
  • A measurement plan: drip campaigns
  • Trigger-based automations

Example prompts

  • “/suede-emails”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Sequence Type
  2. Audience Context
  3. Goals

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 Emails loads about 2.5k tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 139 tokens; SKILL.md has 1,200 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.7k

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,200 words, ~2,538 tokens.

Download SKILL.mdSave it as .claude/skills/suede-emails/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
suede-emails
description
Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences. Use when the user needs a multi-email flow with entry criteria, cadence, message roles, and a measurement plan: drip campaigns, welcome series, win-back flows, or trigger-based automations. NOT FOR: cold prospecting (use suede-cold-email), SMS as part of the same lifecycle program (use suede-sms), in-product activation flows (use suede-onboarding), or lifecycle-stage operations beyond email (use suede-revops).
metadata.version
2.0.0

Suede Lifecycle Email Systems

Suede designs lifecycle email as a consent-aware system of triggers, message roles, pacing, and measurable next actions. Create sequences that move a known audience toward value without inventing intent, exhausting the list, or confusing lifecycle messaging with cold outreach.

Initial Assessment

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.

Before creating a sequence, understand:

  1. Sequence Type

    • Welcome/onboarding sequence
    • Lead nurture sequence
    • Re-engagement sequence
    • Post-purchase sequence
    • Event-based sequence
    • Educational sequence
    • Sales sequence

  2. Audience Context

    • Who are they?
    • What triggered them into this sequence?
    • What do they already know/believe?
    • What's their current relationship with you?
    • What other emails are they already receiving?
    • What's the current email performance to beat?

  3. Goals

    • Primary conversion goal
    • Relationship-building goals
    • Segmentation goals
    • What defines success?

Core Principle

One email, one job: a single purpose and a single primary CTA per email. Everything downstream, sequence length, roles, copy, follows from that.

Email Sequence Strategy

Sequence lengths are set per type in Sequence Types Overview below; use those numbers, not a generic range. Adjust for sales-cycle length, product complexity, and relationship stage.

Timing/Delays
  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time
Subject Line Strategy
  • Clear > Clever
  • Specific > Vague
  • Benefit or curiosity-driven
  • 40-60 characters ideal
  • Test emoji (they're polarizing)

Patterns that work:

  • Question: "Still struggling with X?"
  • How-to: "How to [achieve outcome] in [timeframe]"
  • Number: "3 ways to [benefit]"
  • Direct: "[First name], your [thing] is ready"
  • Story tease: "The mistake I made with [topic]"
Preview Text
  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)
Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)
Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)
Onboarding Sequence (Product Users)

Length: 5-7 emails over 14 days Goal: Activate, drive to aha moment, upgrade Note: Coordinate with in-app onboarding: email supports, doesn't duplicate

Key emails:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md

Email Types by Category

Six categories: Onboarding · Retention · Billing · Usage · Win-Back · Campaigns.

Read references/email-types.md when you need to pick or design an individual email type: it carries the trigger, timing, role, and copy pattern for each one, plus an email audit checklist.

Email Copy Guidelines

Structure
  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close
Formatting
  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)
Tone
  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Read it out loud: does it sound human?

Never ship these strings. They are the lifecycle-email defaults a model reaches for unprompted, and every one of them is a slot where a specific sentence should be:

  • "We're thrilled to have you aboard!" / "We're excited to have you!"
  • "Welcome to the family!" / "You're in good company"
  • "Here's what you can do next" / "Let's get you started"
  • "Don't miss out" / "Act now" / "Limited time only"
  • "Quick question" / "Just checking in" / "Just following up"
  • "We noticed you haven't..." / "We miss you!"
  • "Ready to take your [X] to the next level?"
  • "Unlock the full power of..." / "Supercharge your..."
  • "As a valued customer" / "We value your feedback"

The replacement is always the same shape: name the specific thing this reader did, or the specific thing they get next. If a sentence would be true for any recipient of any product, it is one of these in disguise.

Show full SKILL.md (408 more words)Show less
Length
  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven
CTA Guidelines
  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md

Output Format

Sequence Overview
Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]
For Each Email
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
Metrics Plan
Per email: open rate, click rate, unsubscribe rate
Per sequence: completion rate, primary-conversion rate, revenue or signups attributed
Baseline: [the user's current numbers for this audience, or "none supplied"]
Review point: [when to read results and what number would trigger a rewrite]

Pre-delivery self-check

Run this on the drafted sequence before presenting it. Each box checks a rule this skill already states, against the copy you just wrote.

  • Every email has exactly one primary CTA
  • Every subject line is 40-60 characters: count them, do not estimate
  • No preview text repeats its subject line
  • Every body is inside the word band for its type (50-125 transactional / 150-300 educational / 300-500 story-driven)
  • Exit conditions are specified for the sequence
  • No string from the Tone blocklist appears anywhere in the copy
  • The consent and suppression assumption is stated explicitly rather than assumed: say which list, which opt-in, and what excludes a contact

Any box that fails means fix it before presenting. Do not deliver the sequence with the failure noted as a caveat.

Implementation Hand-off

Choose the provider only after reading the user's installed tools and live account state. Customer.io, Mailchimp, Resend, SendGrid, Kit, and similar services may support parts of the workflow, but this public Suede skill does not assume that any provider, connector, account, or permission is available.

Before implementation, return:

  1. The required trigger, audience, fields, suppression rules, and exit criteria
  2. The provider-neutral sequence and event contract
  3. The exact account or integration that must be inspected
  4. A preview-and-approval checkpoint before any live change or send

Boundaries

  • Do not send, schedule, import contacts, alter automations, or change suppression lists without explicit authorization.
  • Do not invent consent, deliverability, attribution, audience, or performance data.
  • Do not promise inbox placement or revenue; separate observed results from projections.
  • Do not decide legal compliance, transactional classification, or contact eligibility on the user's behalf.

Routing

  • Use suede-lead-magnets for the asset that feeds a nurture sequence.
  • Use suede-churn-prevention for cancellation, save, and dunning strategy.
  • Use suede-onboarding for in-product activation and suede-copy for destination-page copy.
  • Use suede-ab-testing for sequence experiments and suede-revops for lifecycle-stage orchestration.
  • Use suede-sms when the same lifecycle program should also reach people by text: SMS layers on top of email, it does not replace it.
  • Use suede-deslop before any email in the sequence goes to a real recipient.
  • From those skills, route lifecycle sequence design, cadence, and message roles back to suede-emails.

© 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 6 other files (references) in skills/suede-emails of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/copy-guidelines.md
  • references/email-types.md
  • references/sequence-templates.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Emails 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.

Suede Emails compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Emails this skillJasonColapietro/suede-creator-skills127—~2.5kAutomated safety check: PassMIT
Email Generationextruct-ai/gtm-skills109—~1.7kAutomated safety check: PassNone
56 Retargeting Plan Globalminhnv0807/ai-business-skills609—~2.8kAutomated safety check: PassMIT
Emailscoreyhaines31/marketingskills54k1 repos~2.8kAutomated safety check: PassMIT
Email Sequence Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~4.2kAutomated safety check: PassApache-2.0
Outreach Specialistognjengt/founder-skills447—~3.2kAutomated safety check: PassMIT

Similar skills

  • Email Generation

    extruct-ai/gtm-skills

    Render a cold-outreach email sequence from a fixed template set and a contact CSV whose input fields are already filled.

    109 GitHub stars~1.7k tokensUpdated 12 days ago
    Marketing & SEOAuto-check passed

  • 56 Retargeting Plan Global

    minhnv0807/ai-business-skills

    A skill your agent uses when warm audiences need a plan — retargeting tiers by intent and recency, a different message per tier, frequency caps, attribution windows, lookalike seeds, exclusion…

    609 GitHub stars~2.8k tokensUpdated 28 days ago
    Marketing & SEOAuto-check passed

  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.8k tokens
    Marketing & SEOAuto-check passed

  • Email Sequence Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound…

    2.9k GitHub starsUsed in 2 repos~4.2k tokens
    Marketing & SEOAuto-check passed

  • Outreach Specialist

    ognjengt/founder-skills

    Crafts high-converting outreach messages and email sequences for cold outreach, LinkedIn DMs, and follow-ups.

    447 GitHub stars~3.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed

  • Linkedin Comment To Outreach

    gethouston/houston

    Turn a single LinkedIn post URL into a paused cold email campaign in Instantly.

    117 GitHub stars~2.1k tokensUpdated today
    Writing & ContentAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo

  • Suede 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.

    127 GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

  • 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.

    127 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes

  • 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.

    127 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • 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.

    127 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • 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.

    127 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • 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.

    127 GitHub stars~5k tokensUpdated today
    Auto-check passed

Categories

Questions about Suede Emails

What does Suede Emails do?

Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences. Suede Emails is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences.

When should I use Suede Emails?

Suede Emails fits situations like: the user needs a multi-email flow with entry criteria; A measurement plan: drip campaigns; trigger-based automations.

How do I install Suede Emails in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-emails -a claude-code`. Or copy the skill folder (skills/suede-emails in JasonColapietro/suede-creator-skills) into .claude/skills/suede-emails in your project. Claude Code loads it when a task matches its description.

How do I install Suede Emails in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-emails -a codex`. Or copy the skill folder (skills/suede-emails in JasonColapietro/suede-creator-skills) into .agents/skills/suede-emails in your project. Codex loads it when a task matches its description.

Can I use Suede Emails 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-emails -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-emails, .gemini/skills/suede-emails, .github/skills/suede-emails and .opencode/skills/suede-emails in your project.

What does Suede Emails need to run?

SKILL.md names no scripts, command-line tools or credentials: Suede Emails is instructions for the agent only.

Does Suede Emails 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 Emails 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 Emails use?

Suede Emails 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 Emails use?

About 2.5k tokens (SKILL.md is roughly 10k 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.1k tokens, read only when the agent opens those files.

What are the alternatives to Suede Emails?

Skills that share tags, products or a category with Suede Emails: Email Generation (extruct-ai/gtm-skills, 109 stars), 56 Retargeting Plan Global (minhnv0807/ai-business-skills, 609 stars), Emails (coreyhaines31/marketingskills, 54k stars) and Email Sequence Designer (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 Emails?

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.