Jtbd Analyzer

v1.0.0

Uncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations. Use when user say...

0· 40·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for marjoriebroad/qui-jtbd-analyzer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Jtbd Analyzer" (marjoriebroad/qui-jtbd-analyzer) from ClawHub.
Skill page: https://clawhub.ai/marjoriebroad/qui-jtbd-analyzer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install qui-jtbd-analyzer

ClawHub CLI

Package manager switcher

npx clawhub@latest install qui-jtbd-analyzer
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the SKILL.md content: guidance, templates, and example analyses for JTBD. The skill declares no binaries, env vars, or config paths and does not request access to unrelated services or resources.
Instruction Scope
SKILL.md confines runtime behavior to asking JTBD questions, producing structured output, and showing examples. It does not instruct the agent to read local files, access credentials, or transmit data externally. It does reference integrating with other skills (e.g., first-principles-decomposer), which is a behavioral extension but is explicitly named and reasonable for this type of skill.
Install Mechanism
No install spec or code files that would be written to disk or executed; this instruction-only format is low risk and matches the skill's purpose.
Credentials
The skill requests no environment variables or credentials (proportionate). Note: example outputs and 'feature implications' mention capabilities like face recognition (product design guidance), which could imply handling sensitive user data if implemented — the skill itself does not request such access, but integrating it with other skills or product features might.
Persistence & Privilege
Flags show default behavior (not always:true, agent-invocable allowed). The skill does not request persistent or elevated privileges nor does it claim to modify other skills or system-wide settings.
Assessment
This skill appears internally coherent and low-risk because it's instruction-only and asks for no credentials. Before installing: 1) Verify the skill publisher/source (homepage is unknown) if provenance matters to you. 2) Be cautious when you combine this skill with others (the SKILL.md suggests integrations) — those other skills may request credentials or data access. 3) Do not provide sensitive user data (photos, PII, or credentials) into prompts unless you trust the downstream integrations. 4) If you plan to operationalize suggestions (e.g., face recognition), audit the concrete implementation and required permissions separately.

Like a lobster shell, security has layers — review code before you run it.

latestvk970xbthyxjb06j0phvfq0rr8585m1g8
40downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Jobs-To-Be-Done Analyzer

The Core Concept

Customers don't buy products. They HIRE products to do a job.

"People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family.

The Three Job Dimensions

DimensionQuestionFormat
FunctionalWhat task needs doing?"Help me [verb] [object]"
EmotionalHow do I want to feel?"Make me feel [emotion]"
SocialHow do I want to be seen?"Help me be seen as [quality]"

The Process

  1. Job Statement: "When [situation], I want to [motivation], so I can [outcome]"
  2. Map all 3 dimensions for each user type
  3. Find real competition: What ELSE could do this job?
  4. Prioritize: Which jobs are most critical and underserved?

Output Format

PRODUCT: [What you're analyzing]

For [User Type]:
JOB: "When [situation], I want [motivation], so I can [outcome]"

📋 FUNCTIONAL: [Task to accomplish]
💜 EMOTIONAL: [Feeling desired]
👥 SOCIAL: [Perception desired]

ALTERNATIVES: [What else could do this job?]
UNDERSERVED: [What part isn't done well?]
PRIORITY: Critical / Important / Nice-to-have

Key Questions

  1. "What were you trying to accomplish when you [action]?"
  2. "Walk me through the last time you needed to [job]"
  3. "What would you do if [product] didn't exist?"
  4. "What's frustrating about how you currently [job]?"

Integration

Compounds with:

  • first-principles-decomposer → Decompose job to atomic need
  • cross-pollination-engine → Find how others solve similar jobs
  • app-planning-skill → Use JTBD to inform features

See references/examples.md for Artem-specific JTBD analyses

Comments

Loading comments...