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 Product Marketing

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned product-marketing context discipline. An agent skill from JasonColapietro/suede-creator-skills.

MITAuto-check passedMarketing & SEO

Install Suede Product Marketing

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

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

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-product-marketing --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-product-marketing .claude/skills/suede-product-marketing && 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-product-marketing
GitHub stars
127
Token cost
~3k tokens
SKILL.md length
1,324 words
Files
4
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned product-marketing context discipline. An agent skill from JasonColapietro/suede-creator-skills.

  • Works in 12 steps: Check for Existing Context → Gather Information → Product Overview → …
  • A project needs a shared record of product
  • SKILL.md covers Workflow, Sections to Capture, Step 3: Create the Document and Step 4: Confirm, Version, and…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Product Marketing is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned product-marketing context discipline. Use when a project needs a shared record of product, audience, ICP, positioning, objections, customer language, proof, and goals, or when that record needs updating. NOT FOR: writing a campaign (use suede-campaign-in-a-box), conducting new customer interviews (use suede-customer-research), or publishing brand claims.

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

It sits in Marketing & SEO, covering User research, Market research and Positioning and messaging. 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

  • A project needs a shared record of product
  • Customer language
  • That record needs updating

Example prompts

  • “/suede-product-marketing”

Workflow steps

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

  1. Check for Existing Context
  2. Gather Information
  3. Product Overview
  4. Target Audience
  5. Personas (B2B only)
  6. Problems & Pain Points
  7. Competitive Landscape
  8. Differentiation
  9. Objections & Anti-Personas
  10. Switching Dynamics
  11. Customer Language
  12. Brand Voice

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 Product Marketing loads about 3k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,324 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
~3k

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,324 words, ~2,968 tokens.

Download SKILL.mdSave it as .claude/skills/suede-product-marketing/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
suede-product-marketing
description
Suede-owned product-marketing context discipline. Use when a project needs a shared record of product, audience, ICP, positioning, objections, customer language, proof, and goals, or when that record needs updating. NOT FOR: writing a campaign (use suede-campaign-in-a-box), conducting new customer interviews (use suede-customer-research), or publishing brand claims.
metadata.version
2.1.0

Suede Product Marketing Context

Suede Product Marketing maintains the shared evidence layer for audience, positioning, objections, customer language, and proof. The Suede growth suite reads this context so each downstream skill starts from the same verified product story.

The document is stored at .agents/product-marketing.md.

Workflow

Step 1: Check for Existing Context

First, check if .agents/product-marketing.md already exists. Also check .claude/product-marketing.md and the legacy filename product-marketing-context.md (in either .agents/ or .claude/) for older setups, if found anywhere other than .agents/product-marketing.md, offer to move it to the canonical location.

If it exists:

  • Read it and summarize what's captured: note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
  • Ask which sections they want to update
  • Only gather info for those sections
  • On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.

If it doesn't exist, offer two options:

  1. Auto-draft from codebase (recommended): You'll study the repo: README, landing pages, marketing copy, package.json, etc., and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.

  2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.

Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"

Step 2: Gather Information

If auto-drafting:

  1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
  2. Draft only what the sources actually say. Every auto-drafted field carries its source in the form [src: path/to/file.md], the file the claim came from. A field with no source is not drafted: leave it empty and mark it [unverified].
  3. Never source a field from inference. If the README implies a differentiator without stating it, if a competitor is guessed from the category, or if a testimonial-shaped sentence in marketing copy has no attributed customer, that field is [unverified], not a draft with a hedge. Differentiation, Competitive Landscape, Proof Points, and Customer Language are where this rule earns its keep; a fabricated entry there propagates to every skill that reads this doc.
  4. Present the draft and say plainly how many fields are sourced versus [unverified], then ask what needs correcting or is missing
  5. Iterate until the user is satisfied. A field the user confirms in conversation is sourced as [src: user]

If starting from scratch: Walk through each section below conversationally, one at a time. Don't dump all questions at once.

For each section:

  1. Briefly explain what you're capturing
  2. Ask relevant questions
  3. Confirm accuracy
  4. Move to the next

Push for verbatim customer language: exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.

Sections to Capture

