evidence-based-reviews

Featured

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.

Code & Development 735 stars 103 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
95
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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`) - Instructional how-to content that teaches a procedure or concept...

Details

Author
rampstackco
Repository
rampstackco/claude-skills
Created
3 months ago
Last Updated
2 weeks ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

evidence-based-copywriting

Produces and audits externally published marketing copy where factual claims must survive scrutiny — landing pages, product pages, launch emails, one-pagers, search/social metadata. Every statistic, competitor comparison, capability description, and proof point is traced to a fetched source or the project's own documents, labeled, and adversarially verified before it ships. Use when writing or rewriting high-stakes marketing copy; when copy must pass legal, compliance, brand, or claims review; when the audience is skeptical technical or executive buyers; when the company has little or no customer proof yet (pre-launch, zero customers); or when auditing existing copy for unsupported claims, invented capabilities, unverified statistics, or AI-slop language.

5 Updated 1 weeks ago
arome3
Code & Development Listed

evidence-based-copywriting

Produces and audits externally published marketing copy where factual claims must survive scrutiny — landing pages, product pages, launch emails, one-pagers, search/social metadata. Every statistic, competitor comparison, capability description, and proof point is traced to a fetched source or the project's own documents, labeled, and adversarially verified before it ships. Use when writing or rewriting high-stakes marketing copy; when copy must pass legal, compliance, brand, or claims review; when the audience is skeptical technical or executive buyers; when the company has little or no customer proof yet (pre-launch, zero customers); or when auditing existing copy for unsupported claims, invented capabilities, unverified statistics, or AI-slop language.

0 Updated 2 days ago
mucinous-riposte867
Code & Development Solid

evidence-review

Build evidence-controlled literature reviews and gap maps with source-status labels, claim registers, citation-role plans, traceability tables, and overclaim audits. Use when drafting or auditing review papers, thesis literature reviews, scoping reviews, or evidence syntheses where adjacent-domain evidence, candidate records, unpublished work, and unsupported claims must be kept separate.

29 Updated 1 weeks ago
yha9806