mcpbeat Sign in

Jtbd Agent Skill

Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions.

5k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
1
copies elsewhere
how many repositories repackaged it
106
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/neurofoo/agent-skills --skill jtbd

What comes with it

16 007 bytes besides the instruction
commands/jobs.md
commands/jtbd.md
references/examples.md

The instruction itself

14 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

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.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

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.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

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.

16k tokens
Benchling Integration
by christophacham
×3

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.

14k tokens
Biopython
by christophacham
×3

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.

24k tokens

How to use it

Copy the folder

Take neurofoo/jtbd from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.