Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add assimovt/productskills --skill jtbd-analysisgit clone --depth 1 https://github.com/assimovt/productskillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/assimovt/productskills/jtbd-analysis)<a href="https://agentmods.dev/skills/assimovt/productskills/jtbd-analysis"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/jtbd-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/assimovt/productskills/jtbd-analysis"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/jtbd-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.00761 |
| Opus 5 | $0.00026 | $0.00380 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
jtbd-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Understand why customers "hire" and "fire" products. JTBD (Christensen/Moesta) reframes competition: you're not competing against similar products, you're competing against whatever the customer currently uses to get the job done — including doing nothing.
Job Statement Format
Structure every job as: "When [situation], I want to [motivation], so I can [expected outcome]."
- "When I finish a customer call, I want to capture key insights quickly, so I can share them with my team before I forget the context."
- NOT: "Users want better note-taking." (Too vague, no situation, no outcome.)
The situation is critical — the same person has different jobs in different contexts.
Forces of Progress
Four forces determine whether someone switches to your product. Map all four:
DRIVING ADOPTION RESISTING ADOPTION
================ ==================
Push: Pain with current solution Anxiety: Fear of the new solution
Pull: Attraction of new solution Habit: Comfort with current way
Push (away from current solution)
What's broken or frustrating about how they do it today? Stronger push = more urgency.
- "I spend 3 hours every week manually copying data between tools."
Pull (toward your solution)
What's attractive about the new way? This is your value proposition.
- "Automatic sync means I never copy data again."
Anxiety (about the new solution)
What are they afraid of? Switching costs, learning curves, data migration, reliability.
- "What if the sync breaks and I lose data?"
Habit (of the current solution)
What keeps them doing it the old way? Muscle memory, sunk costs, "good enough."
- "I've built all my templates in the current tool over 2 years."
To win: Push + Pull must be stronger than Anxiety + Habit.
If anxiety is high, reduce it (free trials, migration tools, guarantees). If habit is strong, find the trigger moment when the current solution fails hard enough to break inertia.
Conducting JTBD Analysis
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 71 lines · 53 tokens per session scan A 5949cf51fc9c
jtbd-analysis is a skill published in the GitHub repository assimovt/productskills (68 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 761 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prd-taskmaster
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…
handoff
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…
generate
Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholdersfound, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis…
discover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the…
execute-fleet
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…