CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jobs-to-be-done

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing product value propositions. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable — templates, verbatim interview scripts, copy patterns, and a diagnostic checklist make the framework immediately usable — and the reference bundle is well organized at one level deep. Its weaknesses are token efficiency (re-explaining known theory, duplicated insights, an author bio) and the absence of an explicit sequenced workflow tying the six concepts into a procedure.

Suggestions

Cut the 'Why it works' explanations, the duplicated integration/modularization lines (section 6), the 'About the Author' biography, and the affiliate-linked 'Further Reading' — Claude already knows the JTBD canon, so keep only the product-specific applications, copy patterns, and ethical boundaries that add new value.

Add a short sequenced workflow at the top (e.g., 1. Run timeline interviews, 2. Draft the job statement, 3. Map the four forces, 4. Map non-obvious competition, 5. Design metrics/roadmap around the job) with the Quick Diagnostic as an explicit validation checkpoint after each step.

Move the per-section 'Key insights' and detailed application tables into the corresponding references/ files, keeping SKILL.md as a lean overview with the templates, copy patterns, and section-level reference pointers.

DimensionReasoningScore

Conciseness

The body is well-structured with tables and tight bullets, but each of the six sections re-explains standard JTBD theory Claude already knows ("Core concept"/"Why it works", the milkshake anecdote), the integration/modularization insight is stated twice in section 6, and the author biography plus affiliate-linked "Further Reading" are pure padding. It is above 2 because the applications, copy patterns, and diagnostics are genuinely additive, but it could clearly be tightened.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a job-statement template with a worked example ("When I'm commuting alone, I want something to occupy me..."), verbatim interview question scripts ("When did you first think about looking for a solution?"), literal copy patterns, per-context application tables, and a question→if-no→action diagnostic. Specific examples cover the common cases; a 4 would imply missing key details, which is not the case.

5 / 5

Workflow Clarity

The six framework sections are conceptual modules rather than a sequenced procedure, and the practical order (interview → job statement → forces → competition → design) is only implicit. The "Scoring" section and the Quick Diagnostic table provide checkpoint-like validation, matching "steps listed but... checkpoints missing or implicit"; it is not 4 because no explicit end-to-end sequence with checkpoints is given.

3 / 5

Progressive Disclosure

Five real, one-level-deep reference files (verified to exist, with no nested references) are each signaled from the relevant section ("See: [references/innovation-process.md]") and indexed with content summaries in a "Reference Files" section. It falls short of 5 because the ~250-line body inlines substantial detail (per-section key insights, application tables, copy patterns) that could partly be deferred to the references, making it heavier than a lean overview.

4 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 is exemplary: it clearly states what the skill does, provides an extensive set of natural trigger phrases including domain jargon, and disambiguates against sibling skills. The only minor weakness is that capability coverage is phrased somewhat topically rather than as a comprehensive action list.

DimensionReasoningScore

Specificity

"Discover what customers truly need by analyzing the 'job' they hire your product to do" plus "Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps" lists several concrete capability areas. It falls short of 5 because coverage is partly topical ('Covers...') rather than a full list of specific actions, and above 3 because multiple distinct capabilities are named.

4 / 5

Completeness

It explicitly answers both 'what' (discover customer needs via job analysis; JTBD interviews, competition analysis, jobs-oriented roadmaps) and 'when' ("Use when the user mentions..." with a list of concrete trigger phrases, plus "Also trigger when..."). This matches the top anchor exactly; a 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would actually say: "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", and "functional vs emotional jobs", plus broader conditions like "investigating why users choose competitors". Coverage including book-title jargon and synonyms matches the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

Distinctive JTBD-specific triggers ("milkshake moment", "competing against luck") establish a clear niche, and explicit routing ("For product positioning, see obviously-awesome. For rapid validation, see design-sprint.") actively resolves overlap with adjacent skills. Broad terms like "product-market fit" are mitigated by this routing, keeping conflict risk minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/jobs-to-be-done/SKILL.md

Reviewed

Table of Contents

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.