SkillAgentSearch skills...

derisk-measurement-advisor

Identify what to measure, test, or track to de-risk a product or AI idea

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill derisk-measurement-advisor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of derisk-measurement-advisor

derisk-measurement-advisor scores 86/100 on our quality scale, 41st of 61 Product Management skills we index.

Its SKILL.md is 23 KB long, well organised into 30 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so derisk-measurement-advisor is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

derisk-measurement-advisor compared with similar skills

All 4 of these similar skills score higher than derisk-measurement-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
derisk-measurement-advisor (this skill)by deanpeters867.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install derisk-measurement-advisor?
Run npx skills add deanpeters/Product-Manager-Skills --skill derisk-measurement-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does derisk-measurement-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is derisk-measurement-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is derisk-measurement-advisor still maintained?
The repository was last updated about 3 months ago, so derisk-measurement-advisor is actively maintained.

name: derisk-measurement-advisor argument-hint: "[product or AI idea]" description: Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions. intent: >- Guide product managers through a structured risk scan across 10 dimensions — 4 internal (Desirability, Usability, Feasibility, Viability) and 6 external (Political, Economic, Social, Technological, Environmental, Legal) — to identify the most important things to measure, test, or track before committing to a product or AI idea. Each surfaced risk gets triaged into act on immediately or start tracking, producing a prioritized risk register with concrete next steps. type: interactive best_for:

  • "Stress-testing an AI or product idea before putting it on the roadmap"
  • "Identifying the cheapest tests to run before committing teams and budget"
  • "Scanning for external forces that could blindside your product plans"
  • "Building a risk register with clear act-now vs. watch-and-track priorities" scenarios:
  • "I have an AI product idea. What should I measure before we commit?"
  • "Help me figure out what risks to act on now vs. track over time"
  • "We're about to put this on the roadmap. What could go wrong internally and externally?"
  • "Is this idea worth the squeeze? What should we test first?" estimated_time: "15-20 min" theme: validation-experiments

Purpose

Guide product managers through identifying the most important things to measure, test, or track across 10 risk dimensions — 4 internal and 6 external — then triage each into act on immediately or start tracking. The output is a prioritized risk register that tells you what to do first, not just what could go wrong.

This is not a generic risk list. It's a guided scan tied to your specific product, customer, and market context. The question it answers: is the orange worth the squeeze?

Input

Works best with: The product or AI idea you want to stress-test. Also useful: Its stage (concept, prototype, in-market), what you've already validated, and any dimensions you already know are risky.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The advisor opens by asking for the idea in a sentence or two, then scans the 10 risk dimensions against it.

Example invocation: De-risk this: an AI agent that auto-drafts insurance claim responses for adjusters — prototype stage, no compliance review yet.

Key Concepts

Two Lenses, One Question

Every product idea carries two kinds of risk. Most PMs check one and ignore the other.

Internal risks ask whether the product itself will work:

  • Product Outcome Metrics (Desirability + Usability) = "What's in it for the customer/user?"
  • Business Outcome Metrics (Feasibility + Viability) = "What's in it for our business/organization?"

External risks ask whether the world will let it work:

  • PESTEL forces (Political, Economic, Social, Technological, Environmental, Legal) = "What could blindside us?"

The single triage question that applies to both sides: Do I act on this now, or start tracking it?


The Internal Risk Framework (DUFV)

Adapted from Marty Cagan's four product risks, split into two measurement categories:

| Category | Dimension | Core Question | |----------|-----------|---------------| | Product Outcome Metrics | Desirability | Will customers value it enough to buy it? | | Product Outcome Metrics | Usability | Will customers figure out how to use it? | | Business Outcome Metrics | Feasibility | Can we build it? Can we sustain it at scale? | | Business Outcome Metrics | Viability | Will it work as a viable business? |

Product Outcome Metrics answer: What's in it for the customer/user? They measure whether the product is solving meaningful problems and delivering value to its intended users.

Business Outcome Metrics answer: What's in it for our business/organization? They measure how effectively and reliably the product supports a seamless customer experience while remaining feasible to deliver.

The connection to positioning: Product Outcome Metrics validate your Problem Positioning Statement (the customer promise). Business Outcome Metrics validate your Problem Framing Statement (the business case).


The External Risk Framework (PESTEL)

Six categories of forces outside your organization that can reshape, delay, or kill your product plans:

| Category | What It Covers | Example Risk | |----------|---------------|--------------| | Political | Government policies, trade regulations, political priorities | New AI safety rules for state contractors | | Economic | Market conditions, funding, inequality, supply chains | VC AI funding dries up — focus shifts to profitability | | Social | Demographics, sentiment, digital literacy, cultural shifts | AI accused of bias — can you prove fairness? | | Technological | Platform dependencies, standards, competing tech | New AI model outdates yours — time for rapid innovation? | | Environmental | Energy consumption, sustainability, carbon footprint | AI criticized for carbon footprint — how to go green? | | Legal | Data privacy, compliance, IP, evolving regulations | AI deepfakes lawsuit crossfire — can you protect your product? |

