jobs-to-be-done

Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/jobs-to-be-done/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-sequenced and highly actionable with templates, prompts, examples, and quality checks, but it is verbose — re-explaining the JTBD framework Claude already knows — and its progressive disclosure is broken because the referenced `template.md` and `examples/sample.md` files do not actually exist.

Suggestions

Either create the referenced `template.md` and `examples/sample.md` and move the fill-in templates and example lists into them, or remove the dangling references and keep the content inline.

Collapse the duplicated jobs/pains/gains definitions: keep the Key Concepts overview lean and let the Application section carry the templates, removing redundant re-explanation.

Trim the generic placeholder templates ('[Task 1 customer needs to perform]') where the concrete examples and quality checks already convey the expected output.

Dimension	Reasoning	Score
Conciseness	The body re-explains a framework Claude already knows — defining functional/social/emotional jobs, pains, and gains twice (once in Key Concepts, again in Application) across ~370 lines with many redundant example blocks. It is mostly useful but could be tightened substantially; it does not reach the 'lean, every token earns its place' anchor.	2 / 3
Actionability	Provides concrete fill-in markdown templates for every category, specific 'Ask:' prompts, copy-paste-ready example outputs ('Reconcile monthly expenses for tax filing'), and per-category quality checks — concrete and actionable even without code, satisfying the instruction-skill note.	3 / 3
Workflow Clarity	A clear Step 1–5 sequence (Define Context → Jobs → Pains → Gains → Prioritize and Validate) with quality checks after each category and an explicit validate step ('Validate with data: Survey a broader audience'). The destructive/batch cap does not apply to this analysis skill.	3 / 3
Progressive Disclosure	References to `template.md` and `examples/sample.md` are signaled, but neither file exists in the bundle (no references/ or assets/ directory), so navigation is broken. The detailed templates/examples that should live in those files are instead inlined, making the SKILL.md monolithic despite decent section organization.	2 / 3
	Total	10 / 12 Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly states what the skill does and when to use it with an explicit trigger clause, and is concrete about its JTBD outputs. Its main weaknesses are trigger-term coverage gaps and overlap risk with related PM skills sharing the same 'repositioning/discovery/messaging' vocabulary.

Suggestions

Add the framework name and common user phrasings to the trigger, e.g. 'Use when running Jobs-to-be-Done / JTBD analysis, doing customer research, or clarifying unmet customer needs'.

Differentiate from sibling skills by scoping the trigger to discovery/motivation work, e.g. 'Use when uncovering why customers hire a product — not for writing the positioning statement itself'.

Consider adding 'value proposition' or 'customer needs' as trigger keywords to widen natural-language coverage.

Dimension	Reasoning	Score
Specificity	Lists concrete deliverables — 'Uncover customer jobs, pains, and gains in a structured JTBD format' names the domain plus three specific output categories and the format, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Uncover customer jobs, pains, and gains in a structured JTBD format') and when ('Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging') with an explicit 'Use when' clause, matching the top anchor.	3 / 3
Trigger Term Quality	'Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging' supplies natural PM terms, but misses common variations a user would actually say ('customer research', 'value proposition', 'what customers want') and does not surface 'jobs to be done'/'JTBD' as an explicit trigger.	2 / 3
Distinctiveness Conflict Risk	The JTBD framing is a recognizable niche, but the 'Use when' triggers ('repositioning a product', 'improving discovery and messaging') overlap territory owned by sibling skills (positioning-statement, problem-statement) that this skill explicitly feeds, so it could trigger for the wrong skill.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/jobs-to-be-done/SKILL.md
Commit: 9971018

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.