Agent skill · Code Review & Quality

suede-customer-research

Suede-owned customer-research discipline for interview design, transcript and ticket synthesis, review and forum mining, quote banks, jobs, and evidence-backed personas. Use when discovering or synthesizing what a defined customer segment actually says, does, needs, and resists. NOT FOR: competitor-only profiling (use suede-competitor-profiling), writing final marketing copy (use suede-copy), or deciding product priorities without product evidence (use suede-product-marketing).

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-customer-research --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 12 KB
Bundled scripts: none
Version: 2.0.1
Path: skills/suede-customer-research/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Customer Research Use this Suede customer-research playbook to ground positioning, product, and copy in traceable customer evidence rather than assumption. ## 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 to skip questions already answered. --- ## Two Modes of Research ### Mode 1: Analyze Existing Assets You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal. ### Mode 2: Go Find Research You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract. Most engagements combine both. Establish which mode applies before proceeding. --- ## Mode 1: Analyzing Existing Research Assets ### Asset Types **Customer interview / sales call transcripts** - Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered - Look for: the moment they decided to look for a solution, what they tried before, what success

What's inside
Steps it walks through
  1. Before Starting
  2. Two Modes of Research
  3. Mode 1: Analyze Existing Assets
  4. Mode 2: Go Find Research
  5. Mode 1: Analyzing Existing Research Assets
  6. Asset Types
  7. Extraction Framework
  8. Synthesis Steps
  9. Research Quality Guardrails
  10. Mode 2: Digital Watering Hole Research
  11. Where to Look
  12. What to Extract from Each Source
  13. Research Synthesis Template
  14. Persona Generation
Ships with 3 files
  • agents/openai.yaml
  • evals/evals.json
  • references/source-guides.md
More from suede-creator-skills
All skills →
About this skill
What does the suede-customer-research skill do?

Suede-owned customer-research discipline for interview design, transcript and ticket synthesis, review and forum mining, quote banks, jobs, and evidence-backed personas. Use when discovering or synthesizing what a defined customer segment actually says, does, needs, and resists. NOT FOR: competitor-only profiling (use suede-competitor-profiling), writing final marketing copy (use suede-copy), or deciding product priorities without product evidence (use suede-product-marketing).

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-customer-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going