Read the piece AS the product's owner-approved buyer — believable, valuable, would they pay. Belief lives here. TRIGGER when a draft needs the buyer's reaction, a believability read, or when the Buyer Reviewer loads it for the review-as-a-buyer stage. DO NOT TRIGGER for whether a claim is technically backed (check-claims), the CTA path (cro-review), or line quality (edit-sentences).
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill buyer-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Buyer Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-buyer-review)More formats (shields.io, HTML) on the badges page.
---
name: buyer-review
description: Read the piece AS the product's owner-approved buyer — believable, valuable, would they pay. Belief lives here. TRIGGER when a draft needs the buyer's reaction, a believability read, or when the Buyer Reviewer loads it for the review-as-a-buyer stage. DO NOT TRIGGER for whether a claim is technically backed (check-claims), the CTA path (cro-review), or line quality (edit-sentences).
---
# Review as a buyer
One Process: become the buyer and react. Read the piece through the owner-approved buyer hypothesis in `Buyers.md` at the workspace root — the WHO is versioned there, so take the version the owner approved: their situation, what they already believe, what they fear, what they have tried — and Reader.md's Sophistication level, which sets how skeptical this market already is. Then answer three questions as that person, not as an editor.
Belief lives HERE. check-claims proves a claim is backed; this pass judges whether the buyer, reading it, actually believes it and wants it. A claim can be fully sourced and still not move this reader.
## 1. Believable
### Judge whether this buyer believes each promise
React to every promise and proof as the buyer would. What counts as "too big" is set by Reader.md's Sophistication level, not proof size alone — a worn, skeptical market (level 4-5) disbelieves a bare claim a fresh market (level 1-2) would take at face value. Fail the moment their internal "yeah, right" fires — a claim too big for the market's sophistication and the proof beside it, a number they would not trust, a before/after that skips the hard part. Name the line and what breaks belief.
## 2. Valuable
### Judge whether this buyer wants the outcome
Fail where the piece sells something this buyer does not care about, pitches a feature over the outcome they came for, or answers a question they were not asking. The get must be a get in their terms.
## 3. Would they pay
### Judge whether this buyer acts
Stand at the ask as the buyer and answer: would they do this, now, at this price. Name the standing objection, the missing reassurance, or the risk they will not take that stops the yes.
Verification: each of the three questions answered in the buyer's voice, citing the exact line that earns or loses them; findings named as the buyer's reaction, not as generic copy notes.
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!