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 Sms

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned SMS and MMS marketing discipline. An agent skill from JasonColapietro/suede-creator-skills.

MITAuto-check passedMarketing & SEO

Install Suede Sms

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

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

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-sms --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-sms .claude/skills/suede-sms && 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-sms
GitHub stars
127
Token cost
~4.3k tokens
SKILL.md length
2,141 words
Files
7 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned SMS and MMS marketing discipline. An agent skill from JasonColapietro/suede-creator-skills.

  • Works in 10 steps: Business Type → Current State → Compliance Posture → …
  • Evaluating SMS as a channel
  • SKILL.md covers Before Starting, When SMS Beats Email, Compliance: Read First and Phone Number Types (US), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Sms is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned SMS and MMS marketing discipline. Use when evaluating SMS as a channel, designing consent-aware sequences, drafting messages, setting cadence, comparing number types or platforms, or defining measurement (TCPA consent, A2P 10DLC, quiet hours, cart-recovery and win-back texts. NOT FOR: email campaigns (use suede-emails), phone capture UX (use suede-site-alchemy), or legal certification) this skill does not give legal advice and never sends, schedules, imports, or registers.

Its SKILL.md is about 4.3k 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 Referral and retention marketing and Email marketing. 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

  • Evaluating SMS as a channel
  • Designing consent-aware sequences
  • Drafting messages
  • Setting cadence

Example prompts

  • “/suede-sms”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Business Type
  2. Current State
  3. Compliance Posture
  4. Goal
  5. Every send has a real cost
  6. Opt-in is your most valuable asset
  7. Each message must justify itself
  8. Brevity + clarity
  9. One CTA, one link
  10. Sender identity, every send

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 Sms loads about 4.3k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 2,141 words of instructions outside code blocks.

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

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). 2,141 words, ~4,254 tokens.

Download SKILL.mdSave it as .claude/skills/suede-sms/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
suede-sms
description
Suede-owned SMS and MMS marketing discipline. Use when evaluating SMS as a channel, designing consent-aware sequences, drafting messages, setting cadence, comparing number types or platforms, or defining measurement (TCPA consent, A2P 10DLC, quiet hours, cart-recovery and win-back texts. NOT FOR: email campaigns (use suede-emails), phone capture UX (use suede-site-alchemy), or legal certification) this skill does not give legal advice and never sends, schedules, imports, or registers.
metadata.version
1.0.0

Suede SMS Programs

Suede SMS designs consent-aware message programs for commerce, mobile, and SaaS use cases where immediacy can earn its interruption cost. It combines sequence logic, sender identity, cadence, carrier constraints, and measurement without claiming legal certification or sending messages.

Before Starting

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.

Gather this context (ask if not provided):

1. Business Type
  • B2C ecom / DTC, B2B SaaS, mobile app, services, fintech
  • Order volume or list size (SMS economics depend on scale)
  • Geographic mix (US, EU, both: compliance differs dramatically)
2. Current State
  • Existing SMS program (platform, list size, opt-in rate, opt-out rate, revenue/send)
  • Email program (SMS works best as a layer on top, not a replacement)
  • Phone number type: short code, toll-free, long code (10DLC)
  • Sequences already running (so a new flow does not double-tap the same contact)
3. Compliance Posture
  • US: A2P 10DLC registration complete? (Required since 2022: without it, your messages get filtered)
  • Opt-in mechanism in use? (Checkbox, keyword opt-in, double opt-in)
  • Privacy policy + terms include SMS disclosures?
4. Goal
  • Drive revenue (promotional, cart recovery, post-purchase)
  • Drive activation (welcome, onboarding, milestone nudges)
  • Transactional (order updates, auth codes, alerts)

When SMS Beats Email

SMS is not "another email." Use it where the channel's properties win:

