ericrisco/rsc-harness / skills/landing-copy
landing-copy
VerifiedUse when writing the words on a single conversion page — the hero headline and subhead, the offer, the proof and testimonials, and one primary CTA — or diagnosing a page that gets traffic and does not convert, as a copy problem rather than a layout one. NOT the paid ad that drives the click (that is `ads`), NOT the visual layout the words sit in (that is `design`), NOT the experiment that picks the winning variant (that is `ab-testing`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.2 KB |
| evals/README.md | markdown | 1.6 KB |
| evals/cases.yaml | config | 5.5 KB |
| references/frameworks.md | markdown | 3.4 KB |
| references/page-skeleton.md | markdown | 2.5 KB |
| references/vsl-page-handoff.md | markdown | 1.4 KB |
| scripts/verify.shexecutable | script | 6.3 KB |
references/vsl-page-handoff.md
View on GitHub# A page and video that agree
Read the offer revision, funnel decision and VSL before writing. Produce a small alignment table: promise, included items, price/currency/tax wording, payment terms, guarantee, deadline, evidence IDs and destination. Record the source revision for each. A changed price invalidates earlier video/page copy until reconciled; do not silently choose the more persuasive version.
Give visitors three useful paths: watch with captions, read the essential argument, or reach the stated next action. Put meaningful button labels at points where a decision is possible. Hiding essential conditions until a timer expires is not a requirement of a VSL page. Do not add autoplay or delay checkout without a user-approved rationale and a way to access the offer without playback.
Keep private source notes separate from public copy. Pending testimonials are draft placeholders, never invented quotes. If permission is missing, omit identifying details and use a supported product demonstration where available. A quote's existence is not permission to publish it.
Deliver copy by section, a video placement/accessible-text note, the shared action label and destination, the offer revision, and an explicit list of unpublished claims. Hand layout to design, implementation to the selected stack, playback events to analytics and controlled comparisons to ab-testing. Do not claim that a text linter proves the assertions or conversion performance.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |