brand-voice-analyzer
Analyzes a company's content to extract and codify their brand voice into a comprehensive style guide. Reads website copy, blog posts, emails, and social media to identify tone, vocabulary patterns, sentence structure, personality traits, and word preferences. Generates a brand-voice-guide.md and reviews new content against it.
What this skill does
# Brand Voice Analyzer Ingest a company's existing content, reverse-engineer the voice behind it, produce a definitive brand voice guide any writer can follow, and review new content against an established guide. ## Contents - `references/voice-dimensions.md` -- the seven-axis tone spectrum, vocabulary, sentence, personality, audience, and formatting dimensions to extract - `references/guide-template.md` -- required sections, quality standards, and pre-delivery checklist for `brand-voice-guide.md` - `references/review-mode.md` -- process and output format for scoring content against a guide - `references/metrics.md` -- quantitative and qualitative analysis techniques and citation standards - `references/edge-cases.md` -- handling for thin corpora, multiple voices, regulated industries, rebrands, plus interaction patterns ## Workflow: Create a New Voice Guide 1. Ask which content sources are available (URLs, files, directories, pasted text). 2. Ask about any known brand attributes, values, or existing guidelines. 3. Collect the corpus. Pull URLs with WebFetch, locate files with Glob/Read, find public content with WebSearch. Gather website copy, 5-10 blog posts, email campaigns, social posts, sales collateral, and support content. Document each source and its word count. 4. Confirm corpus size. Require at least 3,000 words across 2+ content types. If smaller, flag the limitation and mark affected findings as lower confidence. 5. Run the full voice extraction across every dimension in `references/voice-dimensions.md`, citing source examples per the standards in `references/metrics.md`. 6. Present a summary of findings for validation before generating the guide. 7. Generate the complete `brand-voice-guide.md` following `references/guide-template.md`. Verify it against that checklist before delivery. 8. Offer to review a sample piece of content against the new guide. ## Workflow: Review Content 1. Locate or ask for the `brand-voice-guide.md`. 2. Read the content to be reviewed. 3. Run the review process and produce the scored output defined in `references/review-mode.md`. 4. Present findings with actionable, guide-referenced fixes. ## Workflow: Update an Existing Guide 1. Read the current `brand-voice-guide.md`. 2. Ingest the new content sources and run extraction on the new material. 3. Compare findings against the existing guide. 4. Propose specific updates with rationale. 5. Apply approved changes with Edit. ## Output Standards - Primary output: `brand-voice-guide.md`. For multiple brands: `brand-voice-guide-[company-name].md`. Deliver review output inline unless a file is requested. - Use markdown headers (H1-H4), tables for comparative data, blockquotes for source quotes, code blocks only for literal reproduced text. Bold key terms on first use. No emojis. ## Operating Principles - Never fabricate examples. Every quoted example must come from actual source content. - Never assert voice attributes without evidence. If the data does not support a conclusion, say so. - Present findings as observations, not prescriptions, until the user validates them. - Distinguish voice (consistent: who we are) from tone (shifts by context: how we adapt) in every guide. - When reviewing, be specific: cite the exact word, phrase, or structure and the guide section it touches. - Treat the guide as a living document and defer to the user's judgment on subjective calls.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".