Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getcrew44/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.
Passed 21 of 22 test cases with the skill, and 11 of 22 without it.
and 9 more in the full report
10 fixed11 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to start an interactive consultation session to pick a validation probe for our product hypothesis. How should we begin?
| Checked | Without skill | With skill |
|---|---|---|
| The response presents facilitation entry mode choices. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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?"
| 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."
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.