Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.
npx skills add https://github.com/menkesu/awesome-pm-skills --skill jtbd-building
Claude uses this skill when:
Core Principle:
> "People don't buy products, they hire them to make progress in their lives."
The Job:
Four Forces:
PUSH (away from current):
- Pains with current solution
- Frustrations
PULL (toward new):
- Attraction to new solution
- Expected benefits
ANXIETY (hesitation):
- Fear of new
- "What if it doesn't work?"
HABIT (inertia):
- "Current way works okay"
- Switching cost
# Feature: [Name]
## The Job
**When** [situation],
**I want to** [motivation],
**So I can** [expected outcome].
### Example:
When I'm planning my week,
I want to see all my commitments in one place,
So I can feel in control and not miss anything.
## Forces Analysis
### Push (Problems with Current)
- [Current pain 1]
- [Current pain 2]
### Pull (Attraction to New)
- [Desired benefit 1]
- [Desired benefit 2]
### Anxiety (Hesitations)
- [Worry 1: "What if..."]
- [Worry 2: "What if..."]
### Habit (Inertia)
- [Current habit 1]
- [Switching cost]
## Design for the Job
### Functional
[How feature helps get job done]
### Emotional
[How feature makes them feel]
### Social
[How it affects their image]
## Address Forces
- **Reduce anxiety:** [how]
- **Overcome habit:** [how]
- **Amplify pull:** [how]
Understand Job:
Forces:
Design:
Wrong Question: "How do we make better milkshakes?"
Right Question: "What job is the milkshake being hired for?"
Discovery:
Result: Different products for different jobs
Bob Moesta:
> "People don't want a quarter-inch drill. They want a quarter-inch hole."
Clayton Christensen:
> "When we buy a product, we essentially 'hire' something to get a job done."
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take menkesu/jtbd-building from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.