jobs-to-be-done

Uncover the functional, social, and emotional jobs driving customer behavior. Use when you need to understand why customers hire, switch, or abandon products — not just what they say they want.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body is a well-structured, highly actionable prompt template with clear sequencing and clean organization. Its main weaknesses are mild conceptual padding in the intro and tips, and implicit rather than explicit validation checkpoints in the workflow.

Suggestions

Trim the conceptual framing (the "Customers don't buy products" intro and the drill/hole metaphor) to assume Claude's familiarity with JTBD and keep only guidance that earns its tokens.

Add an explicit verification checkpoint within the workflow (e.g., a step that re-checks inferred jobs against stated customer quotes before finalizing the prioritization) to move from implicit to explicit validation.

Consider including one brief worked example of output for a sample product to make the expected result format unambiguous.

Dimension	Reasoning	Score
Conciseness	The prompt template is lean and actionable, but the opening framing ("Customers don't buy products — they hire them to make progress in their lives") and the drill/hole metaphor tip re-explain JTBD concepts Claude already knows, so it could be tightened.	2 / 3
Actionability	The skill provides a copy-paste-ready prompt with seven numbered analysis sections, concrete sub-questions, and explicit "Measure by:" criteria; for an instruction-only skill this is fully actionable and specific guidance.	3 / 3
Workflow Clarity	The seven numbered steps are clearly sequenced with sub-checklists and a closing verification instruction, but there are no explicit validation checkpoints or error-recovery feedback loops within the process, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	No external references are needed and the body is well-organized into intro, Prompt Template, and Tips sections; per the rubric's guidance, a self-contained skill with well-organized sections and no need for references scores 3.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 covers both what the skill does and when to use it, with a distinctive JTBD niche and explicit trigger guidance. It is slightly held back by a single action verb and trigger terms that lean on framework jargon rather than the full range of natural customer-research phrases.

Dimension	Reasoning	Score
Specificity	The description names the domain ("functional, social, and emotional jobs") but relies on a single action verb ("Uncover") rather than listing multiple concrete actions, matching the anchor for naming a domain with some actions but not comprehensive coverage.	2 / 3
Completeness	It explicitly answers both what ("Uncover the functional, social, and emotional jobs driving customer behavior") and when ("Use when you need to understand why customers hire, switch, or abandon products"), with an explicit Use-when trigger clause.	3 / 3
Trigger Term Quality	"why customers hire, switch, or abandon products" includes some natural terms users would say (switch, abandon), but "hire" is framework jargon and common variations like "churn" or "retention" are absent from the description itself.	2 / 3
Distinctiveness Conflict Risk	Jobs-to-be-done is a clear, distinct framework niche with specific triggers (hire/switch/abandon, jobs driving behavior) that are unlikely to fire for unrelated skills.	3 / 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: amplitude/builder-skills
Commit: 22b0634

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.