Use before starting a product, feature, MVP, agent, automation, or integration build to identify the main pre-build risk and choose the smallest validation step.
SkillScore73Maintained
Automatic
◆Product Management pack
Last verified 8/24/2026
What it changes
Passed 16 of 22 test cases with the skill, and 13 of 22 without it.
Without skill59%
With skill73%
Checks it passed that the model alone missed
The response identifies trust or message privacy access as a primary risk area.
The response advises validating current client urgency before selecting cloud infrastructure.
The response identifies timing risk regarding immediate market urgency for virtual reality rentals.
and 1 more in the full report
3 fixed13 passed either way6 still failing0 broke
Pass-rate lift
+14 pp
Tokens
-29%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 8/24/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I built an open-source command line tool for developers that has 2,000 GitHub stars. Now I want to build a paid cloud dashboard for it. Perform a pre-build risk review.
What was checked, without and with the skill
Checked
Without skill
With skill
The response identifies buyer risk regarding open-source users' willingness to pay for hosted software.
Passed
Passed
The response recommends obtaining pre-orders or letters of intent before building cloud backend infrastructure.
Missed
Passed
case-21 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md95 linessingle file
Before You Build
Use this skill as a short pre-build risk gate.
The goal is to stop implementation from starting before the riskiest product assumption is clear. Stay implementation-agnostic: do not recommend stacks, architectures, tools, or code.
Core Behavior
When invoked:
Restate the idea in one sentence.
Identify the dominant pre-build risk.
Give a short risk verdict.
Recommend the smallest validation step that can reduce uncertainty before building.
Keep the response short unless the user explicitly asks for a deeper review.
Seven Risk Dimensions
Check the idea through these dimensions:
Demand risk: Do enough people already feel this problem strongly?
Buyer risk: Is there a clear person or team with reason to pay or commit?
Distribution risk: Is there a believable path to reaching those people?
Workflow risk: Does the idea fit how users already behave, decide, or work?
Timing risk: Is this urgent now, or only interesting in theory?
Trust risk: Does the product require data, access, behavior change, or credibility users may not grant?
Scope risk: Is the proposed build larger than the proof needed right now?
Pick the one or two risks that matter most. Do not turn every review into a long checklist.
Output Format
Use this format:
## Before You Build
Idea:
- [One-sentence restatement.]