000-jeremy-content-consistency-validator

•

1.9k2593 months ago

Validate messaging consistency across website, GitHub repos, and local documentation generating read-only discrepancy reports. Use when checking content alignment or finding mixed messaging. Trigger with phrases like "check consistency", "validate documentation", or "audit messaging".

Quick Install

npxskills add jeremylongshore/claude-code-plugins-plus-skills--skill 000-jeremy-content-consistency-validator

Instructions

Content Consistency Validator

Overview

Checks content for tone, terminology, formatting, and structural consistency across multiple documentation sources (websites, GitHub repos, local docs). Generates read-only discrepancy reports with severity-classified findings and actionable fix suggestions including file paths and line numbers.

Examples

Pre-release audit: Before tagging a new version, run the validator to catch version mismatches between your README, docs site, and changelog — e.g., the website says v2.1.0 but the GitHub README still references v2.0.0.
Post-rebrand check: After renaming a product or updating terminology (e.g., "plugin" to "extension"), validate that all docs, landing pages, and contributing guides use the new term consistently.
Onboarding review: When a new contributor flags confusing docs, run a consistency check to surface contradictory feature claims, outdated contact info, or missing sections across your documentation sources.

Prerequisites

Access to at least two content sources (website, GitHub repo, or local docs directory)
WebFetch permissions configured for remote URLs (deployed sites, GitHub raw content)
Local documentation stored in recognizable paths (docs/, claudes-docs/, internal/)

Instructions

Discover sources — scan for build directories (, , , , ), GitHub README/CONTRIBUTING files, and local doc folders:

Loading…

Related Skills

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

367,360

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

367,309

1password

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

365,915

himalaya

CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).

365,885

Tags & Topics

aiautomationclaude-codedevopsmcpai-agents

Content Consistency Validator

Overview

Examples

Pre-release audit: Before tagging a new version, run the validator to catch version mismatches between your README, docs site, and changelog — e.g., the website says v2.1.0 but the GitHub README still references v2.0.0.
Post-rebrand check: After renaming a product or updating terminology (e.g., "plugin" to "extension"), validate that all docs, landing pages, and contributing guides use the new term consistently.
Onboarding review: When a new contributor flags confusing docs, run a consistency check to surface contradictory feature claims, outdated contact info, or missing sections across your documentation sources.

Prerequisites

Access to at least two content sources (website, GitHub repo, or local docs directory)
WebFetch permissions configured for remote URLs (deployed sites, GitHub raw content)
Local documentation stored in recognizable paths (docs/, claudes-docs/, internal/)

Instructions

Discover sources — scan for build directories (, , , , ), GitHub README/CONTRIBUTING files, and local doc folders:

Error	Cause	Solution
Website content unreachable	URL returns 4xx/5xx or build dir missing	Verify site is deployed or run local build; check WebFetch permissions
GitHub API rate limit	Too many fetches in short window	Pause and retry after reset window; use authenticated requests
No documentation directory	Expected paths don't exist	Confirm working directory; specify doc path explicitly
Empty content extraction	Client-side rendering not visible to fetch	Use local build output directory instead of live URL
Diff command failure	File paths contain special characters	Quote all file paths passed to diff and grep

000-jeremy-content-consistency-validator

Content Consistency Validator

Overview

Examples

Prerequisites

Instructions

Related Skills

skill-creator

skill-creator

1password

himalaya

skill-creator

skill-creator

1password

himalaya

Content Consistency Validator

Overview

Examples

Prerequisites

Instructions

Report Format

Output

Error Handling

Resources

Related Skills

skill-creator

skill-creator

1password

himalaya

Related Skills

skill-creator

skill-creator

1password

himalaya