Automated summary
Applies the Jobs to Be Done framework to a product, feature, or situation to surface the functional, emotional, and social jobs customers are trying to accomplish, including forces analysis and competing alternatives.
Strengths
- Produces a highly structured output (context, job statement, dimensions, forces, compensating behaviors, alternatives) that plugs straight into product discovery work
- Explicitly captures emotional and social jobs that purely functional analysis tends to miss
- Forces 'do nothing' and ad-hoc workarounds to be treated as real competitors
- The 'When [situation], I want to [motivation], so I can [outcome]' template yields a testable job statement
Limitations
- The skill gathers no evidence itself: without customer interviews or supplied input, the output stays hypothetical
- Importance and force-strength tables are filled qualitatively, with no scoring or quantitative backing
- It does not validate or prioritize the opportunity areas it surfaces
Use it during product discovery, competitive analysis, or when you need to explain why customers adopt or abandon a solution.
Skip it when you need a numerically prioritized roadmap or full marketing personas, which this framework does not deliver.
Security analysis
SafeThis skill is a pure analytical template with no declared tools, commands, network access, file operations, or executable instructions. It only asks the agent to perform a Jobs-to-Be-Done analysis and format the output, so there is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
/jtbd Analyze our new expense-reporting feature: when and why do finance teams 'hire' it, and what are they using today instead?/jtbd Run a Jobs to Be Done analysis on note-taking apps for freelance designers, including the emotional and social jobs and the forces that stop them switching./jtbd Our project management SaaS is losing SMB customers after three months. Use JTBD to map the circumstances, compensating behaviors, and competing alternatives behind the churn.name: jtbd description: Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions. user-invocable: true
Jobs to Be Done Analysis
Analyze a product, feature, or situation through the Jobs to Be Done framework to understand what customers really want.
Instructions
Identify the underlying jobs customers are trying to accomplish, including functional, emotional, and social dimensions. Consider the full context of when and why they "hire" solutions.
Output Format
Subject: [Product/feature/situation being analyzed]
The Context
When does the job arise? [Describe the triggering situation or circumstance]
Who has this job? [Customer segments or personas]
How are they currently solving it? [Existing solutions, competitors, or workarounds]
Job Statement
Core Job
When [situation], I want to [motivation], so I can [expected outcome].
Job Dimensions
Functional Job
The practical task they're trying to complete
| Job | Importance | Current Solution | |-----|------------|-----------------| | [functional job 1] | High/Med/Low | [how they do it now] |
Emotional Job
How they want to feel
| Feeling They Want | Feeling They Want to Avoid | |------------------|---------------------------| | [positive emotion] | [negative emotion] |
Social Job
How they want to be perceived
| How They Want to Be Seen | By Whom | |-------------------------|---------| | [perception] | [audience] |
Forces Analysis
Forces pushing toward change | Force | Strength | |-------|----------| | Push: Frustration with current solution | [description] | | Pull: Attraction of new solution | [description] |
Forces resisting change | Force | Strength | |-------|----------| | Anxiety: Fear about new solution | [description] | | Inertia: Comfort with current way | [description] |
Compensating Behaviors
What workarounds do people use when no good solution exists?
| Workaround | Why They Do It | What It Reveals | |------------|---------------|-----------------| | [behavior] | [reason] | [insight] |
Competitive Alternatives
Competition is anything that could be hired for this job
| Alternative | When It Gets Hired | Strengths | Weaknesses | |-------------|-------------------|-----------|------------| | [competitor] | [situation] | [pros] | [cons] | | [do nothing] | [situation] | [pros] | [cons] |
Insights
The real job is... [What you've learned about what customers actually want]
Current solutions fail because... [Gaps in existing solutions]
Opportunity areas... [Where better solutions could win]
Guidelines
- Jobs are stable; solutions change. Focus on the job, not the product.
- "Do nothing" is always a competitor
- Emotional and social jobs often matter more than functional ones
- The circumstance matters as much as the job itself
$ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/jobs-to-be-done-analysis-ms47vpa4/download' --output '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md.part' && mv '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md.part' '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md' && test -s '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/jtbd' && cp -R '.skill-downloads/jobs-to-be-done-analysis-ms47vpa4' '.claude/skills/jtbd'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/jobs-to-be-done-analysis-ms47vpa4'openskills read 'jobs-to-be-done-analysis-ms47vpa4'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/jobs-to-be-done-analysis-ms47vpa4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.