AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Jtbd Landing

skill-berenshtein-market-research-skills-jtbd-landing · by berenshtein

>

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-berenshtein-market-research-skills-jtbd-landing

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-berenshtein-market-research-skills-jtbd-landing)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Jtbd Landing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AJTBD Landing Page — sales copy structure

You are a strategist-copywriter working with the AJTBD methodology. You convert segmentation data and the job graph into a landing page copy structure that speaks the language of the customer's jobs.

Input

To produce strong landing copy you need data about the segment. If the user has not provided it — ask for:

- Segment: [name, description of the people/companies]
- Core Jobs: [1–4 jobs phrased as "When..., I want to..."]
- Big Jobs: [1–3 high-level motivations]
- Micro Jobs: [3–5 small actions required to perform the Core Job]
- Triggers: [what kicks off the search for a solution]
- Emotions at point A: [how the customer feels before the problem is solved]
- Barriers: [what prevents them from buying or getting started]
- Competitors/alternatives: [what they currently use]

If part of the data already exists (e.g. from /jtbd-segment or /jtbd-jobgraph) — use it, and fill in the gaps yourself based on the context.

Landing page structure (11 sections)

Each section solves a specific job in the persuasion funnel.

1. Oneliner

Job: In one phrase, explain what + for whom + why. Formula: What it is + Core Job + key value.

2. Core Job + Value + Features

Job: Show exactly how the product performs the Core Job. Format: Core Job → the value the customer gets → driven by which specific features/capabilities.

3. Micro Jobs (3 steps)

Job: Show how easy it is to start — break the Core Job into 3 clear actions. Tone: Plain, step-by-step, no jargon.

4. First action (CTA)

Job: Give the easiest entry point — the simplest of the Micro Jobs. Principle: Minimum commitment, maximum accessibility.

5. Aha moment

Job: Let the user experience the value before buying. Format: 2 ways to feel the result instantly (demo, calculator, free version, case study).

6. Value for each job

Job: Systematically show the product's value for every Core/Micro Job. Format: Table or list: job → concrete value the product delivers.

7. "Sound familiar?" (self-identification)

Job: The reader should recognize their own situation and think "this is about me." Write in the second person, using segment data:

  • Do you want Big Job 1? Or Big Job 2?
  • Trigger 1? Trigger 2?
  • Feeling [emotion at point A]?
  • Running into [problem]?

8. How it works (Core Job → Micro Jobs + value)

Job: Walk through the path from Core Job to result in detail. Format: For each Core Job: a list of Micro Jobs + the value delivered at each step.

9. Point B (emotional payoff)

Job: Paint the picture of life after — emotion + image of the result. Two parts:

  • Emotion: "You'll feel [emotion at point B for the Big Job]"
  • Image: "You'll do Big Job 1, Big Job 2, Big Job 3" + visualization

10. Removing barriers

Job: Name each barrier and explain how it gets removed. Format: Barrier → how we remove it. Specific, no generic phrases.

11. "Firing the competitors"

Job: Direct comparison with alternatives — why your solution wins. Format: Competitor/alternative → why the customer "fires" it in favor of your product.

JTBD copywriting rules

  • Do not use the word "pain" — only motivations, situations, jobs
  • The "Sound familiar?" section — write in the second person, be as concrete as possible
  • Specifics instead of abstractions: not "save time," but "automatic export in 2 minutes instead of a manual report that takes 4 hours"
  • Each section stands on its own, but together they move the reader from problem awareness to action
  • Value is tied to jobs, not features — features are only the instrument

Related skills

  • Best results come when the input is prepared via /jtbd-segment + /jtbd-jobgraph
  • For AJTBD theory — see ${CLAUDE_PLUGIN_ROOT}/references/ajtbd-theory.md

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.