business/marketing/brand-voice/SKILL.md
Apply and enforce brand voice, style guide, and messaging pillars across content. Use when reviewing content for brand consistency, documenting a brand voice, adapting tone for different audiences, or checking terminology and style guide compliance.
npx skillsauth add harsh040506/claude-code-unified-skill-plugin-library brand-voiceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Frameworks for documenting, applying, and enforcing brand voice and style guidelines across marketing content.
A complete brand voice document should cover these areas. Use this framework to help users define their brand voice or to understand an existing brand voice configuration.
Define the brand as if it were a person. What are its defining traits?
Example: "If our brand were a person, they would be a knowledgeable colleague who explains complex things simply, celebrates your wins genuinely, and never talks down to you."
Select 3-5 attributes that define how the brand communicates. Each attribute should be defined with:
How the voice adapts across contexts while remaining recognizably the same brand.
Specific grammar, formatting, and language rules. See the Style Guide Enforcement section below.
Preferred and avoided terms. See the Terminology Management section below.
When defining brand voice, it helps to position attributes on a spectrum. Here are common attribute spectrums:
| Spectrum | One End | Other End | |----------|---------|-----------| | Formality | Formal, institutional | Casual, conversational | | Authority | Expert, authoritative | Peer-level, collaborative | | Emotion | Warm, empathetic | Direct, matter-of-fact | | Complexity | Technical, precise | Simple, accessible | | Energy | Bold, energetic | Calm, measured | | Humor | Playful, witty | Serious, earnest | | Innovation | Cutting-edge, forward-looking | Established, proven |
For each chosen attribute, document it in this format:
[Attribute name]
Example:
Approachable
The brand voice stays consistent, but tone adapts to context. Tone is the emotional inflection applied to the voice.
| Channel | Tone Adaptation | Example | |---------|----------------|---------| | Blog | Informative, conversational, educational | "Let's walk through how this works and why it matters for your team." | | Social media (LinkedIn) | Professional, thought-provoking, concise | "Three things we learned from running 50 campaigns this quarter." | | Social media (Twitter/X) | Punchy, direct, sometimes witty | "Your landing page has 3 seconds. Make them count." | | Email marketing | Personal, helpful, action-oriented | "We put together something we think you'll find useful." | | Sales collateral | Confident, benefit-driven, specific | "Teams using our platform reduce reporting time by 40%." | | Support/Help docs | Clear, patient, step-by-step | "If you see this error, here's how to fix it." | | Press release | Formal, factual, newsworthy | "The company today announced the launch of..." | | Error messages | Empathetic, helpful, blame-free | "Something went wrong on our end. We're looking into it." |
| Situation | Tone Adaptation | |-----------|----------------| | Product launch | Excited, confident, forward-looking | | Incident or outage | Transparent, empathetic, accountable | | Customer success story | Celebratory, specific, crediting the customer | | Thought leadership | Authoritative, nuanced, evidence-based | | Onboarding | Welcoming, encouraging, clear | | Bad news (price increase, deprecation) | Honest, respectful, solution-oriented | | Competitive comparison | Confident but fair, fact-based, not disparaging |
The voice attributes remain fixed. Tone dials them up or down based on context. For example, if a brand is "bold and warm":
Document and enforce these choices consistently:
| Rule | Options | Example | |------|---------|---------| | Oxford comma | Yes / No | "fast, reliable, and secure" vs. "fast, reliable and secure" | | Sentence case vs. title case (headings) | Sentence / Title | "How to get started" vs. "How to Get Started" | | Contractions | Use / Avoid | "we're" vs. "we are" | | Em dash spacing | No spaces / Spaces | "this—and more" vs. "this — and more" | | Numbers | Spell out 1-9, numerals 10+ / Always numerals | "five features" vs. "5 features" | | Percent | % / percent | "50%" vs. "50 percent" | | Date format | Month DD, YYYY / DD/MM/YYYY / etc. | "January 15, 2025" | | Time format | 12-hour / 24-hour | "3:00 PM" vs. "15:00" | | Lists | Periods / No periods on fragments | "Set up your account." vs. "Set up your account" |
Maintain a list of preferred terms and their incorrect alternatives:
| Use This | Not This | Notes | |----------|----------|-------| | sign up (verb) | signup (verb) | "signup" is the noun form | | log in (verb) | login (verb) | "login" is the noun/adjective form | | set up (verb) | setup (verb) | "setup" is the noun/adjective form | | email | e-mail | No hyphen | | website | web site | One word | | data is (singular) | data are | Unless the publication requires plural |
testing
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
tools
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
testing
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
development
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.