pol-probe
by deanpeterspol-probe helps you define a Proof of Life probe to test a risky hypothesis cheaply before building real product. Use the pol-probe skill to reduce prototype theater, set harsh success criteria, choose the right probe type, and plan disposal after learning.
This skill scores 83/100, which means it is a solid directory listing candidate for users who want a structured way to define and run Proof of Life probes before building. The repository gives enough concrete workflow guidance, examples, and constraints for an agent to trigger it with less guesswork than a generic prompt, though it still lacks supporting automation files and install-time scaffolding.
- Strong triggerability: the frontmatter clearly defines when to use it, with scenarios like pricing hypotheses and workflow automation validation.
- Operational clarity: the template and examples show a concrete PoL probe structure, including hypothesis, risk, prototype type, success criteria, and disposal plan.
- Good agent leverage: the guidance explicitly distinguishes PoL probes from MVPs and prototype theater, helping agents avoid building the wrong thing.
- No install command or support files, so adoption will rely on reading SKILL.md rather than setup automation.
- Marked experimental/test signal and no references/resources, so users should treat it as a lightweight framework rather than a mature, tool-integrated skill.
Overview of pol-probe skill
What pol-probe is for
The pol-probe skill helps you define a Proof of Life probe: a disposable validation artifact used to test a risky hypothesis before you spend real build effort. It is best for teams that need a fast, falsifiable answer, not a polished MVP.
Who should use it
Use the pol-probe skill if you are a product manager, founder, designer, or engineer trying to decide whether an idea is worth building. It is especially useful for pol-probe for Prototypes when you want to avoid prototype theater and focus on learning, not impressing.
Why it stands out
This skill pushes for narrow scope, harsh success criteria, and a disposal mindset. The real value is decision quality: it helps you separate feasibility checks, task-focused tests, narrative prototypes, synthetic simulations, and vibe-coded probes so you pick the right kind of experiment.
How to Use pol-probe skill
Install and inspect the right files
Use the pol-probe install flow from your skill manager, then open skills/pol-probe/SKILL.md first. Also read template.md and examples/sample.md before writing your own probe. There are no supporting scripts or reference folders here, so the main value is in the core skill file plus the template and examples.
Turn a vague idea into a usable prompt
A weak input says: “Help me validate this feature.” A better prompt says: “Create a PoL probe for reducing checkout friction among first-time SMB buyers. The risk is that form length causes abandonment. We need a 2-day, low-cost test with pass/fail criteria and a disposal plan.” The pol-probe usage improves when you state the hypothesis, risk, audience, and what failure would mean.
What the skill needs from you
Give it a single hypothesis, one primary risk, the audience, time budget, and the cheapest test method that can still produce a hard answer. If you omit these, the skill can drift into general prototype advice instead of a real probe plan. For best results, include constraints like timeline, available tools, and the decision you will make after the test.
Practical workflow
Start with the hypothesis, then choose the probe type, then define success criteria that can prove you wrong, not just confirm hope. Finish with timeline and disposal plan. That sequence matters because pol-probe guide output is only useful when it forces a clean experiment design rather than a broad concept brief.
pol-probe skill FAQ
Is pol-probe for prototypes or MVPs?
It is for validation probes, not MVPs. If you are trying to launch something durable, this is the wrong tool. If you are trying to learn whether a risky assumption is true, pol-probe for Prototypes is a strong fit because it keeps the work deliberately temporary.
What makes it different from a normal prompt?
A normal prompt may generate ideas or a draft artifact. The pol-probe skill is more opinionated: it asks for a falsifiable hypothesis, a specific risk, and a disposal plan. That structure makes the output more actionable when you need a decision, not just a concept.
Is it beginner friendly?
Yes, if you can name the thing you are trying to prove or disprove. Beginners usually struggle when the goal is too broad. If you can define one assumption and one test, the skill will help you shape it into a realistic probe.
When should I not use it?
Do not use it when you already know the solution, when you need production-grade architecture, or when the goal is stakeholder presentation rather than learning. It is also a poor fit for fuzzy discovery work that has no clear success or failure signal.
How to Improve pol-probe skill
Provide sharper inputs
The biggest improvement comes from making the hypothesis measurable. Instead of “users will like it,” say “first-time users can complete the flow in under 2 minutes with fewer than two errors.” Strong inputs make the pol-probe usage output more testable and less generic.
Choose the right probe type early
If your risk is technical, use a feasibility check. If the risk is comprehension, use a task-focused test. If you need stakeholder alignment, a narrative prototype may be better. Picking the wrong type is one of the main failure modes in pol-probe because it leads to the wrong evidence.
Write for failure, not confirmation
The skill works best when you ask what result would force you to stop, change direction, or narrow scope. Include explicit fail conditions, a small sample size, and a disposal rule. That improves the usefulness of the pol-probe guide because it turns optimism into a decision framework.
Iterate after the first run
After the first probe, revise the hypothesis based on what you learned, not what you hoped. If the result is ambiguous, tighten the audience or reduce the scope of the test. If the result is negative, capture the lesson and delete the probe instead of polishing it into an MVP.