Use CaseSMS or Email?Why
Abandoned cart recoverySMS first98% open rate within 3 min vs 20% for email in 24h
Order/shipping updatesSMSCustomers want it now, on their phone
Flash sale / limited dropSMSUrgency channel; immediate read
Auth codes / 2FASMS (or app)Latency-sensitive, must arrive in seconds
Welcome seriesEmail primary, SMS layerEmail carries the long-form content
Educational nurtureEmailToo much text for SMS, costs add up
NewsletterEmailWrong channel for SMS
Win-back lapsed customersBothSMS for the strong nudge, email for the offer detail
Post-purchase upsellSMSHigh open rate, ride the purchase momentum

General rule: SMS earns the right to interrupt because of opt-in. Use it for messages that genuinely benefit from immediacy. If it could wait 24 hours, send it via email.

Compliance: Read First

Compliance is the foundation, not an afterthought. A single TCPA class-action settlement runs $5M–$40M. The basics:

US: TCPA (Telephone Consumer Protection Act)
  1. Express written consent required for marketing SMS. Implied consent doesn't count.
  2. Clear disclosure at opt-in must include: program name, frequency expectation ("up to 4 msgs/month"), STOP/HELP instructions, "Msg & data rates may apply," link to terms.
  3. Honor STOP/UNSUBSCRIBE within seconds, every time, no exceptions, on every keyword variant (STOP, END, CANCEL, UNSUBSCRIBE, QUIT).
  4. Honor HELP with a response containing brand name + STOP info + support contact.
  5. Quiet hours: no marketing sends before 8am or after 9pm in the recipient's local time. Carrier rules and state laws (e.g., Florida, Oklahoma, Washington) are stricter than federal: default to 9am–8pm recipient-local.
  6. Keep written consent records with timestamp, opt-in source, and exact disclosure text shown. Auditable.
US: A2P 10DLC Registration (required since 2022)

Application-to-Person 10-digit long codes must be registered through The Campaign Registry (TCR) via your SMS platform. Without registration:

  • Throughput is throttled (or zero)
  • Carriers filter your messages
  • You'll see "delivered" status but recipients won't get them

Registration covers: brand identity verification, campaign use case (marketing, account notification, OTP, etc.), sample messages, opt-in mechanism, opt-out language. Sample message text from registration must match what you actually send.

  • Explicit opt-in required (no pre-checked boxes)
  • Right to withdraw consent must be as easy as giving it
  • Data subject access requests apply to SMS records
  • ePrivacy Directive layered on top of GDPR
Canada: CASL
  • Express consent + sender identification + unsubscribe in every message
  • Implied consent allowed for existing business relationships within 24 months
  • Penalties up to CAD $10M per violation

For full compliance details, edge cases, opt-in copy templates, and STOP/HELP response templates: see references/compliance.md.

Phone Number Types (US)

TypeThroughputCostUse CaseTrust
Short code (5-6 digit)100+ msg/sec$500–$1,000/mo + setupHigh-volume marketingHighest (carrier-vetted)
Toll-free (1-8XX)~3 msg/sec$10–$30/moMid-volume, B2C supportMedium-high (carrier-verified)
10DLC (regular long code)1–250 msg/sec$2–$10/moSMB, conversational, transactionalMedium (requires A2P 10DLC reg)

Rule of thumb: list <10K = 10DLC. List 10K–100K = toll-free. List 100K+ = short code.

Core Principles

1. Every send has a real cost

SMS isn't free. At $0.0075–$0.04 per send + carrier fees, a 100K send costs $750–$4,000. This forces relevance: you can't "blast." Segment hard.

2. Opt-in is your most valuable asset

Opt-in rate from email → SMS is typically 5–25%. A high-quality SMS list of 10K beats a low-quality list of 100K. Optimize opt-in quality, not volume.

3. Each message must justify itself

The recipient gave you their phone number. Every send should pass: "would I be glad I got this text?" If no, don't send.

4. Brevity + clarity

