razbakov/website-voice-audit
skills/website-voice-audit/SKILL.md
Use when reviewing a website's UI copy, content, and meta for brand voice consistency. Triggers include launching a new site, rebranding, noticing inconsistent tone across pages, or preparing content for SEO. Checks nav, CTAs, author bios, meta descriptions, blog posts, project descriptions, config files, and locale files against brand voice guidelines.
$ install --global
skillsauthnpx skillsauth add razbakov/skills website-voice-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 5:07 AM10.8s1 file scanned
SKILL.md
- name:
- website-voice-audit
- description:
- Use when reviewing a website's UI copy, content, and meta for brand voice consistency. Triggers include launching a new site, rebranding, noticing inconsistent tone across pages, or preparing content for SEO. Checks nav, CTAs, author bios, meta descriptions, blog posts, project descriptions, config files, and locale files against brand voice guidelines.
Website Voice Audit
Systematically audit every text surface of a website against its brand voice guidelines. Produce a report of violations with concrete fixes.
When to Use
- Before a site launch or rebrand
- When copy feels inconsistent across pages
- After migrating content from another site/template
- When blog posts span different time periods (voice drift)
- When locale files were translated without voice review
Audit Checklist
1. Read Brand Voice Guidelines First
Find the voice/tone definition (usually in CLAUDE.md, brand docs, or style guide). Extract:
- Tone keywords (e.g., "direct, reflective, authentic")
- Words to use (e.g., "build, ship, validate")
- Words to avoid (e.g., "synergy, leverage, empower, impactful")
- Writing style (first person? casual? process-oriented?)
- CTA style (e.g., "Let's talk" > "Schedule a consultation")
2. Audit Every Text Surface
Check each surface against the guidelines. Read the actual files, don't guess.
| Surface | Where to find | Common violations |
|---|---|---|
| Site config | config.json, nuxt.config.ts | Generic description, dead marketing copy |
| Navigation | Nav components, i18n files | Corporate labels ("Schedule a Consultation") |
| Homepage | Hero, subtitle, CTAs | Template filler, banned words |
| About page | Bio, section headings, CTAs | LinkedIn-style corporate bio |
| Blog subtitles | i18n files, page components | Generic ("Sharing insights on topics I'm passionate about") |
| Author bio | Blog post template | Mismatch with personal voice |
| CTA fallbacks | i18n files | "Ready to Get Started?" / "Take the next step" |
| Blog posts | Content markdown files | Voice drift across years, emoji abuse, marketing hype |
| Project descriptions | Content markdown files | Third-person pitch deck voice vs first-person |
| Meta descriptions | useSeoMeta, i18n files | Generic or missing |
| Footer | App/layout component | Boilerplate |
| Empty states | Page components | Dev-facing text in production |
| All locale files | i18n directory | Translations that don't match voice |
3. Classify Violations
For each violation, note:
- File and line — exact location
- Current text — what it says now
- Problem — why it violates the voice (reference specific guideline)
- Fix — concrete replacement text
4. Prioritize
| Priority | Description | |---|---| | P0 | Uses explicitly banned words | | P1 | Dead/template copy visible to users | | P2 | Inconsistent with voice but not terrible | | P3 | Could be better but functional |
Report Format
## Voice Audit: [site name]
### Voice Guidelines Summary
- Tone: ...
- Words to use: ...
- Words to avoid: ...
### Violations Found
| Priority | Location | Current | Problem | Fix |
|---|---|---|---|---|
### Blog Post Voice Assessment
| Post | Voice match | Issues |
|---|---|---|
### Recommendations
1. ...
Blog Post Rewrites
When rewriting blog posts to match voice:
- Keep: frontmatter (dates, images, links, tags, CTAs), core ideas, code blocks, internal links
- Remove: emojis in headers, marketing hype, exclamation-mark emphasis, "Perfect For" audience sections, "Ready to revolutionize?" CTAs
- Rewrite: titles, descriptions, section structure, all body copy
- Dispatch parallel agents for independent post rewrites (one agent per post)
- Spot-check each rewrite: grep for emojis, verify no banned words, read opening and closing paragraphs
Common Mistakes
- Auditing only English and forgetting locale files
- Fixing UI text but leaving meta descriptions in old voice
- Rewriting blog posts without preserving frontmatter links and CTAs
- Not checking config files for dead/unused marketing copy
- Over-correcting: CV pages should stay professional, not match casual blog voice
Related Skills
razbakov/instagram-launch-grid
development
VerifiedTrustedCommunity
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
3SKILL.mdUpdated May 21, 2026
razbakov/translate-blog-post
testing
VerifiedTrustedCommunity
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
3SKILL.mdUpdated May 20, 2026
razbakov/press-kit-pack
development
VerifiedTrustedCommunity
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
3SKILL.mdUpdated May 20, 2026
razbakov/concert-burndown
development
VerifiedTrustedCommunity
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.
3SKILL.mdUpdated May 20, 2026