π Voice Bible
Audit a draft against your own voice spec and flag every line that breaks your house style. Checks banned words and phrases, em-dashes (when your spec bans them), sentences over your word-count cap, off-spec terms that have a preferred replacement, missing contractions, and forbidden clichΓ©s. Config-driven by a voice-spec.json you control, with a sensible default spec if you don't supply one.
- Scan technical documentation for banned jargon and preferred terms.
- Enforce sentence length limits to improve mobile readability.
- Identify and replace cliches with brand-approved terminology.
$13
Β· or 65 creditsSecure checkout via Stripe
Included in download
- Scan technical documentation for banned jargon and preferred terms.
- Enforce sentence length limits to improve mobile readability.
- file_read, terminal automation included
- Ready for Cursor
Sample input
Compare my latest blog post draft in /docs/blog-post.md against our official voice-spec.json and show me where I'm off-brand.
Sample output
### Voice Audit Results: blog-post.md **Spec:** voice-spec.json - [Line 12] **Banned Word**: "Synergy" (Severity: High) -> *Suggestion: Collaboration* - [Line 45] **Sentence Length**: 38 words (Limit: 25) - [Line 82] **Style Violation**: Em-dash detected (Banned per spec) - [Line 104] **Cliche**: "At the end of the day"
π Voice Bible
Audit a draft against your own voice spec and flag every line that breaks your house style. Checks banned words and phrases, em-dashes (when your spec bans them), sentences over your word-count cap, off-spec terms that have a preferred replacement, missing contractions, and forbidden clichΓ©s. Config-driven by a voice-spec.json you control, with a sensible default spec if you don't supply one.
$13
Β· or 65 creditsSecure checkout via Stripe
Included in download
- Scan technical documentation for banned jargon and preferred terms.
- Enforce sentence length limits to improve mobile readability.
- file_read, terminal automation included
- Ready for Cursor
- Instant install
Sample input
Compare my latest blog post draft in /docs/blog-post.md against our official voice-spec.json and show me where I'm off-brand.
Sample output
### Voice Audit Results: blog-post.md **Spec:** voice-spec.json - [Line 12] **Banned Word**: "Synergy" (Severity: High) -> *Suggestion: Collaboration* - [Line 45] **Sentence Length**: 38 words (Limit: 25) - [Line 82] **Style Violation**: Em-dash detected (Banned per spec) - [Line 104] **Cliche**: "At the end of the day"
About This Skill
The Brand Voice Guardian for Your Content
Maintaining a consistent brand voice across multiple writers or drafts is a scaling nightmare. The Voice Bible skill solves this by transforming your brand guidelines into a rigorous, automated auditing system. Unlike generic AI rewriting that strips away personality, this tool acts as a precision scanner to ensure your content adheres to your specific "bring-your-own" voice specification.
What it does
This skill provides a developer-friendly auditing layer for text and Markdown drafts. It programmatically scans content against your voice-spec.json, identifying violations in real-time. It covers:
- Banned Vocabulary: Instant detection of forbidden words or industry jargon.
- Structural Constraints: Enforcement of sentence-length caps and em-dash bans.
- Preferred Terminology: Mapping "good" vs. "bad" word choices.
- Cliche Detection: Highlighting tired metaphors and low-value filler.
Why use this skill?
Generic AI "checkers" often hallucinate style rules or ignore specific brand nuances. Voice Bible is deterministic; it uses high-speed Python-based scanning to give you a definitive report on file/line violations. You get a clear diagnostic of where the voice fails, allowing you to maintain full creative control while ensuring brand consistency.
Output format
The skill generates a structured report detailing the scope inspected, the specific spec used, confirmed findings with severity levels, and suggested replacements for every violation found.
Use Cases
- Scan technical documentation for banned jargon and preferred terms.
- Enforce sentence length limits to improve mobile readability.
- Identify and replace cliches with brand-approved terminology.
- Ensure consistency across a distributed team of content contributors.
Known Limitations
Heuristic detector. Coverage is only as good as your voice-spec.json: it enforces the words, terms, and limits you define, plus the shipped defaults if you provide none. The contraction and clichΓ© checks are pattern-based, so they can miss edge cases or flag an intentional choice. It is a linter, not an editor.
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/voice-bible -o /tmp/voice-bible.zip && unzip -o /tmp/voice-bible.zip -d ~/.claude/skills && rm /tmp/voice-bible.zipFree skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
File Scopes
Read-only. Loads rules from voice-spec.json (a default spec ships in the package, so it works out of the box) and parses it with the standard library. Prints findings with rule id, severity, file, and line. Reads no environment variables and writes nothing.
Works with any agent that can read a draft and run a local Python script (Claude Code, Cursor, Codex CLI, and other SKILL.md-compatible agents). Standard library only, no install step. Reads Markdown and text drafts plus a voice-spec.json. It flags and reports only; it does not rewrite your prose.