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 Sales Enablement

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned sales-enablement discipline. An agent skill from JasonColapietro/suede-creator-skills.

MITAuto-check passedSales & Support

Install Suede Sales Enablement

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

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

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

At a glance

Suede-owned sales-enablement discipline. An agent skill from JasonColapietro/suede-creator-skills.

  • Works in 4 steps: Value Proposition & Differentiators → Sales Motion → Collateral Needs → …
  • Creating pitch decks
  • SKILL.md covers Before Starting, Core Principles, Sales Deck / Pitch Deck and One-Pagers / Leave-Behinds, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Sales Enablement is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned sales-enablement discipline. Use when creating pitch decks, one-pagers, objection guides, demo scripts, talk tracks, battle cards, proposal structures, buyer cards, or deal-level ROI framing. NOT FOR: setting price or terms (use suede-pricing), building the offer (use suede-offers), sending outreach (use suede-cold-email), or publishing unsupported proof.

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

It sits in Sales & Support, covering Sales enablement and Fundraising and pitch decks. 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

  • Creating pitch decks
  • Objection guides
  • Proposal structures
  • Deal-level ROI framing

Example prompts

  • “/suede-sales-enablement”

Workflow steps

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

  1. Value Proposition & Differentiators
  2. Sales Motion
  3. Collateral Needs
  4. Current State

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 (its code samples are markdown).

    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 Sales Enablement loads about 3.7k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,877 words of instructions outside code blocks.

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

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,877 words, ~3,708 tokens.

Download SKILL.mdSave it as .claude/skills/suede-sales-enablement/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
suede-sales-enablement
description
Suede-owned sales-enablement discipline. Use when creating pitch decks, one-pagers, objection guides, demo scripts, talk tracks, battle cards, proposal structures, buyer cards, or deal-level ROI framing. NOT FOR: setting price or terms (use suede-pricing), building the offer (use suede-offers), sending outreach (use suede-cold-email), or publishing unsupported proof.
metadata.version
2.0.1

Suede Sales Enablement

Suede Sales Enablement turns verified positioning, proof, and deal context into rep-usable decks, one-pagers, objection guides, demos, and playbooks. Every asset separates sourced claims from modeled value and remains a draft until its audience and version are approved.

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. Value Proposition & Differentiators

    • What do you sell and who is it for?
    • What makes you different from the next best alternative?
    • What outcomes can you prove?

  2. Sales Motion

    • How do you sell? (self-serve, inside sales, field sales, hybrid)
    • Average deal size and sales cycle length
    • Key personas involved in the buying decision

  3. Collateral Needs

    • What specific assets do you need?
    • What stage of the funnel are they for?
    • Who will use them? (AE, SDR, champion, prospect)

  4. Current State

    • What materials exist today?
    • What's working and what's not?
    • What do reps ask for most?

Core Principles

Sales Uses What Sales Trusts

Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first.

Situation-Specific, Not Generic

Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show.

Scannable Over Comprehensive

Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.

Tie Back to Business Outcomes

Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%."

Sales Deck / Pitch Deck

10-12 Slide Framework
  1. Current World Problem: The pain your buyer lives with today
  2. Cost of the Problem: What inaction costs (time, money, risk)
  3. The Shift Happening: Market or technology change creating urgency
  4. Your Approach: How you solve it differently
  5. Product Walkthrough: 3-4 key workflows, not a feature tour
  6. Proof Points: Metrics, logos, analyst recognition
  7. Case Study: One customer story told well
  8. Implementation / Timeline: How they get from here to live
  9. ROI / Value: Expected return and payback period
  10. Pricing Overview: Transparent, tiered if applicable
  11. Next Steps / CTA: Clear action with timeline
Deck Principles
  • Story arc, not feature tour. Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there.
  • One idea per slide. If you need two points, use two slides.
  • Design for presenting, not reading. Slides support the conversation: they don't replace it. Minimal text, strong visuals.
