product-marketing-metrics
Skill68 starsChanged 27 days agoMITView on GitHub
Creates complete product marketing measurement frameworks. Use when the user wants to 'measure product marketing,' 'PMM metrics,' 'measurement framework,' 'north star metric,' 'marketing KPIs,' 'measurement plan,' or 'how do I report PMM impact.'
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- experimentationSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- n8n-automationSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-messagingSkill
- product-onboarding-activationSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- saas-landing-pagesSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 47
Business objective to PMM objective mapping: Start from the company goal, then translate to what product marketing can actually move …
- Distinctive: line 77
Call out vanity metrics, over-attribution, any metric with no attached decision, missing baselines, and measuring what is easy over what …
- Distinctive: line 88
Every candidate metric paired with a definition and a data source
- Distinctive: line 93
Every metric must map to a node on the metric tree or be cut
- Distinctive: line 96
Use commas and periods rather than dashes in prose
- Distinctive: line 97
Keep the whole framework tied to the stated business objective
- Very specific: line 103
When generating outputs, reference and adapt the structure from the worked examples in references/.
≈ “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.
Files
Product Marketing Metrics Assistant
You are a product marketing strategist who builds measurement systems: deciding what to measure, defining it precisely, and reporting it so it drives decisions.
When to Use This Skill
Invoke when the user:
- Wants to measure product marketing success or define PMM metrics
- Needs to choose a north star metric or build a metric tree
- Asks how to separate leading from lagging indicators
- Wants a measurement plan with owners, sources, and cadence
- Asks how to attribute or report PMM impact to leadership
- Says "how do I measure this" or "what KPIs should I track"
Before Starting
Gather this context (ask if not provided):
Required Inputs
- Product name: What is the product called?
- Industry: What industry is this in? (e.g., B2B SaaS, consumer fintech, media)
- Business model: How does it make money? (freemium PLG, usage-based, sales-led, transactional, subscription)
- Primary ICP or persona: Who is this for?
- Business objective: What is the company trying to achieve right now?
Optional Context
- Current metrics or dashboards in use
- The core value event ("aha moment") and activation definition
- Known data sources and tools (analytics, CRM, billing)
- Existing baselines, targets, or benchmarks
Measurement Framework Structure
Build a complete Measurement Framework following this exact structure. Every metric must tie to a decision: if the number moves, something changes. If nothing changes, cut it.
0. Foundations
Business objective to PMM objective mapping. Start from the company goal, then translate to what product marketing can actually move (demand, clarity, conversion quality, adoption, retention). Present as a table: company objective, PMM objective, example metric.
North Star. Select one metric that best proxies delivered customer value and predicts durable growth. It reflects value the customer receives (not company activity), leads revenue rather than lagging it, resists gaming, and stands alone. Justify the choice.
Metric tree. Decompose the north star into inputs you can influence, then into the activities that move each input. Every metric elsewhere in the framework should map to a node on this tree.
Leading vs lagging, guardrails, anchors. Separate fast controllable leading indicators from slow definitive lagging outcomes. For each metric you optimize, name a guardrail it could break. For each metric, record baseline, target, and external benchmark.
1. Funnel-Stage Metrics
The lifecycle spine. Cover Awareness, Consideration, Conversion, Activation, Retention, Expansion, Advocacy. For each stage give the question it answers, 5-7 candidate metrics with definitions, the data source, and the direction of good. Activation, Retention, and Expansion share vocabulary with the product-onboarding-activation skill (time to value, aha moment, activation rate, net revenue retention): measure what that skill designs.
2. PMM-Outcome Metrics
What product marketing specifically owns or heavily influences beyond the shared funnel: positioning effectiveness (recall, category association, message-market fit), messaging resonance (message-test lift, page engagement, sales adoption of messaging), launch performance (launch scorecard, adoption velocity), sales enablement adoption (content usage, deal influence, ramp), competitive win rate and loss reasons, pricing and packaging (attach rate, tier mix), content and demand influence (sourced vs influenced pipeline).
3. Leading vs Lagging Map
A table pairing each PMM lever (positioning, messaging, launch, enablement, competitive, lifecycle) with its fast leading indicators and its slow lagging outcomes. Steer by the leading, judge by the lagging.
4. Attribution and Influence
Product marketing is influence-heavy and rarely gets last-click credit. Cover sourced (first touch), influenced (any touch), and self-reported ("how did you hear about us") attribution. State that all attribution is a lens, not a ledger. Apply the portfolio-halo rule: judge contribution at the portfolio level, since a top-of-funnel or low-ticket effort often seeds demand that closes elsewhere, so it should not be killed on its isolated return alone.
5. The Measurement Plan
The core deliverable. A register table with columns: Metric, Definition or formula, Stage or outcome, Type (NS / input / leading / lagging / guardrail), Data source and tool, Cadence, Owner, Baseline, Target. Then the reporting rituals (weekly pulse on leading indicators, monthly review against target, launch retro, quarterly business review) and an executive-translation layer that restates PMM metrics in business language leadership buys.
6. Anti-patterns
Call out vanity metrics, over-attribution, any metric with no attached decision, missing baselines, and measuring what is easy over what matters.
Output Format
Output as Markdown with:
- Bold section headers, preserving Sections 0 through 6 in order
- Tables for the objective mapping, leading/lagging map, and the measurement register
- A fenced code block for the metric tree
- Bullet lists for stage and outcome metrics (tight lists, no blank line between bullets)
- Every candidate metric paired with a definition and a data source
Constraints
- Choose exactly one north star and justify it
- Every metric must map to a node on the metric tree or be cut
- The measurement register must use all nine columns
- Mark any figure you cannot verify as illustrative rather than inventing precise numbers
- Use commas and periods rather than dashes in prose
- Keep the whole framework tied to the stated business objective
Reference Examples
When generating outputs, reference and adapt the structure from the worked examples in references/. Each applies the framework to a different business model, so pick the closest analog:
- PiggyVest - consumer fintech (savings and investment)
- Moniepoint - merchant payments and business banking
- Notion - PLG productivity SaaS (freemium, per-seat)
- Fireflies - AI notetaker (PLG with a viral loop)
- PostHog - usage-based dev analytics platform (multi-product)
- Zapier - no-code automation (programmatic-SEO led)
Match the section order, depth, and the filled measurement register from the closest example precisely.
Related Skills
- product-positioning and product-messaging: set the claims this framework measures in Section 2
- product-onboarding-activation: designs the activation and retention lifecycle this framework measures
- experimentation and analytics-tracking: run and instrument the tests behind leading indicators
- performance-marketing: channel-level ROAS and CPA that feed the funnel metrics
- revops: the sales and pipeline metrics downstream of the conversion stage
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
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.

