pol-probe-advisor
Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Product ManagementSupported Platforms
Tags
Our assessment of pol-probe-advisor
pol-probe-advisor scores 89/100 on our quality scale, 28th of 60 Product Management skills we index (top 47%).
Its SKILL.md is 21 KB long, well organised into 34 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.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so pol-probe-advisor is actively maintained.
- Our last check on 2026-10-31 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 foundOur 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-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pol-probe-advisor compared with similar skills
All 4 of these similar skills score higher than pol-probe-advisor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pol-probe-advisor (this skill)by deanpeters | 89 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install pol-probe-advisor?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor. The install tabs above show the steps for each supported agent. - Which AI agents does pol-probe-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 pol-probe-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 pol-probe-advisor still maintained?
- The repository was last updated about 3 months ago, so pol-probe-advisor is actively maintained.
Skill content
View source on GitHubname: pol-probe-advisor argument-hint: "[hypothesis or risk]" description: Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort. intent: >- Guide product managers through selecting the right Proof of Life (PoL) probe type (of 5 flavors) based on their hypothesis, risk, and available resources. Use this when you need to eliminate a specific risk or test a narrow hypothesis, but aren't sure which validation method to use. This interactive skill ensures you match the cheapest prototype to the harshest truth—not the prototype you're most comfortable building. type: interactive best_for:
- "Choosing the cheapest useful validation method for a risky idea"
- "Matching a hypothesis to the right Proof of Life probe"
- "Avoiding overbuilding before learning the harsh truth" scenarios:
- "Which Proof of Life probe should I use to test demand for this idea?"
- "Help me pick the right validation method for an onboarding hypothesis"
- "I have a risky AI concept. What PoL probe should I run first?" theme: validation-experiments estimated_time: "15-20 min"
Purpose
Guide product managers through selecting the right Proof of Life (PoL) probe type (of 5 flavors) based on their hypothesis, risk, and available resources. Use this when you need to eliminate a specific risk or test a narrow hypothesis, but aren't sure which validation method to use. This interactive skill ensures you match the cheapest prototype to the harshest truth—not the prototype you're most comfortable building.
This is not a tool for deciding if you should validate (you should). It's a decision framework for choosing how to validate most effectively.
Input
Works best with: The hypothesis you want to validate or the risk you want to eliminate. Also useful: Your resources (time, budget, engineering access), audience access, and what failure would cost.
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 what you're trying to learn, then matches you to one of the 5 probe flavors.
Example invocation: Which probe fits? Hypothesis: mid-market HR teams will trust AI-drafted job descriptions enough to publish them; 2 weeks, no eng support.
Key Concepts
The Core Problem: Method-Hypothesis Mismatch
Common failure mode: PMs choose validation methods based on tooling comfort ("I know Figma, so I'll design a prototype") rather than learning goal. Result: validate the wrong thing, miss the actual risk.
Solution: Work backwards from the hypothesis. Ask: "What specific risk am I eliminating? What's the cheapest path to harsh truth?"
The 5 PoL Probe Flavors (Quick Reference)
| Type | Core Question | Best For | Timeline | |------|---------------|----------|----------| | Feasibility Check | "Can we build this?" | Technical unknowns, API dependencies, data integrity | 1-2 days | | Task-Focused Test | "Can users complete this job without friction?" | Critical UI moments, field labels, decision points | 2-5 days | | Narrative Prototype | "Does this workflow earn stakeholder buy-in?" | Storytelling, explaining complex flows, alignment | 1-3 days | | Synthetic Data Simulation | "Can we model this without production risk?" | Edge cases, unknown-unknowns, statistical modeling | 2-4 days | | Vibe-Coded PoL Probe | "Will this solution survive real user contact?" | Workflow/UX validation with real interactions | 2-3 days |
Golden Rule: "Use the cheapest prototype that tells the harshest truth."
Anti-Patterns (What This Is NOT)
- Not "build the prototype you're comfortable with": Match method to hypothesis, not skillset
- Not "pick based on stakeholder preference": Optimize for learning, not internal politics
- Not "choose the most impressive option": Impressive ≠ informative
- Not "default to code": Writing code should be your last resort, not your first
When to Use This Skill
✅ Use this when:
- You have a clear hypothesis but don't know which validation method to use
- You're unsure whether to build code, create a video, or run a simulation
- You need to eliminate a specific risk quickly (within days)
- You want to avoid prototype theater
❌ Don't use this when:
- You don't have a hypothesis yet (use
problem-statement.mdorproblem-framing-canvas.mdfirst) - You're trying to impress executives (that's not validation)
- You already know the answer (confirmation bias)
- You need to ship an MVP (this is for pre-MVP reconnaissance)
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/8 and Scoring Qx/5)
- 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 recommend the right PoL probe type based on your context.
Step 0: Gather Context
Agent asks:
Let's figure out which PoL probe type is right for your validation needs. First, I need some context:
1. What hypothesis are you testing? (Describe in one sentence, or use "If [we do X] for [persona], then [outcome]" format)
2. What specific risk are you trying to eliminate? Examples:
- Technical feasibility ("Can our API handle real-time data?")
- User task completion ("Can users find the 'export' button?")
- Stakeholder alignment ("Will leadership approve this direction?")
- Edge case behavior ("How does the system handle duplicate entries?")
- Workflow validation ("Will users complete the 3-step onboarding?")
3. What's your timeline?
- Hours (same-day validation)
- 1-2 days (quick spike)
- 3-5 days (moderate effort)
- 1 week+ (too long—consider breaking into smaller probes)
4. What resources do you have available? Examples:
- Engineering capacity (1 dev for 1 day)
- Design tools (Figma, Loom, Sora)
- AI/no-code tools (ChatGPT Canvas, Replit, Airtable)
- User access (10 users from waitlist, 5 beta customers, etc.)
- Budget (for UsabilityHub, Optimal Workshop, etc.)
Step 1: Identify the Core Question
Agent synthesizes user input and asks:
Based on your hypothesis and risk, which of these core questions are you really trying to answer?
Offer 5 options (aligned to probe types):
- "Can we build this?" — You're uncertain about technical feasibility, API integration, data availability, or third-party dependencies
- "Can users complete this job without friction?" — You're validating critical UI moments, field labels, navigation, or decision points
- "Does this workflow earn stakeholder buy-in?" — You need to explain a complex flow, align leadership, or "tell vs. test" the story
- "Can we model this without production risk?" — You need to explore edge cases, simulate user behavior, or test prompt logic safely
- "Will this solution survive real user contact?" — You need users to interact with a semi-functional workflow to catch UX/workflow issues
User response: [Select one number, or describe if none fit]
Step 2: Recommend PoL Probe Type
Based on user selection, agent recommends the matching probe type:
Option 1 Selected: "Can we build this?"
→ Recommended Probe: Feasibility Check
What it is: A 1-2 day spike-and-delete test to surface technical risk. Not meant to impress anyone—meant to reveal blockers fast.
Methods:
- GenAI prompt chains (test if AI can handle your use case)
- API sniff tests (verify third-party integrations work)
- Data integrity sweeps (check if your data supports the feature)
- Third-party tool evaluation (test if Zapier/Stripe/Twilio does what you think)
Timeline: 1-2 days
Tools:
- ChatGPT/Claude (prompt testing)
- Postman/Insomnia (API testing)
- Jupyter notebooks (data exploration)
- Proof-of-concept scripts (throwaway code)
Success Criteria Example:
- Pass: API returns expected data format in <200ms
- Fail: API times out, or data structure incompatible with our schema
- Learn: Identify specific technical blocker
Disposal Plan: Delete all spike code after documenting findings.
Next Step: Would you like me to generate a pol-probe artifact documenting this feasibility check?
Option 2 Selected: "Can users complete this job without friction?"
→ Recommended Probe: Task-Focused Test
What it is: Validate critical moments—field labels, decision points, navigation, drop-off zones—using specialized testing tools. Focus on observable task completion, not opinions.
Methods:
- Optimal Workshop (tree testing, card sorting)
- UsabilityHub (5-second tests, click tests, preference tests)
- Maze (prototype testing with heatmaps)
- Loom-recorded task walkthroughs (ask users to "think aloud")
Timeline: 2-5 days
Tools:
- Optimal Workshop ($200/month)
- UsabilityHub ($100-300/month)
- Maze (free tier available)
- Loom (free for basic)
Success Criteria Example:
- Pass: 80%+ users complete task in <2 minutes
- Fail: <60% completion, or 3+ users get stuck on same step
- Learn: Identify exact friction point (specific field, button, etc.)
Disposal Plan: Archive session recordings, document learnings, delete test prototype.
Next Step: Would you like me to generate a pol-probe artifact documenting this task-focused test?
Option 3 Selected: "Does this workflow earn stakeholder buy-in?"
→ Recommended Probe: Narrative Prototype
What it is: Tell the story, don't test the interface. Use video walkthroughs or slideware storyboards to explain workflows and measure interest. This is "tell vs. test"—you're validating the narrative, not the UI.
Methods:
- Loom walkthroughs (screen recording with voiceover)
- Sora/Synthesia/Veo3 (AI-generated explainer videos)
- Slideware storyboards (PowerPoint/Keynote with illustrations)
- Storyboard sketches (use
storyboard.mdcomponent skill)
Timeline: 1-3 days
Tools:
- Loom (free, fast)
- Sora/Synthesia (text-to-video, paid)
- PowerPoint/Keynote (slideware animation)
- Figma (static storyboard frames)
Success Criteria Example:
- Pass: 8/10 stakeholders say "I'd use this" or "This solves the problem"
- Fail: Stakeholders ask "Why would I use this?" or suggest alternative approaches
- Learn: Identify which part of the narrative resonates (or doesn't)
Disposal Plan: Archive video, document feedback, delete supporting files.
Next Step: Would you like me to generate a pol-probe artifact documenting this narrative prototype?
Option 4 Selected: "Can we model this without production risk?"
→ Recommended Probe: Synthetic Data Simulation
What it is: Use simulated users, synthetic data, or prompt logic testing to explore edge cases and unknown-unknowns without touching production. Think "wind tunnel testing, cheaper than postmortem."
Methods:
- Synthea (synthetic patient data generation)
- DataStax LangFlow (test prompt logic without real users)
- Monte Carlo simulations (model probabilistic outcomes)
- Synthetic user behavior scripts (simulate click patterns, load testing)
Timeline: 2-4 days
Tools:
- Synthea (open-source, healthcare)
- DataStax LangFlow (pro
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