Key insight from the classroom: Market conditions don't just change — they potentially change us, our business, and our products. PESTEL helps PMs categorize and respond to that change, not just observe it.


The Act/Watch Triage

Every surfaced risk gets one of two labels:

  • Act on immediately: This risk is present, material, and requires a response now — run a test, change a plan, mitigate a gap.
  • Start tracking: This risk is real but not yet urgent — monitor it, set a trigger threshold, revisit on a cadence.

The triage applies equally to internal and external risks. A desirability gap you can't answer is an "act now" just as much as a regulatory deadline. A demographic trend you see coming is a "watch" just like a feasibility concern you've already partially mitigated.

Anti-pattern: Labeling everything "act now." If every risk is urgent, none of them are prioritized. Force yourself to split roughly 40/60 act/watch.


When to Use This Skill

Use this when:

  • You have a product or AI idea and need to decide whether to commit
  • You're about to put something on the roadmap and want a structured risk check
  • You've been focused on internal risks and haven't scanned external forces (or vice versa)
  • Leadership asks "what could go wrong?" and you want a better answer than "nothing, we're good"

Don't use this when:

  • You don't have a specific product idea yet (use problem-framing-canvas first)
  • You need a deep PESTEL analysis with data and citations (use pestel-analysis component skill)
  • You've already validated the idea and need to pick a validation method (use pol-probe-advisor)
  • The idea is already in production and you're optimizing, not de-risking

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/4 and Risk Scan Qx/6)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill uses adaptive questioning to scan your product idea across 10 risk dimensions (4 internal + 6 external), triage each surfaced risk into act/watch, and produce a prioritized risk register.


Session Start: Heads-Up + Entry Mode (Mandatory)

Agent opening prompt:

"Quick heads-up before we start: this usually takes about 15-20 minutes. We'll cover 4 context questions, then scan 10 risk dimensions — 4 internal (will customers want it, can they use it, can we build it, does the business work) and 6 external (political, economic, social, technological, environmental, legal). For each risk that surfaces, we'll triage it: act now or track.

How do you want to do this?

  1. Guided mode: I'll walk through each dimension one at a time.
  2. Context dump: Paste what you know about the idea and I'll skip what's covered.
  3. Best guess mode: Give me the idea in a sentence and I'll make reasonable assumptions, labeled."

Step 0: Gather Context

Agent asks the following questions, one per turn:

Context Q1/4: "What's the product or AI idea you're evaluating? Describe it in 1-2 sentences — what it does and who it's for."

Context Q2/4: "What stage is this idea at?"

  1. Concept — we're still exploring whether to pursue it
  2. Prototype — we have something testable but uncommitted
  3. Building — we've committed and are developing it
  4. Scaling — it's live and we're growing it

Context Q3/4: "What's your primary concern right now?"

  1. Will anyone actually want this? (demand/desirability risk)
  2. Can users figure out how to use it? (usability risk)
  3. Can we actually build and sustain this? (technical/feasibility risk)
  4. Will this work as a business? (viability/business model risk)
  5. Something external could disrupt our plans (regulatory, market, competitive)

Context Q4/4: "Who is the customer — the person who would use or buy this product? Give me a job title or role, not a company name."

After Q4, agent summarizes:

"Here's what I'm working with:

  • Idea: [summary]
  • Stage: [stage]
  • Primary concern: [concern]
  • Customer: [role]

Let's scan for risks. We'll start with internal risks (Product Outcome Metrics and Business Outcome Metrics), then move to external forces (PESTEL)."


Step 1: Internal Risk Scan — Product Outcome Metrics (Desirability + Usability)

Agent introduces:

"First, let's check Product Outcome Metrics — what's in it for the customer? These measure whether the product will be valuable and usable for your customer. I'll present tests and metrics for two dimensions. For each, tell me which 2 are most critical for your product."


Risk Scan Q1/10 — Desirability: "Which of these tests or metrics matter most for validating that [customer role] will actually want [product idea]? Pick 2."

  1. Use landing pages to gauge initial interest
  2. Test engagement with explainer videos or ads
  3. Analyze signup rates from ad campaigns
  4. Observe feedback from storyboard demos
  5. Measure session times during user interactions
  6. Track feature adoption rates over time
  7. Other (describe your own)

For each selection, agent asks: "Is this something you need to act on immediately (run the test, close the gap) or start tracking (monitor over time)?"


Risk Scan Q2/10 — Usability: "Which of these matter most for validating that [customer role] can actually use [product idea] without friction? Pick 2."

  1. Watch how users interact with wireframes
  2. Use Wizard of Oz tests for usability insights
  3. Observe clarity issues from paper model feedback
  4. Track rage clicks to identify frustration points
  5. Measure drop-offs in task completion workflows
  6. Analyze time-to-complete tasks for friction points
  7. Other (describe your own)

For each selection, agent asks: "Act on immediately or start tracking?"


Step 2: Internal Risk Scan — Business Outcome Metrics (Feasibility + Viability)

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
derisk-measurement-advisor — Universal Skill: Install & Safety Check | SkillAgent