Customization by Buyer Type
BuyerEmphasizeDe-emphasize
Technical buyerArchitecture, security, integrations, APIROI calculations, business metrics
Economic buyerROI, payback period, total cost, riskTechnical details, implementation specifics
ChampionInternal selling points, quick wins, peer proofDeep technical or financial detail

For full slide-by-slide guidance: See references/deck-frameworks.md

One-Pagers / Leave-Behinds

When to Use
  • Post-meeting recap: Reinforce what you discussed, keep momentum
  • Champion internal selling: Arm your champion to sell for you
  • Trade show handout: Quick intro that drives follow-up
Structure
  1. Problem statement: The pain in one sentence
  2. Your solution: What you do and how
  3. 3 differentiators: Why you vs. alternatives
  4. Proof point: One strong metric or customer quote
  5. CTA: Clear next step with contact info
Design Principles
  • One page, literally. Front only, or front and back maximum.
  • Scannable in 30 seconds. Bold headers, short bullets, whitespace.
  • Include your logo, website, and a specific contact (not info@).
  • Match your brand but keep it clean: this is a sales tool, not a brand piece.

For templates by use case: See references/one-pager-templates.md

Objection Handling Docs

Objection Categories
CategoryExamples
Price"Too expensive," "No budget this quarter," "Competitor is cheaper"
Timing"Not the right time," "Maybe next quarter," "Too busy to implement"
Competition"We already use X," "What makes you different?"
Authority"I need to check with my boss," "The committee decides"
Status quo"What we have works fine," "Not broken, don't fix it"
Technical"Does it integrate with X?," "Security concerns," "Can it scale?"
Response Framework

For each objection, document:

  1. Objection statement: Exactly how reps hear it
  2. Why they say it: The real concern behind the words
  3. Response approach: How to acknowledge and redirect
  4. Proof point: Specific evidence that addresses the concern
  5. Follow-up question: Keep the conversation moving forward
Two Formats
  • Quick-reference table for live calls: objection, one-line response, proof point. Fits on one screen.
  • Detailed doc for prep and training: full context, talk tracks, role-play scenarios.

For the full objection library: See references/objection-library.md

ROI Calculators & Value Props

Calculator Design

Inputs (current state metrics the prospect provides):

  • Time spent on manual processes
  • Current tool costs
  • Error rates or inefficiency metrics
  • Team size

Calculations (your formula for value):

  • Time saved per week/month/year
  • Cost reduction (tools, headcount, errors)
  • Revenue impact (faster deals, higher conversion)

Outputs (what the prospect sees):

  • Annual ROI percentage
  • Payback period in months
  • Total 3-year value
Value Prop by Persona
PersonaCares AboutLead With
CTO / VP EngArchitecture, scale, security, team velocityTechnical superiority, integration depth
VP SalesPipeline, quota attainment, rep productivityRevenue impact, time savings per rep
CFOTotal cost, payback period, riskROI, cost reduction, financial predictability
End userEase of use, daily workflow, learning curveTime saved, frustration eliminated
Implementation Options

Default to slide-based: the ROI story lives in the deck the rep already presents. Escape to a spreadsheet when the prospect supplies and wants to change their own inputs; build a web tool only when deal volume justifies it.

Demo Scripts & Talk Tracks

Script Structure
  1. Opening (2 min): Context setting, agenda, confirm goals for the call
  2. Discovery recap (3 min): Summarize what you learned, confirm priorities
  3. Solution walkthrough (15-20 min): 3-4 key workflows mapped to their pain
  4. Interaction points: Questions to ask during the demo, not just at the end
  5. Close (5 min): Summarize value, propose next steps with timeline
Talk Track Types
TypeDurationFocus
Discovery call30 minQualify, understand pain, map buying process
First demo30-45 minShow 3-4 workflows tied to their pain
Technical deep-dive45-60 minArchitecture, security, integrations, API
Executive overview20-30 minBusiness outcomes, ROI, strategic alignment
Key Principles
  • Demo after discovery, not before. If you don't know their pain, you're guessing which features matter.
  • Customize to their use case. Use their terminology, their data (if possible), their workflow.
  • Leave time for questions. A demo where the prospect doesn't talk is a demo that doesn't close.

