Jobs to be Done Canvas
Checked<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
product-on-purpose
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.
Automated safety checks
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 product-on-purpose/pm-skills at 1cef1a9eae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1cef1a9eae
- Scanned
- 5 files, 686 lines
About this skill
What it does
This skill utilizes the Jobs to Be Done (JTBD) framework to help define and understand user needs. It facilitates creating a "Canvas" which visualizes the circumstances, motivations, and desired outcomes that drive users to adopt a product or service. The Canvas helps uncover unmet needs and informs product development decisions by focusing on the underlying jobs customers are “hiring” products to do.
When to use it
- New Product Development: To identify the core job(s) a new product should address before building anything.
- Feature Prioritization: To understand which existing features best serve user jobs and prioritize improvements accordingly.
- Competitive Analysis: To map out competitor offerings in terms of the jobs they fulfill, revealing potential gaps or opportunities.
- Understanding Customer Churn: To analyze why customers stop using a product by examining if their original "job" is no longer being adequately served.
Key capabilities
- Canvas creation and visualization
- Identification of circumstances triggering user need
- Articulation of motivations driving job selection
- Mapping desired outcomes for each job
Example prompts
- “Create a Jobs to Be Done Canvas for users who are frustrated with managing multiple social media accounts.”
- "Help me identify the core jobs our mobile banking app is currently fulfilling."
- "I want to understand why customers are leaving our email marketing platform. Generate a JTBD canvas focused on churn reasons."
Tips & gotchas
The effectiveness of this skill relies on having good data about user behavior and motivations. Consider combining it with other research methods like user interviews or surveys for richer insights.