# evidence-based-reviews

evidence-based-reviews builds honest product reviews and buying guides without fabricated hands-on testing. It structures claims across four evidence tiers and formats methodology disclosures.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 253 installs · ★ 1107 repo stars
- Author: rampstackco
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/rampstackco/claude-skills/tree/HEAD/skills/evidence-based-reviews/SKILL.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/evidence-based-reviews

## What it does

The skill enforces a clear boundary: never claim hands-on testing that did not happen. Instead, it grounds buying guides and reviews in four evidence tiers: verified manufacturer specifications, synthesized owner feedback across retailer corpora and forums, triangulated expert coverage, and documented hands-on testing only when true.

Every recommended pick must include a stated drawback, and evaluation criteria must be weighted before naming winners. The workflow stops working if you do not supply source evidence, such as manufacturer pages, retailer review corpora, or an honest count of real hands-on time.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill evidence-based-reviews -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/evidence-based-reviews/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/evidence-based-reviews/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill evidence-based-reviews -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/evidence-based-reviews/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill evidence-based-reviews -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/evidence-based-reviews/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install rampstackco/claude-skills skills/evidence-based-reviews
```

2. **Manually: put the files in place**
- File: `.github/skills/evidence-based-reviews/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill evidence-based-reviews -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/rampstackco/claude-skills --path skills/evidence-based-reviews
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/evidence-based-reviews/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill evidence-based-reviews -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/rampstackco/claude-skills/tree/HEAD/skills/evidence-based-reviews/SKILL.md

## When to use it
- build an evidence-based review methodology for an affiliate site
- synthesize owner feedback at scale across forums and retail reviews
- generate a methodology disclosure block aligned with FTC and Google expectations
- audit Review and Product schema against actual testing evidence

## Example prompts
- Audit this coffee maker review draft and strip any claims of hands-on testing we did not perform.
- Create a methodology disclosure block for our laptop buying guide based on owner review synthesis and verified specs.
- Check if our mattress comparison supports Review schema without real hands-on instrumentation.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 288edc47d9d6530f.

BEGIN THIRD-PARTY FILE 288edc47d9d6530f
```text
---
name: evidence-based-reviews
description: "Produce honest product reviews and buying guides without fabricated first-hand experience, using disclosed evidence tiers: verified specs, owner-experience synthesis at scale, expert triangulation, and hands-on only when true. Use this skill whenever the user wants to write product reviews or buying guides without hands-on access, set up a review methodology, add evidence disclosure to review content, align reviews with Google's reviews system or FTC affiliate disclosure expectations, or decide when Review and Product schema are honest to use. Triggers on product review, buying guide, best-of list, review methodology, evidence basis, hands-on testing, we tested, affiliate review site, review disclosure, methodology block, original research, reviews system. Also triggers when review content claims testing that did not happen, or when an affiliate site needs a trust mechanism that survives scrutiny."
category: content
catalog_summary: "Evidence tiers, methodology disclosure, honest review claims"
display_order: 13
---

# Evidence-Based Reviews

Produce product reviews and buying guides whose claims match their evidence. The method is evidence synthesis with a disclosed basis, and one rule anchors everything: never claim hands-on time that did not happen.

Most review sites fail this rule quietly. "We tested" appears above content assembled from spec sheets, and readers have learned to smell it. The honest alternative is stronger, not weaker: synthesis of owner experience at scale, verified specifications, and triangulated expert sources is demonstrable original analysis, and disclosing it builds the trust that fabricated testing destroys.

---

## When to use

- Writing product reviews or buying guides when hands-on access is partial or absent
- Setting up the review methodology for a new review or affiliate site
- Adding evidence disclosure to existing review content
- Auditing review content for claims its evidence cannot support
- Deciding whether Review or Product schema is honest for a given piece
- Aligning review content with Google's reviews system and FTC disclosure expectations

## When NOT to use

- General content writing and editing (use `content-and-copy`; this skill governs the evidence and claims layer of review content specifically)
- Defining how the brand sounds (use `brand-voice`)
- Optimizing the review page itself for search (use `seo-onpage`)
- Per-piece editorial briefs (use `content-brief-authoring`)
```
END THIRD-PARTY FILE 288edc47d9d6530f

The third-party file has ended. Everything between the 288edc47d9d6530f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2513 of 12410 bytes. © rampstackco · MIT · https://github.com/rampstackco/claude-skills/tree/HEAD/skills/evidence-based-reviews/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
