CtrlK
BlogDocsLog inGet started
Tessl Logo

jtbd-framing

The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.

67

Quality

81%

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

71%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.

A well-structured, opinionated playbook with exemplary progressive disclosure and largely actionable templates, prompts, and a 12-item checklist. Its main weakness is conciseness: the central ritual-vs-real thesis is repeated across multiple sections and the framework plus closing restate earlier detail.

Suggestions

Consolidate the repeated ritual-vs-real thesis: the intro, "Where JTBD adds clarity vs ritual", "Common failure modes", the 12-considerations framework, and the closing all restate the same insight — fold them into one authoritative section and prune the rest.

Tighten the 12-considerations framework so it adds net-new guidance (e.g. decision rules or per-consideration checks) rather than re-listing points already made in the detailed sections above.

Trim the closing section, which recapitulates the opening framing and the ritual-vs-real test without introducing new actionable content.

DimensionReasoningScore

Conciseness

The core ritual-vs-real / jobs-over-features insight is restated across roughly six sections (intro, "Where JTBD adds clarity vs ritual", "Common failure modes", the 12-considerations framework, and the closing), and the 12-considerations list plus closing largely restate the detailed sections; content is substantive and opinionated but could be tightened.

3 / 5

Actionability

Provides concrete usable artifacts — the "When [situation], I want to [motivation], so I can [outcome]" template with worked examples, specific interview prompts ("Walk me through the last time you did X"), and a 12-item audit checklist — but some sections remain conceptual framing rather than executable steps.

4 / 5

Workflow Clarity

The numbered 12-considerations framework sequences application/auditing, and the litmus tests plus the data-availability guardrail act as validation checkpoints; most checkpoints are present with minor gaps, and no destructive/batch cap applies to this analytical skill.

4 / 5

Progressive Disclosure

Each section signals a one-level-deep reference ("Detail in references/..."), all eight referenced files exist with no nested references, and a final "Reference files" section summarizes each — a clear overview appropriately split with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

91%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.

A strong, comprehensive description that clearly answers what and when with rich natural trigger terms and concrete capabilities. Slight overlap risk with adjacent product skills and topic-noun (vs action-verb) framing keep specificity and distinctiveness just below ceiling.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking"; discovery/prioritization/positioning), but frames them as topic nouns rather than the concrete action verbs of the anchor-5 example, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly states both what ("The Jobs-to-be-Done framework as applied product methodology...") and when ("Triggers on... Also triggers when a team is over-relying on feature-request lists...") with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including the full phrase, the acronym, and many synonyms ("jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation"), plus natural scenario triggers.

5 / 5

Distinctiveness Conflict Risk

Clear JTBD niche with distinct triggers, but the discovery/prioritization/positioning triggers overlap with closely related sibling skills the body itself names, giving minor overlap risk rather than minimal.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.