Write a VSL — the spoken script behind a demo or video sales letter that carries a page's selling argument aloud and hands the viewer to the page's CTA. TRIGGER when a piece is a sales video script that sells one offer. DO NOT TRIGGER for a content video (YouTube, educational) that does not close an offer (write-video-script), the page the video sits on (write-sales-page), or an email or ad (write-emails, write-ads).
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill write-vsl --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Write Vsl?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-write-vsl)More formats (shields.io, HTML) on the badges page.
---
name: write-vsl
description: Write a VSL — the spoken script behind a demo or video sales letter that carries a page's selling argument aloud and hands the viewer to the page's CTA. TRIGGER when a piece is a sales video script that sells one offer. DO NOT TRIGGER for a content video (YouTube, educational) that does not close an offer (write-video-script), the page the video sits on (write-sales-page), or an email or ad (write-emails, write-ads).
---
# Write VSL
One Process: the VSL carries the page's selling argument aloud — earn the first ten seconds, run the sales arc spoken, and hand the viewer to the page's exact CTA.
Write under the plan's Reader.md, Brief.md, and Proof.md, and the product's Voice.md, which names the WHO speaking; the script is spoken in that voice to Reader.md's Audience — the named buyer, never a generic viewer. The offer, mechanism, and proof come settled from the owner; never assume an offer mechanism he has not approved, and never stage a result the product did not produce.
## 1. Open on the stakes, not the intro
The first ten seconds decide whether the rest is watched — the viewer already pressed play, so open on the payoff Reader.md's awareness stage calls for: the sharp pain for a problem-aware viewer, the promised result for a solution-aware one, the deal and terms for a most-aware, warm-list viewer. Never a name-and-logo intro. Write the open last, once the script has shown you its strongest ten seconds.
## 2. Run the sales arc spoken
State the pain the viewer already feels, then turn it on the named mechanism — the spoken PAS or PASTOR arc. Where the video shows the product, screen-record the one job that proves the promise and narrate the outcome over the action; never read the interface. Let the proof happen on screen (the number moving, the task finishing) — a demonstration is proof.
### Show one job end to end
Pick the single flow that proves the promise and show it whole, never a tour of the menu. The viewer came to see the product solve their problem, not to watch panels get clicked.
### Keep every on-screen result real
Record the product actually producing the result. A staged result torches the page's proof the same way a fake price anchor does.
## 3. Hand off to the page's CTA
Name the next click and match the page's outcome-named CTA word for word, so the video and the page read as one argument, not two.
## 4. Hold the bar
Fifth-grade words spoken plainly, one pass by ear. No metaphors, no metaphorical verbs. Be specific — every figure traces to a fact or graded source. Never narrate the reader — reference the viewer only through a first-person carried question, a subordinate time clause of visit-proven behavior, a generic subject, or the approved possessives.
Verification: the open earns the first ten seconds off the payoff; one job is shown end to end with real results; the close matches the page's CTA word for word; no unpermitted fact or staged result appears.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!