1. Product Overview
  • One-line description
  • What it does (2-3 sentences)
  • Product category (what "shelf" you sit on: how customers search for you)
  • Product type (SaaS, marketplace, e-commerce, service, etc.)
  • Business model and pricing
2. Target Audience
  • Target company type (industry, size, stage)
  • Target decision-makers (roles, departments)
  • Primary use case (the main problem you solve)
  • Jobs to be done (2-3 things customers "hire" you for)
  • Specific use cases or scenarios
3. Personas (B2B only)

If multiple stakeholders are involved in buying, capture for each:

  • User, Champion, Decision Maker, Financial Buyer, Technical Influencer
  • What each cares about, their challenge, and the value you promise them
4. Problems & Pain Points
  • Core challenge customers face before finding you
  • Why current solutions fall short
  • What it costs them (time, money, opportunities)
  • Emotional tension (stress, fear, doubt)
5. Competitive Landscape
  • Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
  • Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
  • Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
  • How each falls short for customers
6. Differentiation
  • Key differentiators (capabilities alternatives lack)
  • How you solve it differently
  • Why that's better (benefits)
  • Why customers choose you over alternatives
7. Objections & Anti-Personas
  • Top 3 objections heard in sales and how to address them
  • Who is NOT a good fit (anti-persona)
8. Switching Dynamics

The JTBD Four Forces:

  • Push: What frustrations drive them away from current solution
  • Pull: What attracts them to you
  • Habit: What keeps them stuck with current approach
  • Anxiety: What worries them about switching
9. Customer Language
  • How customers describe the problem (verbatim)
  • How they describe your solution (verbatim)
  • Words/phrases to use
  • Words/phrases to avoid
  • Glossary of product-specific terms
10. Brand Voice
  • Tone (professional, casual, playful, etc.)
  • Communication style (direct, conversational, technical)
  • Brand personality (3-5 adjectives)
Show full SKILL.md (537 more words)Show less
11. Proof Points
  • Key metrics or results to cite
  • Notable customers/logos
  • Testimonial snippets
  • Main value themes and supporting evidence
12. Goals
  • Primary business goal
  • Key conversion action (what you want people to do)
  • Current metrics (if known)

Step 3: Create the Document

After gathering information, create .agents/product-marketing.md with this structure:

markdown
# Product Marketing Context

**Document version:** v1
**Last updated:** [date]
**Status:** complete | partial: missing: [required sections still empty]

*Every field ends with its source: `[src: README.md]`, `[src: interview
2026-05-04]`, `[src: user]`, or the marker `[unverified]` if nothing on record
supports it. An unsourced field is empty by definition; do not fill it to make
the document look finished.*

## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**

## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-

## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |

## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**

## Competitive Landscape
**Direct:** [Competitor]: falls short because...
**Secondary:** [Approach]: falls short because...
**Indirect:** [Alternative]: falls short because...

## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**

## Objections
| Objection | Response |
|-----------|----------|
| | |

**Anti-persona:**

## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**

## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |

## Brand Voice
**Tone:**
**Style:**
**Personality:**

## Proof Points
**Metrics:**
**Customers:**
**Testimonials:** *(verbatim only: a quote with no attributable source is `[unverified]`, never paraphrased into existence)*
> "[quote]": [who] [src: where this quote was published or collected]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |

## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**

## Changelog
*Newest first. One line per revision: what changed and why.*
- v1 ([date]): Initial context.