For full script templates: See references/demo-scripts.md

Show full SKILL.md (732 more words)Show less

Case Study Briefs (Sales Format)

How Sales Case Studies Differ

Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.

Structure
  1. Customer profile: Industry, company size, buyer role
  2. Challenge: What they were struggling with (2-3 sentences)
  3. Solution: What they implemented (1-2 sentences)
  4. Results: 3 specific metrics (before/after)
  5. Pull quote: One sentence from the customer
  6. Tags: Industry, use case, company size, persona
Organization

Organize case studies so reps can find the right one instantly:

  • By industry: "Show me a case study for healthcare"
  • By use case: "Show me someone who used us for X"
  • By company size: "Show me an enterprise example"

Proposal Templates

Structure
  1. Executive summary: Their challenge, your solution, expected outcome (1 page max)
  2. Proposed solution: What you'll deliver, mapped to their requirements
  3. Implementation plan: Timeline, milestones, responsibilities
  4. Investment: Pricing, payment terms, what's included
  5. Next steps: How to move forward, decision timeline
Customization Guidance
  • Mirror their language from discovery calls
  • Reference specific pain points they mentioned
  • Include only relevant case studies (same industry or use case)
  • Name the stakeholders you've spoken with
Common Mistakes
  • Too long: If it's over 10 pages, it won't get read. Aim for 5-7.
  • Too generic: Templated proposals signal low effort. Customize the exec summary at minimum.
  • Burying the price: Don't make them hunt for it. Be transparent and confident.

Sales Playbooks

What Goes in a Playbook
  • Buyer profile: Who you're selling to, their goals and pains
  • Qualification criteria: BANT, MEDDIC, or your framework
  • Discovery questions: Organized by topic, not a script
  • Objection handling: Top 10 objections with responses
  • Competitive positioning: How you win against each competitor
  • Demo flow: Recommended sequence for each persona
  • Email templates: Follow-up, proposal, check-in, breakup
When to Build
  • New product launch: Reps need a single source of truth
  • New market segment: Different buyers need different approaches
  • New hire ramp: Playbooks cut ramp time significantly
Keeping It Living

Review quarterly, get input from top reps, remove anything outdated, and assign a named owner.

Buyer Persona Cards

Card Structure
FieldDescription
Role / titleCommon titles and reporting structure
GoalsWhat success looks like for them
PainsWhat frustrates them daily
Top objectionsThe 3-5 objections you'll hear from this role
Evaluation criteriaHow they judge solutions
Buying processTheir role in the decision, who they influence
Messaging angleThe one sentence that resonates most
Persona Types
  • Economic buyer: Signs the check. Cares about ROI and risk.
  • Technical buyer: Evaluates the product. Cares about capabilities and integration.
  • End user: Uses it daily. Cares about ease and workflow fit.
  • Champion: Advocates internally. Needs ammunition to sell for you.
  • Blocker: Opposes the purchase. Understand their concern to neutralize it.

Output Format

Deliver the right format for each asset type:

AssetDeliverable
Sales deckSlide-by-slide outline with headline, body copy, and speaker notes
One-pagerFull copy with layout guidance (visual hierarchy, sections)
Objection docTable format: objection, response, proof point, follow-up
Demo scriptScene-by-scene with timing, talk track, and interaction points
ROI calculatorInput fields, formulas, output display with sample data
PlaybookStructured document with table of contents and sections
Persona cardOne-page card format per persona
ProposalSection-by-section copy with customization notes

Every proof point and every ROI figure in a delivered asset carries an inline tag: [source: named customer / study / internal report + date] or [modeled, assumptions: the inputs used]. An untagged number is a delivery blocker: tag it or cut it before the asset goes out. The sales deck deliverable uses this unit, repeated for each of the 11 slides above:

markdown
### Slide N: [slide name]
**Headline:** [the single idea, written as a sentence]
**Body copy:** [on-slide text, minimal]
**Speaker notes:** [what the rep says out loud, not a re-read of the slide]
**Visual:** [chart / screenshot / logo wall / none]
**Proof:** [source: …] or [modeled, assumptions: …] for every number above

