CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

evidence-based-reviews

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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, dense methodology skill: concrete editorial rules with example language, a clearly sequenced workflow, and clean progressive disclosure into two self-contained reference files. Its weaknesses are minor — rhetorical color that could be trimmed for token efficiency, and validation expressed as standing rules rather than in-sequence checkpoints.

Suggestions

Trim rhetorical flourishes ('readers have learned to smell it', 'an opinion wearing a methodology costume', 'it is decoration') and compress the winding 'When NOT to use' sentence about how-to content into a one-line boundary rule — roughly 15% of body tokens could be saved without losing any guidance (conciseness).

Convert the standing honesty rules into explicit validation gates inside the Workflow: after step 5, 'Verify the block names only tiers the piece actually used', and after step 6, 'Confirm every pick carries a named drawback and no prose claim exceeds its tier' (workflow_clarity).

DimensionReasoningScore

Conciseness

Efficient overall — it never explains concepts Claude already knows — but rhetorical flourishes spend tokens on style: 'readers have learned to smell it', 'an opinion wearing a methodology costume', 'fabrication with extra steps', and the winding 'When NOT to use' sentence about how-to content. Not 5 because those passages could be tightened without losing guidance; not 3 because nothing is padded and every section delivers method rather than filler.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and executable: verification steps ('cross-check the spec against the manufacturer's current listing, note the date'), exact honesty language ('across roughly 1,400 owner reviews' vs 'owners say'; 'none claimed'), per-case schema rules ('ItemList for the picks, Article for the piece'), FTC placement specifics ('near the picks, in body-size text, before or beside the first affiliate link'), a 7-step workflow, and a fillable template with a worked example one level deep in references/methodology-block-template.md.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with a sound ordering rationale ('Set the criteria first… so the criteria cannot quietly bend toward a favored pick') and a failure-patterns list that functions as a checklist. Not 5: validation exists as rules — the block-honesty rule ('A block that claims a tier the piece did not use is the same lie') and 'Match the markup to the claims' — but the workflow sequence lacks explicit verify-before-proceeding gates.

4 / 5

Progressive Disclosure

The body is a genuine overview with two well-signaled, one-level-deep references (references/evidence-tiers.md, references/methodology-block-template.md), both verified to exist and self-contained with no further nesting; tier depth and the fillable template are appropriately split out, and the 'Reference files' section lists both with descriptions for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person, concrete, and comprehensive, explicitly answering both what the skill does and when to use it, with an extensive natural-language trigger list including synonyms. Its only weakness is mild redundancy — the 'Use this skill whenever…', 'Triggers on…', and 'Also triggers…' formulations overlap — but every clause carries routing information rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Produce honest product reviews and buying guides', 'set up a review methodology', 'add evidence disclosure to review content', 'align reviews with Google's reviews system or FTC affiliate disclosure expectations', 'decide when Review and Product schema are honest to use' — comprehensively covering every capability the skill body delivers. Not 4: there is no gap in action coverage; the verbs are specific and the domain is fully spanned.

5 / 5

Completeness

Explicitly answers both questions: what — 'Produce honest product reviews and buying guides without fabricated first-hand experience, using disclosed evidence tiers' — and when — 'Use this skill whenever the user wants to…' followed by a concrete 'Triggers on…' phrase list. This matches the 5 anchor (what AND when with concrete trigger phrases); not 4 because the when-clause is already maximally explicit.

5 / 5

Trigger Term Quality

'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' — twelve natural terms including synonyms (buying guide / best-of list; hands-on testing / we tested) plus behavioral triggers ('claims testing that did not happen'). Not 4: no natural phrasing a user would say in this domain is conspicuously absent.

5 / 5

Distinctiveness Conflict Risk

Clear niche — the evidence and disclosure layer of review content — with distinct triggers ('we tested', 'methodology block', 'best-of list', 'affiliate review site') unlikely to fire for general writing or SEO skills. Not 4: the description scopes itself to review evidence rather than content writing generally, keeping overlap risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/evidence-based-reviews/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.