Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Matches a hypothesis and its risk to one of five Proof of Life probe types instead of defaulting to whichever tool you already know.
Install Proof of Life Probe Selector
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pol-probe-advisor .claude/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .claude/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pol-probe-advisor .agents/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .agents/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pol-probe-advisor .cursor/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .cursor/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/pol-probe-advisor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pol-probe-advisor .gemini/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .gemini/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pol-probe-advisor .github/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .github/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills pol-probe-advisor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pol-probe-advisor .opencode/skills/pol-probe-advisor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pol-probe-advisor" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/pol-probe-advisor into .opencode/skills/pol-probe-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pol-probe-advisor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pol-probe-advisor- GitHub stars
- 7.2k
- Used in
- 1 other repo
- Token cost
- ~5.3k tokens
- SKILL.md length
- 2,595 words
- Files
- 1
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Matches a hypothesis and its risk to one of five Proof of Life probe types instead of defaulting to whichever tool you already know.
- Works in 10 steps: Gather Context → Identify the Core Question → Recommend PoL Probe Type → …
- Unsure which validation method fits a specific hypothesis
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Picking a validation method by tooling comfort, reaching for Figma because you know Figma rather than because it answers the actual risk, is the failure mode this guards against. It works backwards from the hypothesis to ask what specific risk needs eliminating and what the cheapest path to a harsh truth looks like, then matches the answer to one of five probe flavors: a feasibility check, a task-focused test, a narrative prototype, a synthetic data simulation, or a fifth option for cases the first four don't cover, each with its own core question, best-fit situation, and typical timeline.
When your agent uses it
- Unsure which validation method fits a specific hypothesis
- Choosing between a feasibility check and a task-focused test
- Matching available time and resources to a probe type
Example prompts
- “Which probe fits: mid-market HR teams trusting AI-drafted job descriptions, 2 weeks, no eng support?”
- “We have 3 days and no engineering access, what should we test?”
- “Pick a probe for validating whether users will pay for this before we build it.”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Gather Context
- Identify the Core Question
- Recommend PoL Probe Type
- Apply Component Skill
- Refine or Iterate (Optional)
- Choosing Based on Tooling Comfort
- Defaulting to Code
- Confusing Vibe-Coded Probes with MVPs
- Testing Multiple Things at Once
- Skipping Success Criteria
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
deanpeters.substack.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Proof of Life Probe Selector loads about 5.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 2,595 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,595 words (~5,284 tokens).
“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…”
- name
- pol-probe-advisor
- argument-hint
- [hypothesis or risk]
- 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…
- 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…
- 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…
- theme
- validation-experiments
- estimated_time
- 15-20 min
Files
Just SKILL.md in skills/pol-probe-advisor of deanpeters/Product-Manager-Skills.
Open the folder on GitHubat commit 1b5a524
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in deanpeters/Product-Manager-Skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Proof of Life Probe Selector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Proof of Life Probe Selector this skilldeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~5.3k | Automated safety check: Pass | Custom licence | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Idea Validatoraakashg/pm-claude-skills | 112 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Triagejoa23/linear-cli | 144 | — | ~699 | Automated safety check: Pass | MIT | |
| Define Opportunity Treeproduct-on-purpose/pm-skills | 716 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Topissuesfullsend-ai/fullsend | 150 | — | ~523 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Idea Validator
aakashg/pm-claude-skills
A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.
Triage
joa23/linear-cli
Triage and prioritize Linear backlog issues using the linear CLI.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Topissues
fullsend-ai/fullsend
Build a merged RICE priority table: top unassigned backlog issues plus issues assigned to the current user.
Super Product Owner
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoUser Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
TAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Related
Categories
Questions about Proof of Life Probe Selector
What does Proof of Life Probe Selector do?
Matches a hypothesis and its risk to one of five Proof of Life probe types instead of defaulting to whichever tool you already know. Picking a validation method by tooling comfort, reaching for Figma because you know Figma rather than because it answers the actual risk, is the failure mode this guards against. It works backwards from the hypothesis to ask what specific risk needs eliminating and what the cheapest path to a harsh truth looks like, then matches the answer to one of five probe flavors: a feasibility check, a task-focused test, a narrative prototype, a synthetic data simulation, or a fifth option for cases the first four don't cover, each with its own core question, best-fit situation, and typical timeline.
When should I use Proof of Life Probe Selector?
Proof of Life Probe Selector fits situations like: unsure which validation method fits a specific hypothesis; choosing between a feasibility check and a task-focused test; matching available time and resources to a probe type.
How do I install Proof of Life Probe Selector in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a claude-code`. Or copy the skill folder (skills/pol-probe-advisor in deanpeters/Product-Manager-Skills) into .claude/skills/pol-probe-advisor in your project. Claude Code loads it when a task matches its description.
How do I install Proof of Life Probe Selector in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a codex`. Or copy the skill folder (skills/pol-probe-advisor in deanpeters/Product-Manager-Skills) into .agents/skills/pol-probe-advisor in your project. Codex loads it when a task matches its description.
Can I use Proof of Life Probe Selector in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill pol-probe-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pol-probe-advisor, .gemini/skills/pol-probe-advisor, .github/skills/pol-probe-advisor and .opencode/skills/pol-probe-advisor in your project.
What does Proof of Life Probe Selector need to run?
SKILL.md names no scripts, command-line tools or credentials: Proof of Life Probe Selector is instructions for the agent only.
Does Proof of Life Probe Selector access the network?
SKILL.md names 1 domain. As links in the text: deanpeters.substack.com. This is read from the text; nothing was executed.
Is Proof of Life Probe Selector safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Proof of Life Probe Selector use?
Proof of Life Probe Selector has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Proof of Life Probe Selector use?
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Proof of Life Probe Selector?
Skills that share tags, products or a category with Proof of Life Probe Selector: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Idea Validator (aakashg/pm-claude-skills, 112 stars), Triage (joa23/linear-cli, 144 stars) and Define Opportunity Tree (product-on-purpose/pm-skills, 716 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Proof of Life Probe Selector?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.