phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add phuryn/pm-skills --skill north-star-metricgit clone --depth 1 https://github.com/phuryn/pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/phuryn/pm-skills/north-star-metric)<a href="https://agentmods.dev/skills/phuryn/pm-skills/north-star-metric"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/north-star-metric/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/phuryn/pm-skills/north-star-metric"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/north-star-metric.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.00889 |
| Opus 5.5 | $0.00030 | $0.00356 |
| Sonnet 5.5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
north-star-metric scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- north-star-metric — 100% identical, 0 lines differ
- north-star-metric — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
North Star Metric
Identify a North Star Metric and 3-5 Input Metrics that form a metrics constellation. Classifies the business game being played and validates against criteria for an effective North Star. Use when defining key metrics, setting up a metrics framework, or choosing what to measure.
Domain Context
NSM is NOT: multiple metrics, a revenue/LTV metric (must be customer-centric), an OKR (that's a goal-setting technique), or a strategy (but choosing the right NSM is a strategic choice).
NSM IS: a single, customer-centric KPI that reflects the value customers get from the product and serves as a leading indicator of long-term business success. You can use Key Results (OKRs) to express expected change in NSM.
Free resource: The North Star Framework 101 (PDF)
When to Use
- Defining your company's key metric framework
- Setting up a metrics tracking system
- Choosing what to measure and optimize for
- Evaluating potential North Star candidates
- Triggers: North Star metric, north star, key metric, what to measure, metrics framework, OMTM
The Three Business Games
Before identifying your North Star, classify your business into one of these three games:
- Attention Game: How much time do customers spend using your product? (Examples: Facebook, Spotify, YouTube, TikTok)
- Transaction Game: How many transactions occur between customers and your platform? (Examples: Amazon, Uber, Airbnb, PayPal)
- Productivity Game: How efficiently can someone complete their work or achieve their goals? (Examples: Canva, Dropbox, Loom, Notion)
Prompt
You are a metrics strategist specializing in North Star metrics and growth measurement frameworks.
Given the following business context: $ARGUMENTS
Step 1: Classify the Business Game Determine which game this company plays: Attention, Transaction, or Productivity.
Step 2: Identify the North Star Metric Suggest a single metric that meets all seven criteria for an effective North Star:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 75 lines · 75 tokens per session scan A 00242397486a
north-star-metric is a skill published in the GitHub repository phuryn/pm-skills (27,091 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 889 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
pmm-resume
Resume reviewer and tailoring engine for Product Marketing Managers (IC to VP, including AI PMM roles). Takes baseline resume + job description → dissects JD → ranks bullets by impact fit → rebuilds complete resume in one pass. Trigger on: resume + JD paste, "tailor this", "which bullets for this role", "rebuild for…
product-marketing-context
Build and maintain the shared GTM brain — product context, ICP, positioning, voice, market context, proof points, plus optional strategy and execution, and the deal-reality fields (objections, switching forces, customer language, anti-persona) — that every other skill in this stack reads before producing output. Works…
workflow-orchestrator
Orchestrates multi-skill PMM programs end-to-end — chains positioning, competitive, GTM strategy, campaign briefs, stakeholder maps, and retros into one coherent program with a master document and brain updates. Trigger on: "run full GTM workflow", "run a full launch", "launch [product] end to end", "positioning…
positioning-messaging
Builds or audits positioning statements, messaging hierarchies, homepage copy, and persona cards using April Dunford's Obviously Awesome framework across five modes (build, audit, fletch, sales-enablement, homepage). Refuses to generate without a named primary persona and 3+ alternatives including status quo, and…
writing-assistant
Rewrites, sharpens and drafts B2B writing in the writer's real voice: Slack messages, emails, memos, PRDs, decks, plus marketing content (blog posts, landing pages, press releases, case studies, newsletters, social posts). Use whenever someone wants to rewrite, tighten, draft or audit copy, asks why copy isn't landing…
proof-points
Build and maintain a sourced, gated registry of the proof points your messaging relies on — metrics, customer quotes, case study results, and analyst citations. Use when pulling proof points out of a deck or battlecard, checking whether a stat is safe to use in copy, sourcing a new claim before it ships, or auditing…