validate-style-guide
/validate-style-guide
Audits a brand's style guide for problems that would make two reviewers disagree, such as rules that contradict each other or their own examples, rules too vague to apply, overlapping rules, and code-check settings that disagree with the rule text, plus schema errors. Use when someone asks to validate, audit, lint, or sanity-check a style guide.
- Author
- animalzinc ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Audits a brand's style guide for problems that would make two reviewers disagree, such as rules that contradict each other or their own examples, rules too vague to apply, overlapping rules, and code-check settings that disagree with the rule text, plus schema errors. Use when someone asks to validate, audit, lint, or sanity-check a style guide.
Arguments
/validate-style-guide <brand> [--guide F]
Original author description
Audits a brand's style guide for problems that would make two reviewers disagree, such as rules that contradict each other or their own examples, rules too vague to apply, overlapping rules, and code-check settings that disagree with the rule text, plus schema errors. Use when someone asks to validate, audit, lint, or sanity-check a style guide.
How it works
SKILL.md has no level-two headings · 16 lines, 272 words
SKILL.md preview
---
name: validate-style-guide
description: Audits a brand's style guide for problems that would make two reviewers disagree, such as rules that contradict each other or their own examples, rules too vague to apply, overlapping rules, and code-check settings that disagree with the rule text, plus schema errors. Use when someone asks to validate, audit, lint, or sanity-check a style guide.
argument-hint: <brand> [--guide F]
allowed-tools: Read, Write, Glob, Agent, Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sgc.py" *), Bash(py -3 "${CLAUDE_PLUGIN_ROOT}/scripts/sgc.py" *)
---
# Validate a style guide
Checks one guide in two passes: code for the schema, then an auditor for what needs reading. Changes nothing unless the user asks.
Arguments: $ARGUMENTS
Every `sgc` step is `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sgc.py" <command> ...`, written out in full and run as its own Bash call, never chained with `;`, `&&`, or a pipe, so it matches the skill's permission for `sgc`. On Windows, `py -3` in place of `python3`. Without Python 3.9 or later, stop and say the plugin needs it.
1. The plugin's guides folder setting reads: `${user_config.guides_dir}`. Run `sgc brand-path <brand> --project-dir "${CLAUDE_PROJECT_DIR}"`, adding `--guides-dir "<path>"` only when that setting is an absolute path (an unset setting shows as text starting with `${`, which must never reach the shell), and `--guide F` when given. Without a guide, stop and offer `build-style-guide`.
2. A `schema_version` of 1: report that the guide predates rule IDs, that the checks still read it, and that `build-style-guide <brand> --upgrade` converts it. Then audit it as it is.
3. Run `sgc guide validate <guide>` and `sgc guide parse <guide> --out <brand_dir>/builds/<YYYY-MM-DD>/rules.json`.
4. Launch `blog-style-guide-creator:guide-auditor` with `model: "${user_config.deep_model}"` (leave `model` out when the value is empty or still reads `${`), giving the guide path, the parsed rules path, the validate output, and the output `<brand_dir>/builds/<YYYY-MM-DD>/audit.json`.
5. Report the schema errors and warnings, then the audit's findings grouped by type (contradiction, example conflict, vague, overlap, check mismatch, scope gap), each with the rules involved and the proposed fix. End with the counts.
6. When the user asks for fixes, make them through `build-style-guide`'s approve-and-write steps, so the diff is shown before the guide changes.
Versions
The database has no other skills named validate-style-guide.
Database snapshot: 13.11.2026 · package version a955646ec5d8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100build-style-guide
Builds or updates a brand's editorial style guide from its published articles, a brand kit, a brand style document, or its editors' edits, and converts a version 1 guide. Every rule cites its evidence, mechanical rules get code checks, and nothing is written until the user… - 90style-check
Checks one draft against a brand's style guide and writes a report of violations, each with the exact quote, the rule, and a fix. Code runs the mechanical checks; parallel reviewers cover usage, structure, voice, and proofreading; a verifier confirms every reviewer finding. With… - 100brand-style-guide
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand,… - 100style-system
Use when user wants to initialize style, extract reusable writing signals from user-supplied text, compose a project style guide, or analyze style drift. - 100style-system
Use when user wants to initialize style, extract reusable writing signals from user-supplied text, compose a project style guide, or analyze style drift. - 90brand-review
Use this skill to review content against brand voice, style rules, messaging pillars, terminology, positioning, audience fit, and proof standards before publication.