sundial-org/awesome-openclaw-skills

jtbd-analyzer

Uncover the real "job" customers hire your product to do.

First seen Jun 18, 2026

Installation

$ npx skills add sundial-org/awesome-openclaw-skills --skill jtbd-analyzer

Summary

  • Uncover the real "job" customers hire your product to do.
  • Goes beyond features to understand functional, emotional, and social motivations.
  • Use when user says "jobs to be done", "jtbd", "why do customers", "what job", "customer motivation", "what problem", "user needs", "why do people buy".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sundial-org/awesome-openclaw-skills · top by installs.

npx skills add sundial-org/awesome-openclaw-skills

Browse all from sundial-org/awesome-openclaw-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 660
License LICENSE
Default branch main
Open issues 12
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,101 B
  • docs SUMMARY.md 312 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Jobs-To-Be-Done Analyzer

The Core Concept

Customers don't buy products. They HIRE products to do a job.

"People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family.

The Three Job Dimensions

Dimension Question Format
Functional What task needs doing? "Help me [verb] [object]"
Emotional How do I want to feel? "Make me feel [emotion]"
Social How do I want to be seen? "Help me be seen as [quality]"

The Process

  1. Job Statement: "When [situation], I want to [motivation], so I can [outcome]"
  2. Map all 3 dimensions for each user type
  3. Find real competition: What ELSE could do this job?
  4. Prioritize: Which jobs are most critical and underserved?

Output Format

PRODUCT: [What you're analyzing]

For [User Type]:
JOB: "When [situation], I want [motivation], so I can [outcome]"

📋 FUNCTIONAL: [Task to accomplish]
💜 EMOTIONAL: [Feeling desired]
👥 SOCIAL: [Perception desired]

ALTERNATIVES: [What else could do this job?]
UNDERSERVED: [What part isn't done well?]
PRIORITY: Critical / Important / Nice-to-have

Key Questions

  1. "What were you trying to accomplish when you [action]?"
  2. "Walk me through the last time you needed to [job]"
  3. "What would you do if [product] didn't exist?"
  4. "What's frustrating about how you currently [job]?"

Integration

Compounds with:

  • first-principles-decomposer → Decompose job to atomic need
  • cross-pollination-engine → Find how others solve similar jobs
  • app-planning-skill → Use JTBD to inform features

See references/examples.md for Artem-specific JTBD analyses