Step 4: Confirm, Version, and Save

  • Show the completed document
  • Ask if anything needs adjustment
  • Check the v1 floor before saving. Six sections must be non-empty and sourced for the document to be trustworthy as shared context: Product Overview, Target Audience, Problems & Pain Points, Differentiation, Customer Language, and Goals. Everything else is optional by product type. If any of the six is empty or entirely [unverified], set Status: partial and list exactly which ones on that line. Never save a partial document as complete.
  • What a partial document means downstream. A consuming skill that reads .agents/product-marketing.md and finds Status: partial must ask the user for the named missing sections before generating anything that depends on them, and must not infer them from the rest of the doc. Say this in the save message so the user knows why they will be asked again.
  • Set the version and changelog: this is the paper trail for a doc every other skill reads:
    • New document: set Document version: v1 and a single Changelog entry: - v1 ([today]), Initial context.
    • Updating an existing document: increment the version (v2 → v3 …), update Last updated to today, and prepend a new Changelog entry at the top of the list (newest first) summarizing what changed and why in one line. Never rewrite or reorder past entries.
    • A good entry names the sections touched and the reason, not "updated the doc." Examples:
      • - v3 (2026-07-16): Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP.
      • - v2 (2026-06-02): Rewrote value prop and objections after 5 customer interviews; added competitor Acme.
    • Use today's date in ISO form (YYYY-MM-DD) for the entry and Last updated.
    • Pure typo-only fix: don't bump the version or add a changelog entry: just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly, downstream skills will now generate against the new context.
  • Save to .agents/product-marketing.md
  • Tell them: "The Suede growth suite will now use this context automatically. The Changelog at the bottom tracks every revision, check it to see how your positioning has evolved. Run /suede-product-marketing anytime to update it."

Tips

  • Skip what doesn't apply, outside the six-section v1 floor in Step 4: not every product needs Personas (B2C), Switching Dynamics, or a Glossary. Skipping one of the six is not a skip: it is a partial document.

Boundaries

  • Do not overwrite an existing context file without reading it, preserving supported facts, and showing the user the material changes.
  • Do not invent customer language, differentiation, proof points, market position, or durable brand rules; label hypotheses and missing evidence.
  • Do not publish external copy or mutate product, CRM, analytics, or campaign systems. This skill owns the shared context document only.

Routing

  • Use suede-customer-research to gather new customer evidence.
  • Use suede-competitor-profiling for evidence on named competitors.
  • Use suede-marketing-plan to turn approved context into a channel plan.
  • Use suede-campaign-in-a-box to package an approved campaign.

© 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 3 other files in skills/suede-product-marketing of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Product Marketing 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 Product Marketing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Product Marketing this skillJasonColapietro/suede-creator-skills127—~3kAutomated safety check: PassMIT
Customer ResearchNexus-JPF/note-companion8706 repos~3.2kAutomated safety check: PassMIT
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Startup Validatorailabs-393/ai-labs-claude-skills4551 repos~2.8kAutomated safety check: PassMIT
Yao Positioning Skillyaojingang/yao-open-skills1.3k—~805Automated safety check: PassMIT
Traditional Market Analysismonarchjuno/vibe-investing299—~1.1kAutomated safety check: PassMIT

Similar skills

  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Marketing & SEOAuto-check passed

  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

  • Startup Validator

    ailabs-393/ai-labs-claude-skills

    Comprehensive startup idea validation and market analysis tool.

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

  • Yao Positioning Skill

    yaojingang/yao-open-skills

    Generate evidence-aware positioning reports for personal IPs, courses, products, services, brands, or companies by combining positioning theory, course-marketing analysis, user intent, competitor…

    1.3k GitHub stars~805 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Traditional Market Analysis

    monarchjuno/vibe-investing

    Analyze traditional market context for an investment case by identifying the current regime, cycle position, market expectations, liquidity and macro transmission, positioning and crowd psychology…

    299 GitHub stars~1.1k tokensUpdated 5 mo ago
    Marketing & SEOAuto-check passed

  • Collecting Intelligence

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to research competitors, plan customer interviews, conduct market research, or understand their competitive landscape.

    264 GitHub stars~4.9k tokensUpdated 2 mo 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 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 Product Marketing

What does Suede Product Marketing do?

Suede-owned product-marketing context discipline. An agent skill from JasonColapietro/suede-creator-skills. Suede Product Marketing is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned product-marketing context discipline.

When should I use Suede Product Marketing?

Suede Product Marketing fits situations like: A project needs a shared record of product; customer language; that record needs updating.

How do I install Suede Product Marketing in Claude Code?

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

How do I install Suede Product Marketing in Codex?

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

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

What does Suede Product Marketing need to run?

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

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

Suede Product Marketing 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 Product Marketing use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Suede Product Marketing?

Skills that share tags, products or a category with Suede Product Marketing: Customer Research (Nexus-JPF/note-companion, 870 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars), Startup Validator (ailabs-393/ai-labs-claude-skills, 455 stars) and Yao Positioning Skill (yaojingang/yao-open-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Product Marketing?

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.