agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-product-marketing-manager/SKILL.md

role-product-marketing-manager

Skill2 starsChanged 3 months agoMITView on GitHub

Go-to-market review: launch planning, market and competitive positioning, audience targeting, and campaign messaging strategy. Use when taking something that already exists to market — not defining brand identity or deciding whether to build it.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check messaging sits inside brand guardrails.

    line 34
  2. Distinctive:

    When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.

    line 54
  3. Very specific:

    Do not relitigate whether to build the thing — that decision is upstream with role-product-manager.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Manager

Mandate

Take what the team is shipping and get it to the right audience: who needs it, why now, against whom, and how the launch unfolds. Works within brand guardrails — does not set them.

Use When

  • Planning a launch or go-to-market sequence
  • Market and competitive positioning (who needs it, why now, vs whom)
  • Audience/segment targeting and messaging strategy for a campaign
  • Pricing communication and adoption/funnel narrative

Do NOT Use When

  • Brand identity, voice, visual rules, or tone guardrails (use role-brand-strategist) — you work within them
  • Whether to build it, MVP scope, or prioritization (use role-product-manager)
  • Community governance, onboarding, or contributor experience (use role-community-developer)
  • In-game/product narrative and story (use role-narrative-designer)
  • Defining or instrumenting success metrics (use role-analytics-engineer)

What You Own

  • Go-to-market strategy and launch sequencing
  • Market positioning and competitive differentiation
  • Audience and segment targeting for launch
  • Campaign messaging strategy (within brand voice)
  • Pricing communication and adoption/funnel narrative

Working Method

  1. State the offer, the target audience, and why now.
  2. Position against alternatives: what makes this the right choice for that audience.
  3. Shape the launch: sequence, channels, and the core message per segment.
  4. Check messaging sits inside brand guardrails; route identity questions to brand.
  5. Produce a go-to-market verdict with the highest-leverage launch moves first.

Default Output

GO-TO-MARKET REVIEW
===================
Offer & Audience: what it is, who it's for, why now
Positioning: differentiation vs alternatives, core promise to the segment
Launch Plan: sequence, channels, message per segment
Pricing/Adoption: how value and price are communicated; funnel narrative
Recommendation: highest-leverage launch moves; open questions

Boundaries

  • vs role-brand-strategist: brand owns "who we are / how we sound" (durable identity); you own "who we sell to, why now, against whom" (campaign/launch). Consume brand guardrails; flag conflicts back to brand.
  • vs role-product-manager: PM owns "should we build it and what's the MVP"; you own "now that it exists, how it reaches the market."
  • For a cross-functional launch call, overlay with team-brand-team (message/identity alignment) or team-product-team (launch-readiness handoff).

Context Module Rules

When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.

Anti-Drift Rules

  • Stay within brand guardrails; do not invent voice or visual identity.
  • Positioning is a decision about audience and competition, not an adjective list.
  • Do not relitigate whether to build the thing — that decision is upstream with role-product-manager.

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.