jtbd-building

Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./jtbd-building/SKILL.md

Quality

Content

64%

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

This skill provides solid, actionable JTBD frameworks with good concrete examples and a usable template. The main weaknesses are some unnecessary explanatory content (activation triggers, quotes) and missing validation/iteration guidance for the analysis process. The structure is clear but could benefit from explicit feedback loops to verify job identification accuracy.

Suggestions

Remove the 'When This Skill Activates' section - Claude can infer appropriate usage from the content itself

Add a validation step to the workflow, such as 'Test job hypothesis by asking: Would solving this job make the user switch from their current solution?'

Remove or relocate the quotes section - they explain concepts Claude already understands and don't add actionable guidance

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary elements like the 'When This Skill Activates' section (Claude knows when to apply skills) and explanatory quotes that don't add actionable value. The frameworks themselves are well-condensed.	2 / 3
Actionability	Provides a complete, copy-paste ready template with concrete examples (the milkshake case study, the weekly planning job story). The JTBD Analysis template is immediately usable with clear fill-in-the-blank structure.	3 / 3
Workflow Clarity	The checklist provides a clear sequence of considerations, but lacks explicit validation steps or feedback loops. For a design skill, there's no guidance on how to verify the analysis is correct or iterate based on findings.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline in one file. For a conceptual framework skill, this is acceptable, though the Forces Diagram and Action Templates could potentially be separate reference files for cleaner navigation.	2 / 3
	Total	9 / 12 Passed

Description

89%

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

This is a well-structured description with explicit 'Use when' guidance and good trigger term coverage for the JTBD methodology domain. The main weakness is that the capabilities could be more concrete - it describes the framework used but not the specific deliverables or actions Claude will perform (e.g., creating forces diagrams, conducting job mapping, analyzing switching behavior).

Suggestions

Add 2-3 specific concrete actions/outputs like 'create forces diagrams', 'map customer timelines', or 'analyze switching triggers' to improve specificity

Dimension	Reasoning	Score
Specificity	Names the domain (Jobs-to-be-Done theory, Bob Moesta's frameworks) and mentions actions like 'designing features' and 'identifying customer jobs', but doesn't list specific concrete actions like 'conduct switch interviews', 'map timeline of events', or 'analyze forces diagram'.	2 / 3
Completeness	Clearly answers both what ('Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks') and when ('Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests').	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'designing features', 'customer jobs', 'push/pull forces', 'hidden needs', 'feature requests'. These are terms practitioners and product managers would naturally use when seeking this type of help.	3 / 3
Distinctiveness Conflict Risk	Clear niche with distinct triggers - 'Jobs-to-be-Done', 'Bob Moesta', 'push/pull forces' are highly specific to this methodology and unlikely to conflict with generic product or feature skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: menkesu/awesome-pm-skills
Commit: 53530ef

Reviewed: 3 months 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.