Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wondelai/jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do.
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 8 more in the full report
8 fixed13 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are drafting a primary job statement for our cloud backup app 'DataVault'. Draft the job statement for our target user who needs to prevent data loss during unexpected hardware failures.
| Checked | Without skill | With skill |
|---|---|---|
| Formats the job statement as 'When [circumstances], I want to [progress], so I can [outcome]'. | Missed | Passed |
| Excludes any reference to 'DataVault', cloud backup, or specific software solutions from the job statement. | Passed | Passed |
The instructions your model reads when the skill loads.
Framework for discovering innovation based on a fundamental truth: customers don't buy products -- they "hire" them to do a specific job in their lives.
Job to Be Done = the progress a customer wants to make in specific circumstances.
Key elements of the definition:
Goal: 10/10. Score 1 point per satisfied row in the Quick Diagnostic (7 rows) plus up to 3 points for depth: +1 if all three job dimensions are evidenced, +1 if the job statement avoids any product/solution name, +1 if competition includes non-consumption. Bands: 9-10 = job stated without the product, all four forces mapped, three dimensions evidenced, non-obvious competition and Little Hire tracked; 5-6 = job named but one or two diagnostic rows fail (usually missing forces or emotional/social dimensions); <=3 = product-first framing, demographic segmentation, or Pull-only thinking. Always state the current score and the specific diagnostic rows to fix.
Every job has three inseparable dimensions -- omitting any means failure:
| Dimension | Question | Example (milkshake) |
|---|---|---|
| Functional | What does the customer need to do? | Occupy myself during a boring commute |
| Emotional | How do they want to feel? | Have a small treat for myself |
| Social | How do they want to be perceived? | As a sensible parent (not buying donuts) |
Core concept: A job statement captures the progress a customer seeks in a specific circumstance, in a structured format separating context, desired progress, and expected outcome.
Why it works: Because jobs are stable while solutions churn, anchoring on the job protects a roadmap from chasing features that the next technology shift makes irrelevant.
Key insights:
test cases passed, vs 13 / 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.