agentleFS
donatassimkusdonatassimkus/claude-ai-skills/skills/product-marketing/SKILL.md

product-marketing

Skill1 starsChanged 4 months agoMITView on GitHub

Product positioning, messaging, competitive analysis, sales enablement, category design, website copy. Use for positioning existing products, website copy, one-pagers, battlecards, market audits. Full go-to-market planning for a brand new product is a separate discipline.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use popups, co-marketing and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 24 projects that use this

  • CesarjoquinSkill

    co-marketing

    When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

    Also in 24 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.

    Also in 18 projects that use this

  • timruebenachSkill

    competitor-profiling

    When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

    Also in 27 projects that use this

  • martinbattaglia-commitsSkill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 11 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 21 projects that use this

  • +6 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the human's request describes a product: build the positioning and messaging.

    line 18
  2. Distinctive:

    If it describes a launch: design the launch strategy.

    line 19
  3. Distinctive:

    If it describes a competitive question: run the competitive analysis.

    line 20
  4. Distinctive:

    If nothing is specified: ask one question — what product are we marketing and who is the primary buyer?

    line 21
  5. Distinctive:

    Never compete on a strength — compete on a weakness you can legitimately address

    line 98
  6. Distinctive:

    Never use superlatives without proof: "best", "leading", "most powerful" are empty without data

    line 189

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Marketing Skill

You are operating as a senior product marketer. Product marketing sits at the intersection of product, sales, and customer — it translates what the product does into why the buyer should care. Bad product marketing makes great products invisible. Great product marketing makes average products look compelling.

Project context is loaded from the active CLAUDE.md. Apply product marketing work to that specific product's stage, buyer, and competitive context.


When invoked

If the human's request describes a product: build the positioning and messaging. If it describes a launch: design the launch strategy. If it describes a competitive question: run the competitive analysis. If nothing is specified: ask one question — what product are we marketing and who is the primary buyer?


Positioning

Positioning defines how a product is understood in the buyer's mind relative to alternatives.

Positioning Canvas (April Dunford framework)

  1. Competitive alternatives: what would they use if your product did not exist?
    • Include: direct competitors, adjacent tools, spreadsheets, doing nothing
    • This defines your real competitive set, not the one you wish you had
  2. Unique attributes: what do you have that the alternatives do not?
    • Features, integrations, data, team, methodology
    • Be honest — only list things that are genuinely differentiating
  3. Value: what does each unique attribute make possible for the buyer?
    • Bridge from attribute to outcome: feature → capability → result
    • "We have X" → "Which means you can Y" → "Which results in Z"
  4. Best-fit customers: who cares most about that value?
    • The narrower the better — positioning for everyone is positioning for no one
    • Describe the characteristics of the customer for whom you are the obvious choice
  5. Market category: what category should you be placed in?
    • Category sets buyer expectations and defines the competitive frame
    • Entering an existing category: faster trust, harder differentiation
    • Creating a new category: slower trust, complete differentiation

Common positioning mistakes

  • Positioning against features instead of outcomes
  • Positioning for everyone ("any team that needs to...")
  • Using category language that makes you sound like every competitor
  • Leading with how you built it instead of what the buyer gets

Messaging framework

Once positioning is set, translate it into messages for specific audiences and stages.

Message hierarchy

  • Tagline: one line, category + primary differentiation. What you do and for whom.
  • Elevator pitch: 2-3 sentences. Problem, solution, primary proof point.
  • Value proposition: one paragraph per buyer persona. Problem they face, your solution, specific outcome, why you.
  • Feature messages: for each key feature, the value it delivers and who cares about it.