Tool Integrations

Partner platforms such as Introw can support engagement tracking, deal registration, and mutual action plans. Treat that as an evaluation lead, not a guaranteed integration: verify current vendor documentation, authenticated access, pricing, permissions, and data-export behavior before use.

Boundaries

  • Do not publish, send, present, or upload sales collateral without approval of the final audience, claims, and version.
  • Do not invent customer quotes, logos, benchmarks, savings, integrations, or product capabilities; cite the source for each proof point and label modeled ROI.
  • Do not decide pricing, contract terms, discounts, guarantees, or legal commitments. Route those decisions to their accountable owner.

Routing

  • Use suede-product-marketing for approved positioning and proof context.
  • Use suede-competitors for comparison and battle-card evidence.
  • Use suede-pricing for pricing and packaging decisions.
  • Use suede-revops for pipeline stages, routing, and deal-desk operations.

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

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/deck-frameworks.md
  • references/demo-scripts.md
  • references/objection-library.md
  • references/one-pager-templates.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Sales Enablement 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 Sales Enablement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Sales Enablement this skillJasonColapietro/suede-creator-skills127—~3.7kAutomated safety check: PassMIT
29 Xuat Khau B2bminhnv0807/ai-business-skills609—~2.9kAutomated safety check: PassMIT
Sales EnablementAvdLee/RocketSimApp80610 repos~3.5kAutomated safety check: PassCustom licence
Case Study BuilderBrianRWagner/ai-marketing-claude-code-skills441—~1.8kAutomated safety check: PassNone
B2B Lead Generationminhnv0807/ai-business-skills609—~1.2kAutomated safety check: PassMIT
Sales Enablementcoreyhaines31/marketingskills54k—~5.2kAutomated safety check: PassMIT

Similar skills

  • 29 Xuat Khau B2b

    minhnv0807/ai-business-skills

    Dung khi doanh nghiep Viet Nam muon ban ra NUOC NGOAI theo duong B2B — ho so nang luc tieng Anh, chon thi truong muc tieu, pitch deck cho buyer, email chao hang quoc te, chuan bi hoi cho thuong mai…

    609 GitHub stars~2.9k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed

  • Sales Enablement

    AvdLee/RocketSimApp

    When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts.

    806 GitHub starsUsed in 10 repos~3.5k tokens
    Sales & SupportAuto-check passed

  • Case Study Builder

    BrianRWagner/ai-marketing-claude-code-skills

    Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.

    441 GitHub stars~1.8k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

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

    609 GitHub stars~1.2k tokensUpdated 29 days ago
    Sales & SupportAuto-check passed

  • Sales Enablement

    coreyhaines31/marketingskills

    When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts.

    54k GitHub stars~5.2k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed

  • Eol Internal Enablement

    deanpeters/Product-Manager-Skills

    Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.

    7.2k GitHub stars~3.1k tokensUpdated 1 mo ago
    Sales & SupportAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Suede Sales Enablement

What does Suede Sales Enablement do?

Suede-owned sales-enablement discipline. An agent skill from JasonColapietro/suede-creator-skills. Suede Sales Enablement is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned sales-enablement discipline.

When should I use Suede Sales Enablement?

Suede Sales Enablement fits situations like: creating pitch decks; objection guides; proposal structures; deal-level ROI framing.

How do I install Suede Sales Enablement in Claude Code?

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

How do I install Suede Sales Enablement in Codex?

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

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

What does Suede Sales Enablement need to run?

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

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

Suede Sales Enablement 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 Sales Enablement use?

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

What are the alternatives to Suede Sales Enablement?

Skills that share tags, products or a category with Suede Sales Enablement: 29 Xuat Khau B2b (minhnv0807/ai-business-skills, 609 stars), Sales Enablement (AvdLee/RocketSimApp, 806 stars), Case Study Builder (BrianRWagner/ai-marketing-claude-code-skills, 441 stars) and B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Sales Enablement?

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.