Back to Skills

pol-probe

Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

6,261stars760forksUpdated 8/5/2026

Security Assessment

Safe(98/100)
Security Score98/100

About pol-probe

This skill helps product managers define and document a Proof of Life (PoL) probe: a lightweight, disposable validation artifact designed to surface harsh truths before expensive development. It solves the problem of prototype theater, where teams build impressive demos that impress stakeholders but teach nothing, by forcing the validation method to match the actual learning goal and by keeping the experiment cheap enough to delete.

The skill explains what a PoL probe is and contrasts it with an MVP, laying out five essential characteristics (lightweight, disposable, narrow scope, brutally honest, tiny and focused) and five prototype flavors (feasibility checks, task-focused tests, narrative prototypes, synthetic data simulations, and vibe-coded probes) matched to the hypothesis being tested. It provides a fill-in template covering the hypothesis, the specific risk being eliminated, the chosen prototype type, target users, harsh-truth success and failure criteria, tools and stack, a build/test/analyze timeline, an explicit disposal plan, an owner, and a status checklist. If invoked without a hypothesis, it asks for the hypothesis and the riskiest assumption inside it before designing the probe, and it treats any context supplied at invocation as answers already given.

Target users are product managers, founders, and product teams who want to de-risk an idea before committing engineering time. Typical use cases include testing a pricing hypothesis, validating a new workflow automation idea, or checking demand for a feature. It is a pure planning and documentation framework with no code execution or system access.

FAQ

What is a Proof of Life probe?

A deliberate, disposable validation experiment designed to answer one specific question as cheaply and quickly as possible; it is not a product, MVP, or pilot but a targeted truth-seeking mission meant to be deleted.

How is a PoL probe different from an MVP?

A probe de-risks a single question over hours to days and is then deleted, while an MVP is the smallest shippable product increment aimed at real customers and iterated over weeks to months.

What if I don't have a fully formed hypothesis?

You can arrive empty-handed; the skill asks for the hypothesis and the riskiest assumption inside it before designing the probe.

What does the output look like?

A completed template documenting the hypothesis, risk being eliminated, prototype flavor, target users, harsh-truth pass/fail criteria, tools, timeline, disposal plan, owner, and a status checklist.

Does this skill run code or access systems?

No. It is a documentation and framework skill that helps you design and write up a validation probe; it does not execute anything.

All Files

3 files
template.md1.7 KB
View
SKILL.md10.5 KB
View
examples/sample.md4.7 KB
View

Install pol-probe

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill