Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asgard-ai-platform/ux-lean-startup
Apply Lean Startup methodology — Build-Measure-Learn loop, MVP, validated learning, and pivot decisions.
Passed 21 of 22 test cases with the skill, and 17 of 22 without it.
and 6 more in the full report
5 fixed16 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a product concept for an automated invoice reconciliation assistant targeting freelance graphic designers. Can you help me create a structured Lean Startup Plan? Please outline our core underlying hypothesis that must hold true, recommend a minimal test approach with estimated effort and actionable success metrics, map out a phased iteration table tracking build, measurement, and learning stages, and set clear quantitative rules for when we should pivot versus persevere.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the exact top-level title format '# Lean Startup Plan: Automated Invoice Reconciliation Assistant' or equivalent product name | Missed | Passed |
| Recommends an actionable metric like conversion rate or activation rate rather than a vanity metric like total page views or signups | Passed | Passed |
| Proposes a low-effort MVP type such as a landing page or concierge test rather than building a functional software backend first | Passed | Passed |
The instructions your model reads when the skill loads.
IRON LAW: Validate Before You Build
Every product decision is a hypothesis. The most expensive way to test
a hypothesis is to build the full product. The cheapest is to test the
riskiest assumption FIRST with the minimum possible effort.
"Build it and they will come" is not a strategy — it's a prayer.
| MVP Type | Effort | What It Tests |
|---|---|---|
| Landing page | Hours | "Do people want this?" (signup conversion) |
| Explainer video | Days | "Do people understand and desire this?" |
| Concierge | Days | "Can we deliver value manually?" (do it by hand for 10 customers) |
| Wizard of Oz | Weeks | "Does the full experience work?" (fake the backend, real frontend) |
| Single-feature | Weeks | "Does this core feature solve the problem?" |
| Functional prototype | Months | "Can we build this and do users adopt it?" |
| Vanity (avoid) | Actionable (use) |
|---|---|
| Total signups | Activation rate (% who complete onboarding) |
| Page views | Conversion rate (% who take desired action) |
| Downloads | Retention (% who return after 7/30 days) |
test cases passed, vs 17 / 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.