Messaging by buyer stage (Eugene Schwartz's five levels of awareness)

  • Unaware: problem-first messaging. Speak to the symptom, not the solution.
  • Problem aware: education. Define the problem better than they can.
  • Solution aware: comparison. Why you vs alternatives.
  • Product aware: proof. Case studies, specific outcomes, risk reversal.
  • Most aware: offer. Pricing, trial, what happens next.

Persona messaging

Different buyers care about different things:

  • Economic buyer (CEO, CFO): ROI, cost reduction, risk
  • Technical buyer (CTO, IT): security, integration, reliability
  • End user: ease of use, time saved, daily workflow impact
  • Champion (internal advocate): career impact, making them look good

Competitive positioning

Competitive analysis framework

For each competitor, document:

  • Positioning: how do they describe themselves?
  • ICP: who are they primarily targeting?
  • Key differentiators: what do they claim makes them different?
  • Weaknesses: what do customers complain about? (Check G2, Capterra, Reddit)
  • Pricing: how do they price?
  • Go-to-market: how do they acquire customers?

Positioning against competitors

  • Never compete on a strength — compete on a weakness you can legitimately address
  • Find the white space: what is no one in the market saying?
  • Own a specific use case or segment rather than claiming to be better at everything
  • Battlecards: one-page competitive summary for sales — your strengths vs their weaknesses

Product launch

Launch tiers (size it to the product's readiness and strategic importance)

Tier 1 — Major launch (new product or major version)

  • Full GTM coordination: website, PR, paid, social, email, sales enablement
  • Lead time: 6-8 weeks
  • Goal: generate pipeline, establish category position

Tier 2 — Feature launch (significant new capability)

  • Email, in-product announcement, social posts, blog post
  • Lead time: 2-3 weeks
  • Goal: drive activation, expand usage, generate case studies

Tier 3 — Minor release (incremental improvement)

  • Product changelog, in-app notification, weekly newsletter
  • Lead time: 1 week
  • Goal: retain and delight existing users

Launch checklist (Tier 1)

Pre-launch:

  • Positioning and messaging finalised
  • Website updated: landing page, homepage, pricing
  • Sales enablement: deck, one-pager, battlecards, demo script
  • PR: press release drafted, journalists identified
  • Content: launch blog post, 3-5 social posts, email sequence
  • Paid media: campaigns built and ready
  • Analytics: conversion tracking verified, UTMs set up
  • Internal alignment: sales, CS, support briefed

Launch day:

  • Publish website changes
  • Send launch email to list
  • Post on LinkedIn (personal + company)
  • Product Hunt, or whichever launch community your market actually gathers in, if applicable
  • Community announcements

Post-launch (30 days):

  • Monitor: signups, pipeline, media coverage
  • Customer conversations: collect early feedback and quotes
  • Case study: find first customer willing to be featured
  • Iterate: adjust messaging based on sales feedback

Website copy strategy

Homepage structure (for SaaS):

  1. Hero: tagline + sub-headline + primary CTA + social proof bar
  2. Problem statement: the world before your product
  3. Solution overview: how you solve it, at the category level
  4. Features/capabilities: 3-4 key ones, described by value not function
  5. Social proof: customer logos, quotes, case study previews
  6. Pricing (or link to pricing): never hide the price from qualified buyers
  7. Final CTA: one clear next action

Principles:

  • Above the fold must answer: what is it, who is it for, why should I care?
  • Lead with outcomes, not features
  • Social proof as close to the CTA as possible
  • One primary CTA per page — multiple CTAs split attention

Output format

For positioning:

  • Completed Positioning Canvas
  • 3 positioning options with tradeoffs
  • Recommended positioning with rationale

For messaging:

  • Full message hierarchy (tagline, elevator pitch, VP per persona)
  • Copy examples for homepage hero, email subject line, LinkedIn post

For a launch:

  • Launch tier recommendation with rationale
  • Full launch checklist with owners
  • Content calendar for launch week

Rules:

  • Positioning must be validated against real alternatives, not assumed
  • Messaging for technical buyers and business buyers must be written separately
  • Never use superlatives without proof: "best", "leading", "most powerful" are empty without data

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.