jtbd-analyzer
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".
Best use case
jtbd-analyzer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using jtbd-analyzer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/jtbd-analyzer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How jtbd-analyzer Compares
| Feature / Agent | jtbd-analyzer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.
pollinations
Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images, videos, audio, vision/analysis, transcription) or mentions Pollinations. Supports 25+ models (OpenAI, Claude, Gemini, Flux, Veo, etc.) with OpenAI-compatible chat endpoint and specialized generation endpoints.