К основному содержанию
скилл CX Codex

positioning-angles — скилл для Claude Code

Скилл positioning-angles для Claude Code находит маркетинговые углы подачи и формулирует офферы на основе анализа конкурентов и отзывов клиентов.

MIT ★ 778 обновлён 2026-11-16

Установить в Claude Code · Через маркетплейс плагинов Все способы и платформы ↓
/plugin marketplace add boringmarketer/boring-marketing-skills
/plugin install boring-marketing@boring-marketing-skills
Открыть на GitHub

Что делает positioning-angles

Скилл формулирует от 3 до 5 углов позиционирования с заголовками и выделяет один главный вариант. Анализ опирается на слабые места альтернатив, претензии клиентов в отзывах и формулировки конкурентов. Результаты работы сохраняются в файл ./brand/positioning.md.

В скилле действует строгое правило проверки фактов: в готовые фразы и офферы попадают только подтверждённые данные о бизнесе. Если сильная идея требует возможностей, которых у компании пока нет, скилл выносит её в отдельный список «To make this true» с описанием необходимых условий.

Скилл считывает контекст из папки ./brand/ или файла MARKETING.md через скрипт brand_context.py. При наличии ключей FIRECRAWL_API_KEY или EXA_API_KEY он выкачивает сайты конкурентов и страницы цен целиком, а не довольствуется поисковыми сниппетами.

Какие задачи решает

  • сформулировать позиционирование перед запуском продукта или страницы
  • найти отстройку от конкурентов на основе жалоб из их отзывов
  • составить оффер и гарантию без неподтверждённых обещаний
  • собрать список доработок продукта для проверки смелых гипотез

Примеры запросов агенту

  • Найди углы позиционирования для сервиса онлайн-бухгалтерии
  • Как отстроить сантехническую компанию от конкурентов в городе?
  • Почему этот оффер плохо конвертирует и как переписать заголовок?

Как установить positioning-angles

1Через маркетплейс плагинов

/plugin marketplace add boringmarketer/boring-marketing-skills
/plugin install boring-marketing@boring-marketing-skills

Команда ставит плагин boring-marketing целиком, со всеми его скиллами

2Через Skills CLI (Vercel)

npx skills add boringmarketer/boring-marketing-skills --skill positioning-angles -a claude-code

3Вручную: положить файлы

~/.claude/skills/positioning-angles/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/positioning-angles/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о positioning-angles

Как установить positioning-angles в Claude Code?

В консоли Claude Code выполните по очереди две команды: /plugin marketplace add boringmarketer/boring-marketing-skills и /plugin install boring-marketing@boring-marketing-skills.

Что делает скилл positioning-angles?

Он исследует рынок, выделяет боли аудитории, формирует 3–5 вариантов позиционирования и сохраняет готовую стратегию в файл ./brand/positioning.md.

Что нужно для работы positioning-angles?

Скилл работает автономно, но для полного парсинга сайтов конкурентов и прайс-листов можно передать ключи FIRECRAWL_API_KEY или EXA_API_KEY.

Исходный текст

