review-contentlisted

# Review Content Use this skill when the artifact is content or content-like, not code. ## When To Use Trigger for: - digital products and guides - PDFs where the artifact itself is the deliverable - landing pages and sales pages - email sequences - strategy documents - slide decks - competitive content audits Do **not** use this for: - code review - raw architecture review - PR review For code, use `/bs:quality` or `/gh:review-pr`. Use this skill as the rubric source for `/bs:review`. The command is the entrypoint; this skill supplies the review frame and artifact-specific standards. ## Core Review Principle The goal is not “helpful feedback.” The goal is to determine: 1. whether the artifact is good enough to ship 2. what would make it clearly better than the generic AI slop in the market 3. what should be cut, tightened, or restructured ## Review Modes ### 1. SOTA Review Use when the user asks whether something is top-tier, strong enough, or “good enough to ship.” Rubric: - substance - originality - specificity - structure - audience fit - differentiation - polish ### 2. Conversion Review Use for landing pages, sales pages, launch emails, and offer docs. Rubric: - buyer clarity - pain clarity - offer legibility - objection handling - credibility - CTA strength - price support ### 3. Clarity Review Use when the artifact is informative but not directly sales-led. Rubric: - readability - hierarchy - signal-to-noise - terminology precision - pacing - t