160 GSM-7 characters = 1 SMS segment. 161+ chars = 2 segments (you're billed for 2). Emojis force UCS-2 encoding (70 chars per segment). Plan for segment count.

Short links are mandatory (klvy.co, txt.attn.tv, branded short domain). Track UTM params on every link.

6. Sender identity, every send

"From [Brand]:" or branded short code at the start of every message. Even on automated flows. Recipients can't see "from" address: they need it inline.

SMS Sequence Types

Welcome / Opt-In Confirmation (immediate)

Send 1: Confirmation + reward (immediate)

From Acme: Thanks for joining! Here's 10% off: ACME10. Use at checkout: acme.co/sale. Reply STOP to opt out.

Optional Send 2 (24h later): Reminder + best-seller showcase

Abandoned Cart (highest-ROI flow for ecom)
  • Send 1 (30 min after abandon): "Forget something? Your cart's still here: [short link]"
  • Send 2 (4 hours later): Soft urgency + social proof
  • Send 3 (24 hours later, optional): Discount offer (only if margin allows)

Note: Discount on first message trains customers to abandon. Reserve discount for Send 2 or 3.

Browse Abandonment
  • Send 1 (1 hour after browse): Product + "Thinking it over?" + link
Post-Purchase
  • Send 1 (immediate): Order confirmation + delivery ETA (transactional, separate consent OK)
  • Send 2 (after delivery + 2 days): "How are you liking [product]?" + review prompt + cross-sell
Win-Back (lapsed)
  • Send 1 (60–90 days after last purchase): "We miss you" + curated picks
  • Send 2 (14 days later): Discount offer
  • Send 3 (final, 14 days later): Opt-out warning + last chance
Promotional / Campaign Sends
  • Flash sales, drops, launches, BFCM
  • 1–2 sends max per campaign
  • Stack against email send schedule to avoid same-day double-tap
Transactional (separate compliance bucket)
  • Order updates, shipping, delivery, auth codes, account alerts
  • Generally OK without separate marketing consent if directly related to a transaction the user initiated
  • Still subject to A2P 10DLC registration in US

For full sequence templates with copy and timing: see references/sequence-templates.md.

SMS Copy Guidelines

Structure
  1. Sender ID ("From Acme:" or brand short code): required
  2. Hook: first 5 words decide if they read on
  3. Value: what's in it for them, specifically
  4. CTA + short link: single action, single URL
  5. Compliance footer: "Reply STOP to opt out" (required on opt-in confirmation and at least quarterly thereafter; carrier-recommended on every promotional message)
Length
  • 160 chars (GSM-7) = 1 segment. Aim here.
  • 70 chars (UCS-2) if you use emojis, accented characters, or curly quotes: you'll pay for more segments.
  • 161–306 chars = 2 segments (concatenated SMS). Acceptable for richer messages, but you're paying double per send.
  • MMS (image + up to 1,600 chars) = 3–5× the SMS cost. Use sparingly for high-impact moments.
Show full SKILL.md (897 more words)Show less
Voice
  • Conversational, not corporate. SMS feels personal: write like you're texting a friend.
  • No subject line, no formatting, no marketing-speak.
  • Emojis are fine in moderation (one per message, situationally).
  • ALL CAPS reads as shouting. Avoid except for explicit codes (e.g., "Use ACME10").

Never ship these strings: they are the SMS defaults a model reaches for unprompted, and several are expensive too, since a leading emoji flips the message to UCS-2 and halves the segment to 70 characters. Replace each with the specific thing: the product they left, the amount off, the date it ends.

  • "Don't miss out!" / "Hurry, ends soon!" / "LAST CHANCE" / "Time is running out"
  • "Hey [Name]! 👋" / "Hey friend!" / "Psst..." / "We miss you 😢" / "It's been a while!"
  • "Exclusive offer just for you" / "You've been selected" / "Tap here" with no statement of what is on the other side
  • Flame, siren, alarm-clock, or party-popper emoji as the opener
Personalization
  • First name token if available (boosts CTR ~20%)
  • Recent product/category browse-based
  • Location-based offers (where applicable)

Platform Selection

Evaluation examples, not guaranteed integrations: this pack ships no SMS connectors. Before recommending one, verify vendor documentation, authenticated access, per-message cost, carrier support, consent storage, quiet hours, STOP/HELP behavior, and send limits.

PlatformBest ForCost TierVerify Before Use
Klaviyo SMSDTC ecom already on Klaviyo email$$Store integration, consent, attribution
PostscriptDTC Shopify ecom, deep integration$$Store integration, consent, attribution
AttentiveMid-market+ ecom, full-service$$$Store integration, consent, attribution
Twilio / PlivoCustom builds, transactional, devs$ (raw API)Number registration, throughput, callbacks
Brevo SMSEU-focused, email + SMS combo$Regional coverage, orchestration, suppression
SimpleTextingSMB, simple needs, ease of use$Regional coverage, consent record
Customer.ioBehavior-based automation + SMS$$Regional coverage, orchestration, suppression
AudienceTapSpecialized DTC capture$Capture method, consent record, carrier coverage

Quick picks:

  • Already on Klaviyo for email + DTC/ecom → Klaviyo SMS (no second platform to learn)
  • Shopify ecom, want deeper SMS-specific features → Postscript
  • Building custom SMS into a product → Twilio
  • B2B SaaS doing transactional/auth → Twilio or Customer.io

For platform deep-dives (features, pricing, integration paths, A2P registration): see references/platforms.md.

Measurement

Key Metrics
MetricWhat it tells youHealthy range (ecom DTC)
Opt-in rateTop of funnel health5–25% of email subscribers
CTRMessage relevance8–15% (vs ~3% email)
Conversion rate (per send)Revenue impact1–5% per promotional send
Revenue per send (RPS)Channel economics$0.20–$2.00
Opt-out rate per sendAudience fatigue<2% per send, <0.5% for promotional
Cost per sendChannel cost discipline$0.0075–$0.04
List growth rateAudience momentum5–15%/month early, 1–3% steady-state
What to track in analytics
  • UTM tag every link: utm_source=sms&utm_medium=sms&utm_campaign=[campaign-name]
  • Conversion attribution: SMS-driven sessions, last-click revenue, assisted conversions
  • LTV impact: SMS subscribers vs email-only subscribers (typically 1.5–3× LTV for SMS opt-ins)
What to A/B test
  • Send time (afternoon vs evening, local time)
  • Copy length (short SMS vs MMS with image)
  • Discount amount and trigger (immediate vs delayed)
  • Personalization tokens (with first name vs without)
  • CTA copy ("Shop now" vs "See it" vs "Last chance")

Output Format

When the user asks for an SMS plan, return these six sections, in this order, with these headings:

  1. Compliance check: Are they registered for A2P 10DLC (if US)? Is the opt-in mechanism compliant? Flag blockers first.
  2. Strategy: Which SMS flows to build first, ranked by ROI for their business model.
  3. Sequence designs: For each priority flow, one block per message, in this exact shape:
Trigger: [event that fires this message]
Delay: [time after the trigger]
Copy: (NN chars, N segments, GSM-7|UCS-2)
[the message exactly as it would send, sender ID and compliance footer included]
CTA link: [short link + UTM params]
Segment: [who receives this, who is excluded]
Compliance footer: [STOP language present / not required here, and why]
  1. Platform recommendation: Based on stack, list size, and complexity.
  2. Measurement plan: KPIs, benchmarks, A/B test queue.
  3. Compliance footer: Required disclosures, STOP/HELP response templates.

Keep recommendations specific. Don't say "send an SMS at the right time": say "send 30 min after cart abandon, 4 hours later if no purchase, 24 hours later with discount."

Pre-delivery self-check

Run this on the messages you just drafted, not on the user's program: section 1 above audits the program, and nothing else checks the copy. Any failure means the plan is not deliverable: name the failing item and fix it before presenting.

  • Every message carries the sender ID inline
  • Every message shows its character and segment count, and stays inside the segment budget you declared
  • Opt-in confirmation and at least one message per quarter carry STOP language
  • Every send time falls inside 9am–8pm recipient-local
  • No personal phone number appears in any draft
  • The drafted copy is consistent with the sample text declared at A2P registration

Common Mistakes

  1. Treating SMS like email: sending daily promotional blasts. Opt-out rates spike, list dies.
  2. Not tracking conversions: you can't justify channel ROI without attribution.
  3. No throttling on bulk sends: burst sends trigger carrier filtering. Use platform throttling.

Boundaries

  • Do not send or schedule messages, import or purchase lists, register numbers, change carrier settings, or mutate consent records without verified live state and explicit approval.
  • Do not treat this skill as legal advice or claim compliance. Require documented consent, sender identification, quiet-hour, opt-out, suppression, and jurisdiction review before activation.
  • Do not invent consent, delivery, revenue, or attribution data, and do not place personal phone numbers in drafts or reports.

Routing

  • Use suede-emails for the email side of a coordinated lifecycle program.
  • Use suede-site-alchemy for phone-number capture experiences.
  • Use suede-churn-prevention for approved win-back strategy.
  • Use suede-analytics to define delivery, response, and revenue measurement.
  • Use suede-ab-testing to design the send-time, copy-length, and offer tests queued in the measurement plan.
  • Use suede-deslop before any message goes to a real recipient.
  • From those skills, route SMS sequence design, copy, and consent-aware cadence back to suede-sms.

© 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-sms of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/compliance.md
  • references/platforms.md
  • references/sequence-templates.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Sms 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 Sms compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Sms this skillJasonColapietro/suede-creator-skills127—~4.3kAutomated safety check: PassMIT
Churn Preventionfreekmurze/dotfiles1k13 repos~4.4kAutomated safety check: PassNone
Smscoreyhaines31/marketingskills54k1 repos~4.6kAutomated safety check: PassMIT
Email Sequence Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~4.2kAutomated safety check: PassApache-2.0
Reactivation Specialistaaron-he-zhu/aaron-marketing-skills2.9k2 repos~4.1kAutomated safety check: PassApache-2.0
Growth Enginesickn33/agentic-awesome-skills47k2 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Churn Prevention

    freekmurze/dotfiles

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.

    1k GitHub starsUsed in 13 repos~4.4k tokens
    Marketing & SEOAuto-check passed

  • Sms

    coreyhaines31/marketingskills

    When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS.

    54k GitHub starsUsed in 1 repo~4.6k 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

  • Reactivation Specialist

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop…

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

  • Growth Engine

    sickn33/agentic-awesome-skills

    Motor de crescimento para produtos digitais -- growth hacking, SEO, ASO, viral loops, email marketing, CRM, referral programs e aquisicao organica.

    47k GitHub starsUsed in 2 repos~2.2k tokens
    Marketing & SEOAuto-check passed

  • Email Automation Builder

    Affitor/affiliate-skills

    Build multi-sequence email automation flows with branching logic.

    701 GitHub stars~2.9k tokensUpdated 25 days ago
    Marketing & SEOAuto-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 Sms

What does Suede Sms do?

Suede-owned SMS and MMS marketing discipline. An agent skill from JasonColapietro/suede-creator-skills. Suede Sms is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned SMS and MMS marketing discipline.

When should I use Suede Sms?

Suede Sms fits situations like: evaluating SMS as a channel; designing consent-aware sequences; drafting messages; setting cadence.

How do I install Suede Sms in Claude Code?

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

How do I install Suede Sms in Codex?

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

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

What does Suede Sms need to run?

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

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

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

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

What are the alternatives to Suede Sms?

Skills that share tags, products or a category with Suede Sms: Churn Prevention (freekmurze/dotfiles, 1k stars), Sms (coreyhaines31/marketingskills, 54k stars), Email Sequence Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Reactivation Specialist (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 Sms?

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.