landing-page
Turn an offer into a shipped landing page with section architecture chosen by offer type and awareness level, a first screen that repeats the ad's promise word for word, a deployable build (single-file HTML or Next.js) with A/B variant routes, and an optional deploy; includes a teardown mode that scores any live page section-by-section into a prioritized rewrite plan (the conversion-audit capability), and a local section for service businesses (call-first page vs quote form vs booking, plus a phone first-screen checklist). Use when the user wants a page built, has approved copy that needs to become a working page, has ads that get clicks but no sign-ups or calls, or has a live page that isn't converting.
boringmarketer · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add boringmarketer/boring-marketing-skills --skill landing-page技能说明
name: landing-page description: Turn an offer into a shipped landing page with section architecture chosen by offer type and awareness level, a first screen that repeats the ad's promise word for word, a deployable build (single-file HTML or Next.js) with A/B variant routes, and an optional deploy; includes a teardown mode that scores any live page section-by-section into a prioritized rewrite plan (the conversion-audit capability), and a local section for service businesses (call-first page vs quote form vs booking, plus a phone first-screen checklist). Use when the user wants a page built, has approved copy that needs to become a working page, has ads that get clicks but no sign-ups or calls, or has a live page that isn't converting. when_to_use: build me a landing page, landing page for X, turn this copy into a page, ship a page, page isn't converting, tear down my landing page, landing page teardown, audit my landing page, page for my ads, ads get clicks but no sign-ups, service page that gets calls, page for my plumbing ads argument-hint: "[offer or campaign name | live URL for teardown]" metadata: boring: version: 4.1.1 layer: execution reads: [voice-profile, positioning#chosen-angle, audience#pain-language, voc, creative-kit, competitors, learnings] writes: [] optional-keys: [FIRECRAWL_API_KEY] enhances_with: - toolset: web-scrape gains: "teardown mode scores the real rendered page instead of pasted copy"
Landing Page
A landing page is an argument with a URL. /direct-response-copy owns the words;
this skill owns everything that happens to them on the way to a visitor: section
architecture, the build, the ship. "Done" is a page that renders the approved copy
verbatim, survives the 5-second test on a phone, and is one command from live. This is
the floor, not the ceiling. When the situation argues for a better path, take it and
say why.
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 landing-page
(${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this
file was read from, e.g. .agents/skills/landing-page. 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 the offer, where
the traffic comes from, and whether approved copy exists.)
If learnings.md holds relevant priors (which sections converted, form-length results,
past teardown outcomes), apply them. One line in the Sources and assumptions note, only
when a prior changed the page.
Teardown scraping uses the web-scrape capability, free either way; no spend gate applies. WebFetch reads the page as a summary. We use Firecrawl to read the real rendered page (JavaScript included) as clean text, with a free tier of 1,000 credits a month and no card. Without it, the note says the teardown worked from a summary.
Modes
| Situation | Mode | Path |
|---|---|---|
| No copy exists yet (default) | FULL BUILD | Copy phase via /direct-response-copy's method → Architecture → Build → Ship |
| Approved, scored copy exists | BUILD FROM COPY | Architecture → Build → Ship |
| A live page isn't converting | TEARDOWN | Scrape → section-by-section score → prioritized rewrite plan |
FULL BUILD copy phase: load ${CLAUDE_SKILL_DIR}/../direct-response-copy/SKILL.md
(If that sibling skill isn't installed, score without anchors and say so in one line in
the note.) and execute its method: Phase 0 VoC mining through the 7-dimension score loop.
Its scoring rules apply unchanged, run silently: build from copy that passes, never ship
below-threshold copy, and show the client the passing copy, not the scores.
If the Architecture phase below then cuts or reorders sections, update the copy file to
match before building. The copy file stays the single source the build diffs against.
Local service business? (plumber, roofer, dentist, med spa, cleaner, auto shop: the goal is a call, an estimate visit or a booking.) Run LOCAL OFFERS below before Architecture. It picks the page type and adds the phone first-screen checklist. Every other business skips it.
Iteration detection: if ./campaigns/{name}/page/ already exists, read it before
touching anything and ask: revise the page, add a variant, or rebuild. Never silently
overwrite a shipped page: copy the old one to page/.prev/ first.
ARCHITECTURE: the page earns its sections
Copy answers "what do we say." Architecture answers "what does this visitor need to
see, in what order, before they'll act". Different for every traffic source. Write
the decisions to ./campaigns/{name}/architecture.md before building: page job, each
section's one job, friction budget, and what got cut and why.
Offer type × awareness picks the sections
Name the page job first. A section list copied from "what landing pages have" is how cold-traffic pages end up with a nav full of exits and waitlist pages end up with testimonials nobody has given yet.
| Page job | Traffic reality | Keep | Cut |
|---|---|---|---|
| Cold-traffic offer (paid/social, awareness 1-3) | They didn't ask to be here; the page must make the whole argument | Pain-led hero, problem, mechanism, proof, offer, objection FAQ, closing CTA | The nav (every link is an exit), footer link farms |
| Warm-list page (email/newsletter clicks, awareness 4-5) | Trust transferred from the sender; they arrive pre-sold on the problem | Offer-led hero, what-you-get, proof, FAQ, CTA | Problem education and mechanism: re-explaining what they already believe reads as padding |
| Waitlist / pre-launch | No product proof exists yet | Vision-led hero, why-this-will-work mechanism, founder story, single-field CTA | Testimonia |