Content Auditor Skill

Audit website copy for quality, consistency, and completeness issues.

10|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mrhinkle/VibeCoding-a-Website --skill content-auditor-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Content Auditor Skill
Source: https://github.com/mrhinkle/VibeCoding-a-Website/tree/main/.claude/skills/content-auditor
Command: npx skills add https://github.com/mrhinkle/VibeCoding-a-Website --skill content-auditor-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Content Auditor identifies and prioritizes quality, consistency, and completeness issues in website copy so stakeholders can fix low-quality text, placeholder content, factual errors, and broken CTAs before launch or during maintenance.

Core Features & Use Cases

  • Placeholder detection: Finds lorem ipsum, TODO tokens, unfilled variables, example emails/phones, and other draft text.
  • Factual accuracy checks: Flags dates, statistics, pricing, and feature claims that require verification.
  • Brand voice & consistency: Detects tone and messaging inconsistencies across pages and audience segments.
  • Grammar & spelling: Identifies typos, punctuation errors, and grammar issues with prioritized fixes.
  • CTA and messaging assessment: Evaluates CTA clarity, placement, and messaging contradictions that reduce conversions.
  • Contact and legal checks: Verifies contact information consistency and presence of critical pages (contact, privacy, terms).
  • Use cases: Pre-launch full-site audits, targeted page reviews (homepage, pricing, legal), quarterly content maintenance, and QA after major updates.

Quick Start

Run a full-site content audit and generate a prioritized report with critical issues, suggested fixes, and an overall score.

Frequently Asked Questions about Content Auditor Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit website copy for placeholder text and broken CTAs before launch?

To audit website copy, run a full-site content audit to detect placeholder text, unfilled variables, and weak CTAs. The process generates a prioritized, exportable report with severity classifications, suggested fixes, and estimated fix times for pre-launch review.

Can I check brand voice consistency and grammar across multiple landing pages?

Yes, you can check brand voice consistency and grammar across multiple landing pages. The audit detects tone and messaging inconsistencies across audience segments while identifying typos, punctuation errors, and grammar issues with prioritized fixes for each page section.

What is the best way to find missing legal pages and contact discrepancies during a content review?

The best way to find missing legal pages and contact discrepancies is using contact and legal checks. This verifies contact information consistency and confirms the presence of critical pages like contact, privacy, and terms during quarterly content maintenance.

Does the content audit report include estimated fix times and severity classifications?

Yes, the content audit report includes estimated fix times and severity classifications. It produces exportable reports that contain page and section locations, suggested fixes, a scoring rubric, and prioritized critical issues to guide maintenance workflows.

Can I run a targeted content audit on just my pricing page instead of the full site?

Yes, you can run a targeted content audit on just your pricing page instead of the full site. The tool supports targeted page reviews for specific sections like homepage, pricing, and legal pages to flag dates, statistics, and pricing claims requiring verification.

When should I avoid running a full-site content audit on a staging environment?

You should avoid running a full-site content audit on a staging environment when page content is still actively being drafted. The audit is designed for pre-launch and periodic reviews, so auditing incomplete pages will surface excessive placeholder text and TODO tokens that are already known.