SKILL.md · MIT
---
name: positioning-angles
description: Find the angle and the offer that make something sell. Researches what competitors say and pay to say, mines their bad reviews for the fears nobody answers, reads how jaded the market is, then writes 3-5 angles with one starred. Shipped lines use only verified facts, and a stronger idea the business can't back yet goes on a To make this true list with what it would take. Has a local-service mode (job types, map-pack competitors, trade guarantees). Use when launching a product or service, building an offer or lead magnet, before writing a page, or when marketing isn't converting.
when_to_use: find angles for X, how should I position X, what's the hook, why isn't this selling, we sound like everyone else, make this stand out, differentiate this, what offer should we run, write a guarantee, what makes us different, positioning for my plumbing company
argument-hint: "[product, service or offer to position, plus market or city; blank uses brand memory]"
metadata:
  boring:
    version: 4.1.1
    layer: foundation
    reads: [audience, competitors, voc, voice-profile#voice-summary, learnings]
    writes: [positioning, assets]
    optional-keys: [FIRECRAWL_API_KEY, EXA_API_KEY]
    enhances_with:
      - toolset: web-scrape
        gains: "reads competitor sites, pricing pages and review pages in full instead of from search snippets"
---

# Positioning & Angles

The same product can sell far better with a different angle. Same thing, framed around
a different fear, promise or comparison. This skill finds the frames worth
testing, grounded in what competitors say and pay to say, what customers complain about,
and what the business can actually promise. Done means 3-5 distinct angles with one
starred, each with a headline and an offer built only from verified facts, a guarantee
and a named method where the business already has them, and a short **To make this
true** list for the stronger ideas it can't back yet, written to `./brand/positioning.md`,
plus an optional ad matrix. The method is a floor, not a ceiling. When the market in
front of you argues for a better path, take it and say why in one line.

## The claim gate (hard rule)

Hunt for the bold angle. Ship only what's true. Every line someone could paste into a
page or an ad (the statement, headline, subhead, offer, guarantee and named method) uses
only facts from four places: the brief or the user's messages, the business's own site,
its reviews, and research you verified with a source. Write these down in Phase 1 as the
**fact sheet**, one fact per line with where it came from.

- **A named method describes something the business does today.** Name a step the fact
  sheet shows. Never build one from a guess about how the product could work. If nothing
  in the facts supports a method, the angle runs without one.
- **A guarantee is one the business already offers.** Otherwise it's a proposal.
- **Nothing that doesn't exist yet goes in shipped lines.** No feature on the roadmap,
  no option the product lacks, no policy the owner hasn't agreed to.
- **Keep the facts exact.** "22 techs" never becomes "22 licensed plumbers"; "most jobs"
  never becomes "every job".
- **The stronger idea still gets said.** When the best angle needs something the business
  doesn't do yet, write the shipped lines from verified facts, then add the idea to **To
  make this true**: the idea, the line it would unlock, and what it takes (a policy, a
  build, a number to check, the owner's sign-off). That list is often the most valuable
  part of the deliverable.

A claim with no source moves to To make this true or gets cut. Admitting in the output
that a claim was assumed or made up doesn't make it shippable.

Frameworks (Schwartz's stages, Hormozi's value equation, the eight generator names) are
for thinking. The deliverable says what they found in plain words: "buyers have heard
every speed promise, so show how it works", not "Stage 3, Mechanism angle".

## Context

Only if `./brand/`, `./brands/` or `MARKETING.md` exists (nothing to load otherwise), run:
`python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for positioning-angles`
(`${CLAUDE_SKILL_DIR}` is this skill's folder; outside Claude Code use the folder this
file was read from, e.g. `.agents/skills/positioning-angles`. If the script or python3 is
unavailable, read the brand folder directly: `./brands/<slug>/` when `./brands/active`
names one, else `./brand/`; then `MARKETING.md`, `preferences.md` and the files in
`reads:`. If none exist, proceed standalone and ask only for what it is, who buys it, and 2-3 competitors if known; for a local business, also the city or service area.)

If `./brand/positioning.md` already exists, this is an update session. Show the current
angle and date, then offer **refine** (re-run Phase 2, diff the landscape against what's
saved, adjust only where the market moved) or **start fresh**. On save, auto-version the
old file per the brand memory spec. If `learnings.md` holds positioning priors (an angle
or offer that won a test), apply them and say which.

## Phase 1. What's actually being sold

- **The after-state, in the customer's words.** What their life looks like after buying.
  An invoicing app sells "stop chasing clients for money", a running coach sells "a
  faster 10K without getting hurt again", a plumber sells "hot water back by dinner".
  Reviews and testimonials say it better than the founder. If you can't state it in one
  concrete sentence, get it from the user; every angle inherits it.
- **One moment at a time.** Many businesses sell several moments to different buyers: a
  SaaS has use cases, a coach has beginners and veterans, a local trade has emergencies
  and planned projects. Position the one the owner most wants more of, and say which.
- **The real alternatives**, not only competitors: do nothing, DIY, a spreadsheet, hire
  someone, a different category, a direct competitor. Each alternative's worst weakness
  is angle material.
- **What they do that customers never see.** Run the fact-sheet interview in
  `references/angle-frameworks.md` with the founder, owner or whoever delivers the work.
  Mechanisms come out of that interview more often than out of research. With no
  interview possible, the fact sheet is what the brief, the site and the reviews say.
  Write it before Phase 2; Phase 3 draws only from it.

Load `references/dunford-positioning.md` if the problem is bigger than messaging: the
wrong category, the wrong segment, or losing deals on price they should win on value.
That's a positioning problem, and Dunford's five components come before any angle.

## Phase 2. Read the market (parallel fan-out)

Angles from model knowledge are guesses. Identify 3-5 competitors (from `competitors.md`,
the user, or a search for "[category] for [audience]"; for local, see the Local section).
Run one WebSearch in the main thread first; if it's denied, write a `Data: MODEL
KNOWLEDGE` draft instead of fanning out.

We use Exa to find the competitors and "alternatives to" pages a keyword search misses
(free tier, then pay as you go), and Firecrawl to read their first screens, pricing and
review pages in full (free tier of 1,000 credits a month, no card). Without them,
WebSearch and WebFetch do the work, and a page read as a summary is labelled that way in
its evidence pack.

**One subagent per competitor, in parallel.** Each returns an evidence pack, not prose:

```
COMPETITOR: <name> · <url> · <rating + review count if any>
FIRST SCREEN: "<headline>" / "<subhead>" / "<primary CTA>"
PRICE FRAME: <posted prices, tiers, "free estimate", trial terms, or none>
PAID HOOKS: "<ad 1>" / "<ad 2>" (Meta Ad Library or Google Ads Transparency Center, <date>)
GUARANTEE: "<verbatim>" or none
COMPLAINTS: "<verbatim from 1-3 star reviews>" (<source>)
```

What a competitor pays to say is their real positioning; homepages carry old committee
compromises. Pull paid hooks from facebook.com/ads/library and adstransparency.google.com.
If a competitor runs no ads, that's a finding too.

**One complaints and VoC subagent.** If `./brand/voc.md` exists, start there. Otherwise
read the 1-3 star reviews of the top competitors and of the business itself: G2,
Capterra, app stores, Trustpilot or Amazon for products; Reddit threads for the category;
Yelp, BBB or Angi for local. Bad reviews name the exact failure buyers fear ("the
onboarding took three months", "the program ignored my knee injury", "quoted $350,
charged $900"). The most repeated fear is often the angle, and the guarantee in Phase 3
answers it. Skip login-walled hosts (Facebook, Instagram, LinkedIn) and say so.

**The AI-answer check.** Buyers increasingly ask an assistant before they look at any
site. Load `references/aeo-positioning.md` and run its prompts. Treat the consensus
description as saturated territory and its blind spots as white space.

**Merge into the landscape triage:**

- **Saturated.** Claims on 3+ competitor surfaces or in the AI consensus. Dead language
  that can sit in a trust strip but is never the angle.
- **Contested.** Claims 1-2 competitors make. Usable only with more proof or specificity.
- **White space.** A fear or axis nobody answers with a specific promise. Check that
  customers actually care (it shows up in the complaints), and that the business can
  keep the promise, before claiming it.

Label once: `Data: LIVE (n competitors, n ad-library pulls, n reviews read)`, and flag
any leg that fell back to model knowledge.

## Phase 3. The offer, the guarantee and the named method

Two businesses with the same angle can sell very differently because of the offer. Build
three pieces from the fact sheet. Each ships only if the business does it today; a piece
it could do but doesn't yet goes to To make this true with what it would take.

**The offer** is what the customer gets and on what terms. Run Hormozi's value equation:
raise the dream outcome and the buyer's belief they'll get it, cut the wait and the
effort. Most offers lose on the bottom half (setup time, the four-hour service window,
the 12 weeks before any result). Load `references/hormozi-offer.md` for offer shapes by
business type, including a section for local trades.

**The guarantee** removes the fear the complaints surfaced. Decision rule: it answers the
top complaint, and the owner confirms the business can afford it (refund rate, missed
deadlines, callbacks). A guarantee the business can't keep becomes the next bad review.
Write it as a sentence the owner would sign, with a number, a window and what happens if
they miss. If the business doesn't offer it today, the sentence goes under To make this
true with what to check first (refund rate, missed windows, callbacks) and who signs off.

**The named method** is the HOW that makes the promise believable, the answer to "why
will this work when other things haven't?" Even when nothing is proprietary, there is
often a step competitors skip or an ordinary fact nobody explains (Claude Hopkins'
Schlitz move). Find it in the fact sheet: a step the site, the reviews or the owner
describe. Never infer one from how the product might work. Name it like a method, give
the "because" in two sentences, and test it: could a competitor say this sentence
verbatim? If yes, sharpen it. No step in the facts means no named method in shipped
lines; propose one under To make this true and say what the owner would need to confirm.
Load `references/unique-mechanism.md` when the owner says "we don't really do anything
different".

## Phase 4. How jaded the market is (Schwartz, for thinking only)

Use the stage to choose generators. Never print the stage number or the word
"sophistication" in the deliverable; say what it means for this buyer. Detect the stage
from Phase 2 evidence, not vibes:

- **Stage 1.** You'd have to explain what the category is; buyers say "I didn't know that
  was possible". Announce the promise.
- **Stage 2.** Similar promises exist and are escalating (faster, more, #1). Be more
  specific than the superlatives.
- **Stage 3.** Ads sound alike and buyers say "I've tried things like this". Explain the
  mechanism.
- **Stage 4.** Competing mechanisms, ads leading with proof. Out-prove them.
- **Stage 5.** Features commoditized, one known brand wins by default. Sell identity or
  rally against an enemy.

Paid hooks are the best signal; homepages lag. AI-adjacent markets compress the ladder:
if the AI-answer check shows assistants already comparing mechanisms and proof, call it
Stage 3-4. Load `references/schwartz-sophistication.md` when the signals conflict or the
user disputes the call.

| Stage | Run first | Also viable | Skip (and why) |
|---|---|---|---|
| 1 | Transformation, Speed/Ease | Specificity | Mechanism, Contrarian. Nothing to answer yet |
| 2 | Specificity, Transformation (with numbers) | Social Proof, Speed/Ease | Contrarian. The market isn't frustrated yet |
| 3 | Mechanism, Contrarian, Specificity, Risk Reversal | Enemy | bare Speed or Transformation. Reads as the hype everyone claims |
| 4 | Mechanism with proof, Social Proof, Risk Reversal | Specificity | anything unproven |
| 5 | Enemy, Specificity as identity ("for people who...") | Contrarian | generic promises. The market stopped listening |

## Phase 5. Generate angles

Run the mapped generators against the after-state, the offer, the method, the landscape
and the customer's words. Generate broadly, keep the 3-5 strongest. Load
`references/angle-frameworks.md` when output feels thin.

The 8 generators (the trigger condition matters more than the template):

1. **Contrarian.** "Stop [common practice]. Here's what works." When the market is
   frustrated with the standard approach.
2. **Unique Mechanism.** "The [Named Method] that [result]." Stage 3 and up.
3. **Transformation.** "From [painful now] to [after-state] in [time]." When the result is
   dramatic and specific and the buyer is problem-aware.
4. **Enemy.** A problem, practice or mindset, never a competitor by name (the surprise
   bill, the setup fee, the cookie-cutter plan). When complaints share a villain.
5. **Speed/Ease.** "[Result] in [short time]" or "without [usual sacrifice]." The most
   claimed angle in most markets; use it only with a number the business keeps.
6. **Specificity.** Narrow the who or the what. "For [specific buyer] who want [specific
   result]." Beats generic incumbents, and it's the default when the brand is absent from
   the AI answers.
7. **Social Proof.** "[Specific result] for [number] [type of people]." When proof is
   strong and trust is the barrier.
8. **Risk Reversal.** The guarantee is the headline. When risk is the top objection and
   the business can afford to keep the promise.

**Quality gate.** Every surviving angle passes all seven, or it's cut or sharpened. Run
it privately; the checklist never appears in the deliverable.

1. **Sourced?** Every word of the statement, headline, offer, guarantee and method traces
   to the fact sheet. Anything that doesn't moves to To make this true.
2. **Specific?** "Better results" fails. "Paid 11 days sooner" passes.
3. **Differentiated?** Saturated claims and copies of a competitor's paid hook fail.
4. **Believable?** The method or the proof supports it.
5. **Keepable?** The business does it today, every time.
6. **Right for this buyer and moment?** Checked against audience segments and the
   customer's words.
7. **Repeatable?** It fits a headline, an ad or the side of a van in about ten words, and
   a customer could repeat it to a friend.

About three generate-and-gate passes is the ceiling. Past that the constraint is the offer
or the proof, so present the best honestly and name the test it strains.

## Local service businesses

When the business is a plumber, roofer, HVAC company, dentist, med spa, cleaner or any
business customers call from a map, adjust the method:

- **Split by job type before anything else.** Each wants a different angle.

| Job type | Example | Buyer's state | What decides the call |
|---|---|---|---|
| Emergency | burst pipe, no heat | panicked, phone in hand, calls one or two numbers | someone answers now, can come today, rough price |
| Urgent, can wait a day | failing water heater | annoyed, calls 2-3 businesses | a clear price, an arrival window, reviews |
| Planned project | repipe, new roof | researching for weeks, gets 3 quotes | proof of similar jobs, warranty, financing |

- **The competitors are whoever shows up for "[service] [city]":** the top 3 on the map,
  the Local Services Ads row, and the 2-3 businesses running search ads. Read their first
  screen as a phone visitor sees it. Google Maps pages often don't fetch; use review
  snippets from search, Yelp, BBB or Angi, or ask the user to paste.
- **Saturated in nearly every trade:** "family owned and operated", "licensed and
  insured", "24/7 emergency service", "honest upfront pricing" with no price shown,
  "quality workmanship", "fast and reliable", "free estimates", "satisfaction guaranteed".
  Trust strip only.
- **The offer often outsells the angle.** "The price on the quote is the price on the
  invoice" beats another "upfront pricing" claim. Trade offers and guarantees
  (arrival-window, price-lock, workmanship, clean-home) are in the local section of
  `references/hormozi-offer.md`.
- **Most trades sit at Stage 2-3 on claims.** Emergencies bend the stage table. Speed and
  availability decide, so a proven Speed angle leads at any stage.
- **The unspoken mechanism is the rich vein.** Every plumber runs a camera down a slow
  drain; almost none send the homeowner the video before quoting. Claim it only when this
  crew does it; if it doesn't yet, it tops the To make this true list.

## Output

Present in chat per `start-here/references/output-format.md`, in words the owner would
use:

1. The deliverable header.
2. **What the market says.** What every competitor says (skip it), what one or two say,
   and what nobody promises that buyers care about, each with one quote or example.
3. **The read.** One short paragraph: the after-state in the customer's words, what they
   do instead, the top complaint, and what it takes to be believed now ("they've heard
   every speed claim, so show how it works").
4. **The position.** Decide. The one angle that wins here: the **statement**, **why it
   wins** (the complaint or customer phrase it answers, in 1-2 sentences), the **offer** and
   the **guarantee** ("none offered today" is a fine answer).
5. **Ready to ship,** built from that position, finished and passing the claim gate:
   - the first screen: headline, subhead, button and the line under the button;
   - the next block the page needs (how it works, or the proof that backs the headline);
   - answers to the 3 objections buyers raise first, in the customer's words;
   - who it's for and who it isn't for (the buyer to turn away), plus what tends to make
     them buy now.
   The headline never rests on something you called table stakes in step 2.
6. **Other angles worth testing:** 2 or 3, one line each, saying what it claims and when it
   would beat the chosen one. No full builds.
7. **To make this true.** The stronger ideas the facts can't back yet: the idea, the line
   it would unlock, what it takes. Skip it only when there are none.
8. A short evidence note last: what the shipped lines rest on, and any leg that fell back
   to model knowledge.

When the user asked for options to choose from ("give me angles", "brainstorm
positioning"), swap steps 4 to 6 for 3-5 full angles (statement, why it lands, headline,
offer, guarantee, best for) and star one. Otherwise decide, ship, and close with one line:
"Want a different angle to lead? Say which and the pieces rebuild from it." No scoring,
gate checklists, framework names, named-method labels the business doesn't use, or script
paths in the chat output.

**On selection, write `./brand/positioning.md`.** Offer, guarantee and mechanism live
inside Chosen Angle, because other skills read only that section:

```markdown
# Positioning
Last updated: <date> by /positioning-angles

## Chosen Angle
Angle: <name>
Segment or moment: <who, which use case or job type>
Statement: <one sentence>
Offer: <what they get, on what terms, as offered today>
Guarantee: "<the sentence the business offers today>" or none offered today
Mechanism: <named method + the "because", from a step the business does today> or none
Psychology: <the fear or desire it answers, with the customer phrase>
Headline direction: "<example>"
Best for: <segments, channels>
Facts it rests on: <fact (source)>; <fact (source)>
Not yet true (keep out of copy): <idea> | needs: <what it takes>

## Market Assessment
Category: <the market customers shop in>
Market read: <what buyers have heard too often, and what it takes to be believed now>
Primary alternative: <what customers do instead>
Top complaint in the market: "<verbatim>" (<source>)
AI consensus: <how assistants frame the category; our descriptor or ABSENT>

## Competitive Landscape (as of <date>)
Saturated: <claims>
Contested: <claim, who uses it>
White space: <gaps>
Data: LIVE (<n> competitors, <n> ad-library pulls, <n> reviews read)

## VoC Language Bank
Verbatim phrases for copy. Quote them, don't paraphrase:
- PAIN: "<phrase>" (<source>)
- DESIRE: "<phrase>" (<source>)
- OBJECTION: "<phrase>" (<source>)

## Angles Explored
### <Angle 1> (selected) / ### <Angle 2> ...
- Statement / Headline / Offer (one line each)
```

Update `brand.yaml`; version any prior file to `./brand/.history/`.

## The 12-ad testing matrix

After the angle is chosen, offer once: "Want the testing matrix? 4 hooks x 3 formats = 12
ads, saved for /creative and /paid-ads." Default yes when the user mentioned ads. Save it
to disk; cell IDs only pay off when downstream skills and /performance-review read them.

The shared contract is `start-here/references/schemas/ad-matrix.schema.json` (`${CLAUDE_SKILL_DIR}/../start-here/references/schemas/ad-matrix.schema.json`). Rows are 4 hooks from the
chosen angle: `direct`, `question`, `proof`, `contrarian`. Columns are 3 formats: `static`,
`video`, `carousel`. Cell IDs are `MA-H{1-4}-{A-C}` (A static, B video, C carousel). Each
cell holds hook text for the format, a one-sentence visual, primary text with a customer
phrase, and a CTA. Every cell passes the claim gate. Write
`./campaigns/<campaign-name>/ad-matrix.md` (readable grid plus per-cell detail) and `ad-matrix.json` (`{ "angle", "campaign", "created", "source":
"positioning-angles", "cells": [ { "id": "MA-H1-A", "hook_type": "direct", "format":
"static", "hook", "visual", "primary_text", "cta" }, ... ] }`, all 12 cells). Append both
to `./brand/assets.md`. Assets get named by cell ID (`MA-H2-B-9x16-v1.mp4`).

## Worked examples (all research illustrative)

These show the reasoning, so they name stages and generators. The deliverable says the
same things in plain words.

**Local service: Hartline Plumbing, Dallas TX (a sample business).** Water heater
replacements, an urgent job type. The plumbers on the map all say "upfront pricing" and
"same-day service"; two advertise "$50 off" an unposted price; none posts an installed
price. Their bad reviews repeat "quoted one price, the bill was double". Stage 3. The crew
already photographs the heater and venting before quoting, and the final bill matched the
quote on almost every job last year, so the guarantee is affordable. Offer: same-day or
next-morning replacement at one flat installed price, haul-away and permit included.
Guarantee: "The price on your quote is the price on your invoice." Method: the
Price-Before-We-Touch-It check (the crew already does it). ★ The price-in-writing angle
(risk reversal), headline "Your water heater price in writing before we touch it."
Runner-up: the same-day angle, kept for the matrix's direct hook.

**Online service: bookkeeping for Shopify sellers doing $1-10M.** Four competitors say
"stress-free bookkeeping" and "real-time dashboards" (saturated); two pay for
"catch-up bookkeeping" ads (contested); sellers on Reddit complain "my books say I'm
profitable but my bank account disagrees", and nobody talks about inventory-aware cost
of goods (white space). Stage 3. The firm's service page says it closes by the 10th and
reconciles COGS to stock counts every month, so the offer and the method ship. Offer:
monthly close by the 10th with COGS reconciled to stock counts. Method: Inventory-Aware
Books. Guarantee: none offered today. ★ The books-versus-bank angle (mechanism),
headline "Your books say profit. Your bank says no. Here's the disconnect." To make this
true: "If your P&L and bank balance
don't reconcile within 60 days, we work free until they do." It would turn the headline
into a promise; it takes a count of last year's clients who didn't reconcile, and the
owner's sign-off.

**Claim gate in action: a specialty coffee subscription.** The bold angle is "coffee
that arrives before you run out". The site says beans ship within 48 hours of roasting
and customers choose a bag size and a delivery interval; there's no usage tracking, no
skip button and no guarantee. Shipped headline, word for word from the facts: "Shipped
within 48 hours of roasting." (Not "at your door in two days": the site promises the ship
date, not the delivery date.) To make this true: a cups-per-day picker that sets the
interval (a build), one-click skip in the account (a build), and a never-run-out promise
(the owner covers rush shipping). Together they unlock "Never run out of good coffee again."

**Creator or coach: an online running coach for runners over 40.** Competitors promise
"PR faster" and "custom plans" (saturated). Complaints in running forums: "every plan
assumes I'm 25", "got hurt in week 6". Stage 4, so proof and a mechanism lead. The
coach's sales page lists the program and already offers the refund. Offer: 12 weeks, two runs and two
20-minute strength sessions a week, with a weekly video check-in. Guarantee: "Do the
sessions for 6 weeks. If your easy pace hasn't improved, full refund." Method: the
Two-Session Strength Block. ★ The over-40 angle (specificity), headline "A faster 10K
after 40, without another injury."

## When the user edits your work

Apply the edit, then make it stick: save a gold case to `./brand/gold/<this skill>/` and
one to three yes/no checks to `./brand/checks.md`, and confirm in one line. Before handing
over any work, answer the checks the context block loaded, silently, and fix every no.
How: `${CLAUDE_SKILL_DIR}/../start-here/references/taste-loop.md`.

## What's next

- `/direct-response-copy` to write the headlines, offer and page from the chosen angle
  and the VoC bank (~15 min)
- `/landing-page` to build the page for this one offer (~20 min)
- `/paid-ads` to turn the matrix cells into campaigns (~15 min)
- `/lead-magnet` for a top-of-funnel asset that carries the angle; for a local business,
  `/google-business-profile` to put the offer where map searchers see it first (~15 min)

© James Dickerson (@boringmarketer) · MIT · boringmarketer/boring-marketing-skills

Похожие скиллы

Все скиллы по теме «Маркетинг и контент» →
positioning-ideas phuryn Скилл positioning-ideas генерирует варианты позиционирования продукта на основе анализа конкурентов. Пригодится продакт-менеджерам и маркетологам при выходе на рынок или поиске свободных ниш. CX Codex +1 3 100установок brand-positioning arnabbagxd Скилл brand-positioning помогает выделить бренд среди конкурентов, найти свободную категорию и сформулировать чёткое позиционирование. Пригодится при запуске продукта или отстройке от соперников. CX Codex +1 2 200установок asb-positioning asmartbear Скилл asb-positioning для Claude Code и Codex. Переформатирует заголовки, объявления и питчи в язык выгоды: вместо «экономит время» обещает конкретную ценность в единицах, которые считает сам покупатель. CX Codex +1 755установок narrative-baseline-mapper aaron-he-zhu Скилл narrative-baseline-mapper для Claude Code собирает текущие формулировки на ваших поверхностях и сверяет их с задуманным сообщением. Первый шаг фазы Trace и снимок «до» для измерения дрейфа. CX Codex +1 1 100установок message-system-architect aaron-he-zhu Скилл message-system-architect формирует постоянную иерархию бренд-сообщений: главное повествование, три опорные ценности и доказательства под персоны. Закладывает канон бренда в память агента. CX Codex +1 1 100установок brand-building aitytech Скилл brand-building для Claude Code разрабатывает стратегию бренда, позиционирование и голос. Включается при создании гайдлайнов, архитектуры бренда и сообщений. CX Codex +1 1установок

Из того же набора35

Весь набор →
performance-review Скилл performance-review для Claude Code диагностирует маркетинговые кампании и преобразует данные в структуру для обучения ИИ. Он сопоставляет результаты каналов с фактическими продажами бизнеса. CX Codex +1 ★ 778звёзд репо competitive-intel Скилл competitive-intel для Claude Code собирает данные о конкурентах и записывает выводы в ./brand/competitors.md. Он запускает разбор сайтов, цен и рекламы, режим наблюдения за изменениями, анализ объявлений и локальный поиск. CX Codex +1 ★ 778звёзд репо email-sequences Скилл email-sequences для Claude Code проектирует цепочки писем и SMS для онбординга, продаж и холодного аутрича. Проверяет домен отправки и сохраняет черновики. CX Codex +1 ★ 778звёзд репо social-content Скилл social-content для Claude Code пишет оригинальные посты для X и LinkedIn по вашим материалам и реальным цифрам. Помогает подготовить публикацию, оценить черновик или составить план на неделю. CX Codex +1 ★ 778звёзд репо local-seo-plan Скилл local-seo-plan для Claude Code составляет план местного SEO на 90 дней для бизнеса с выездным обслуживанием. Он выбирает страницы для услуг и городов, а также задаёт порядок работ с профилем Google. CX Codex +1 ★ 778звёзд репо keyword-research Скилл keyword-research для Claude Code превращает поисковые запросы и вопросы к ИИ в карту тем с очередью задач и готовыми брифами. Включается при планировании контента и поиске пробелов в SEO. CX Codex +1 ★ 778звёзд репо start-here Скилл start-here для Claude Code разбирает бизнес и направляет маркетинговые запросы к нужному скиллу или рабочему процессу. Он включается при первом запуске, расплывчатой задаче или подключении нового клиента. CX Codex +1 ★ 778звёзд репо ai-search Скилл ai-search для Claude Code проверяет, упоминают ли AI-ответы бизнес и ссылаются ли на его сайт. Запускается для аудита видимости, поиска причин рекомендаций конкурентов и мониторинга изменений. CX Codex +1 ★ 778звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой