Turn raw user feedback into actionable product decisions. Categorization frameworks, signal vs noise filtering, and severity scoring. Use when processing interviews, support tickets, or reviews into product direction.
Understand what people actually hire your product to do. Maps functional, emotional, and social jobs. Surfaces real competition and generates interview frameworks. Use when product direction feels unclear or when features aren't landing.
Build user models that actually inform decisions. Maps motivations, friction points, and decision triggers beyond demographic templates. Use when building for multiple user types or when the agent needs to reason about different users.
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
Identify the moment when a new user first experiences your product's core value. Maps the path from signup to that moment and removes friction in between. Use when new user retention is poor, redesigning onboarding, or when the product has strong acquisition but weak activation.
Identify behavioral, usage, and contextual signals that predict a customer is about to leave — before they cancel. Build an early warning system, not a postmortem. Use when churn is too high, building health scores, or designing proactive retention interventions.
Analyze retention by cohort to understand how and why users stick around or leave. Moves beyond vanity metrics like MAU to actionable retention insights. Use when retention looks bad and you don't know where to focus, measuring impact of product changes, or comparing retention across segments.
Position against alternatives without being negative. Maps competitive landscape, identifies differentiation axes, and generates comparison frameworks. Use when building comparison pages, handling objections, or differentiating from existing solutions.
Decide what to build next based on impact, not excitement. Applies scoring frameworks to feature backlogs. Use when scope is unclear, when the agent is about to build everything at once, or when deciding what ships in v1 vs v2.
Test assumptions before committing resources. Generates lean validation plans, fake door tests, and interview scripts. Use before building anything expensive or when there's no evidence anyone wants what's being built.
Articulate why a product exists, who it serves, and what it replaces. Generates positioning statements, competitive angles, and category definitions. Use when launching something new, entering a crowded market, or when nobody can explain what the product does in one sentence.
First principles decisions for products that don't exist yet. Helps reason about market gaps, user needs, MVP scope, and what to build first. Use when starting from scratch, scoping an MVP, or when the agent needs to think before it builds.
Build a deeply reasoned, evidence-aware BRAND.md that acts as the canonical operational model of any brand. Use this when a brand needs to be understood, reconstructed, documented, governed, reproduced, critiqued, or extended. The skill converts source material and observed brand behavior into a usable brand intelligence system rather than a conventional brand-book summary.
Critique a specific body of brand work by separating observation, impact, root cause, evidence, and recommendation, with severity set by consequence rather than taste. Use to review a logo, identity, campaign, website, messaging, naming direction, or brand book, when feedback has become subjective or endless, or when work keeps being revised without improving. Produces a critique report with root causes and a defensible verdict.
Build brand governance that protects equity while letting teams move fast — decision rights, asset classification, review thresholds, drift detection, exception handling, and an evidence-led protocol for evolving the brand. Use when brand decisions bottleneck on one person, when guidelines are ignored or applied so rigidly work stalls, when nobody knows who decides, or when a brand needs to change without discarding what it has built. Produces a governance manual teams can act on.
Diagnose the real brand problem before anyone designs an answer. Use at the start of any brand engagement, when a brief is vague or arrives pre-solved ("we need a rebrand", "our messaging isn't landing"), or when work keeps failing review for reasons nobody can name. Produces an evidence-backed diagnosis of business reality, audience progress, category behavior, existing equity, perception gaps, and the single highest-leverage problem branding can influence.
Develop and evaluate names for how they behave in the real world — in speech, in memory, in spelling, in search, in sales calls, across languages, and across future products. Use when naming or renaming a company, product, or feature, when a shortlist needs evaluation, or when a favored name needs stress-testing before legal spend. Produces a naming report with behavioral tests, a defended recommendation, and an explicit register of checks that still require professional clearance.
Reconcile strategy, positioning, naming, verbal identity, visual identity, worldbuilding, governance, and applications into one prioritized diagnosis of the whole brand system. Use when a brand needs a full audit rather than a critique of one asset, when specialist reviews contradict each other, when leadership must decide what to protect, change, test, and defer, or before a rebrand decision. Produces a review decision with root causes, priorities, owners, and a validation plan.
Run the final release gate for a brand system — verifying strategy, expression, recognition, real applications, assets, templates, accessibility, legal and cultural boundaries, governance, operational readiness, and measurement before launch. Use before launching or relaunching a brand, before handing a system to another team or agency, or when someone needs to decide whether the brand can actually operate rather than merely present. Produces a release report with a defensible verdict and a post-launch learning plan.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.