Skip to content
TrustedSkillsbeta
Back to all skills

Jobs To Be Done

Checked
pmprompt·vlatest·marketing·MIT

This skill helps you understand *why* people choose a product or service by uncovering their “jobs to be done,” revealing valuable insights for marketing and strategy.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pmprompt/claude-plugin-product-management --skill jobs-to-be-done -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pmprompt

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pmprompt/claude-plugin-product-management at 3114dbe33f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3114dbe33f
Manifest
skills/jobs-to-be-done/SKILL.md
Scanned
1 file, 56 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill applies the Jobs-to-be-Done (JTBD) framework to help product teams understand why customers choose specific solutions. It guides agents to uncover the underlying progress a customer is trying to make rather than just listing surface-level features or demographics.

When to use it

  • Defining new product requirements by identifying the core functional and emotional benefits users seek.
  • Reframing marketing messages to align with the specific "jobs" customers are hiring your product to do.
  • Analyzing churn risks by understanding if a solution failed to help a user achieve their desired outcome.
  • Conducting competitive analysis to see what jobs competitors are successfully fulfilling for your target audience.

Key capabilities

  • Identifies functional, social, and emotional jobs customers need to accomplish.
  • Distinguishes between the problem a customer has and the specific job they want solved.
  • Structures insights around the context in which the job is attempted.
  • Helps articulate value propositions based on outcomes rather than features.

Example prompts

  • "Analyze our user interview transcripts using the Jobs-to-be-Done framework to list the top three jobs our customers are trying to accomplish."
  • "Help me reframe our current feature set by identifying the specific 'jobs' each feature is meant to do for enterprise clients."
  • "Generate a JTBD statement for a customer who wants to automate their weekly reporting process, including the context and desired outcome."

Tips & gotchas

Ensure you have access to qualitative data like user interviews or support tickets before running this skill; it relies on human insights rather than raw metrics. Focus on the context of the job (when and where it happens) as much as the task itself to get actionable product direction.