Get buy-in and drive alignment when you have no direct power over the people you need to move. Covers stakeholder framing, pre-wiring decisions, and building credibility over time. Use when pushing for a direction without exec authority, navigating disagreements, or when a proposal keeps getting blocked.
Build a productive relationship with leadership by communicating effectively, managing expectations, and knowing when to push back. Use when navigating executive relationships, seeking alignment on direction, or when leadership requests conflict with team capacity.
Partner with design to create better products, not just prettier ones. Covers when to involve design, how to give useful feedback, and respecting the design process. Use when PM-design handoffs feel clunky, design feedback conversations are unproductive, or design is brought in too late.
Partner with engineering as a collaborator, not a ticket-writer. Covers communication norms, technical empathy, scope negotiation, and building mutual trust. Use when PM-engineering relationships feel transactional, technical decisions are made without product input, or scope conversations become adversarial.
Partner with marketing, sales, and customer success to bring products to market effectively. Covers launch coordination, sales enablement, and feedback loops. Use when launches aren't driving adoption, sales can't articulate the value prop, or customer feedback isn't reaching the product team.
Ship updates people actually want to read. Structures release notes, changelog entries, and product updates with what-changed, why-it-matters, and what-to-do-next. Use when writing changelogs or release announcements.
Write headlines, CTAs, and value props that move people to act. Audits existing copy for weak verbs, vague claims, and missing specificity. Use when writing landing pages, hero sections, email subject lines, or any surface where words need to do real work.
The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.
Tell the product story in a way that sticks. Structures origin stories, problem narratives, and transformation arcs. Use when building about pages, launch announcements, or pitch decks.
Create structured competitive battlecards for sales, product, and strategy conversations. Covers positioning, objection handling, competitive landmines, and knowing when to walk away. Use when preparing for competitive deals, losing to a specific competitor, or entering a market with established players.
Identify and prioritize feature gaps between your product and competitors. Not just what's missing but which gaps matter, which don't, and which you should intentionally keep. Use when losing deals to missing features, planning roadmap with competitive context, or evaluating build-buy-partner decisions.
Analyze the real cost of switching between products — financial, technical, operational, political, and emotional. Use when trying to win customers from competitors, worried about churn to alternatives, designing migration tools, or setting pricing relative to switching friction.
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
Reduce abandonment in every form, signup, and checkout flow. Multi-step logic, field reduction, inline validation, and completion micro-copy. Use when building signup flows, checkout pages, or any multi-field input.
Information architecture that guides visitors from curiosity to commitment. Enforces section order, content hierarchy, and scroll-depth logic. Use when building landing pages, product pages, or any conversion surface.
Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.
Build credibility through evidence, not claims. Patterns for social proof, testimonials, logo walls, case studies, and security badges. Use when conversion is low despite good traffic or when the product is new and unknown.
Turn raw customer feedback from multiple sources into clear product insights and priorities. Covers feedback collection, pattern recognition, and separating signal from noise. Use when feedback feels overwhelming, contradictory, or when the team can't agree on what users actually want.
Define user problems with enough clarity and specificity that the team can evaluate solutions against them. Covers problem framing, user evidence, and the gap between stated and real problems. Use when the team can't agree on what problem they're solving, solutions aren't landing, or feature requests are mistaken for problems.
Turn user research into product decisions, not just reports. Covers when to research, what methods to use, and how to act on findings. Use when product direction feels disconnected from users, research exists but isn't informing decisions, or you're building on assumptions.
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.