When should you use it?
- Before publishing a landing page
- When an assistant has polished your copy
- Reviewing a teammate's cold email
Not for: Regulated claims that need legal sign-off; Copy where you have no evidence at all yet
What do you need, and what do you get?
You need
- The draft copy
- Which format the copy is written for
- Any real metrics or case studies you can cite
You get
- Rubric scores with reasons
- A list of unsupported claims
- A rewrite that keeps only defensible statements
How does it work, step by step?
- Name the formatTell the evaluator what kind of copy it is, since brevity is good in an email and weak in a deck.
- Score firstHave one prompt score the draft and list every claim lacking proof.
- Cap without evidenceIf no real metric is provided, keep the specificity score capped.
- Rewrite in a separate passA second prompt rewrites, describing what the product does instead of inventing results.
- Check the rewriteMake sure no new numbers appeared and the call to action still fits the format.
The prompt
Our own prompt, inspired by rgb1903 on Hacker News and written to work in ChatGPT, Claude and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Audit this {copy_type} copy. Copy: {copy} Evidence I can cite: {evidence} Pass 1: score clarity, specificity and credibility from 1 to 10 with one reason each; cap specificity at 7 if no evidence is given; list every claim that lacks proof. Pass 2: rewrite so each unproven claim describes what the product does instead. Add no new numbers.
Inspired by rgb1903 on Hacker News: Show HN: PrecisionAudit, a dual-agent copy audit. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The same prompt that wrote the hype is lenient when grading it; use a separate evaluator.
- A rewriter can sneak new numbers in; scan for digits after every pass.
Our take
Assistants inflate copy by default, and the inflated version often reads better, which is why fake percentages slip through. The structural answer is an evaluator with a hard ceiling when evidence is missing, and a rewriter forbidden from inventing proof. Separate brand voice from evidence rules. rgb1903's key choice is separating the grader from the rewriter. The prompt that wrote hype tends to be lenient when asked to judge it, so use a distinct evaluator with a rubric for the specific format, since brevity is good in a cold email and thin in a deck. Holding specificity at seven out of ten when no real metric is supplied stops invented numbers from scoring well. The rewriter's rule is just as important: describe what the product does rather than inventing results. After every pass, scan for digits that were not there before. Regulated claims still need legal sign-off, and copy with no evidence at all needs proof gathered first.
Where the time goes back: Unsupported claims get caught before a prospect reads them, and the rewrite is ready to paste.
FAQ
Do I need the PrecisionAudit app?
What counts as proof?
Source and credit
Inspired by rgb1903 on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Show HN: PrecisionAudit, a dual-agent copy audit
- Creator
- rgb1903 on Hacker News
- Published on
- Hacker News
- Original date
- Mar 3, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.