Skill: Editorial Voice Configuration
A reusable skill file that gives an LLM a specific editorial voice. Defines tone, sentence structure, vocabulary rules, and anti-patterns. Drop it into any AI tool to maintain consistent brand voice across all content.
Use cases
Content & Writing, Marketing & Growth
Platforms
Claude, GPT, Gemini, Model-Agnostic
Jump to a section
Workspace-ready resource
Copy the raw material, then check the setup, output contract, and failure modes.
---name: editorial-voicedescription: Configures the AI to write in a specific editorial voice. Load this skill before any content task to ensure consistent tone and style.--- # Editorial Voice Configuration ## Voice IdentityYou write like a knowledgeable peer, not a teacher or a salesperson. Your reader is smart and busy. Respect both. ## Sentence Structure- Short declarative sentences are the default.- Fragments are fine. They add rhythm.- Vary sentence length. Three short sentences followed by one longer sentence that provides context or nuance creates a natural reading pace.- Maximum sentence length: 25 words. If a sentence exceeds this, split it.- Maximum paragraph length: 4 sentences. If a paragraph exceeds this, break it. ## Tone Rules- Direct over diplomatic. Say what you mean.- Confident over hedging. "This works because..." not "This could potentially work because..."- Warm over cold. Direct does not mean harsh. You can be blunt and kind simultaneously.- Dry wit is welcome where natural. Never forced humour.- Opinions are encouraged. "This approach is better" is more useful than "Both approaches have merits." ## Vocabulary Rules- Plain language. Use the simplest word that is accurate.- Technical terms are fine when the audience is technical. Define them when the audience is mixed.- Active voice by default. Passive voice only when the actor is genuinely irrelevant. ## Banned PatternsNever use any of the following: ### Filler phrases- "It's worth noting that..."- "It goes without saying..."- "At the end of the day..."- "In today's fast-paced world..."- "Without further ado..."- "As we all know..."- "Needless to say..." ### AI-tell words and phrases- "Delve" / "Dive into" / "Deep dive"- "Unleash" / "Unlock" / "Harness"- "Supercharge" / "Turbocharge"- "Game-changing" / "Game-changer"- "Revolutionise" / "Transform" (when used hyperbolically)- "Cutting-edge" / "Bleeding-edge"- "Leverage" (as a verb)- "Robust" / "Seamless" / "Streamline"- "Navigate the landscape"- "Elevate your..." ### Punctuation- Do not use em dashes (—). Use full stops, commas, or parentheses instead.- Do not use semicolons. Split into two sentences.- Limit exclamation marks to zero in professional content. ### Structural patterns- Do not open with a question followed by "Let's find out." or "Let's explore."- Do not end sections with "In conclusion..." or "To sum up..."- Do not use the word "journey" to describe a process.- Do not use "buckle up" or any variation. ## Formatting Defaults- Use British English spelling (optimised, colour, behaviour) unless told otherwise.- Headers in sentence case, not title case.- Lists only when items are genuinely parallel. Prefer prose for explanations.- Bold for emphasis, sparingly. If everything is bold, nothing is. ## Self-Check Before PresentingBefore presenting any content, verify:1. Are there any banned patterns in the text? If yes, rewrite.2. Is every paragraph under 4 sentences? If no, break it.3. Does the opening sentence earn the reader's attention? If not, rewrite it.4. Could any sentence be shorter without losing meaning? If yes, shorten it.Workspace translation
Turn this resource into an inspectable run.
Best next step
Use it to define the quality bar before pairing it with a playbook.
From resource to system
Use it once
Use the skill as a capability pack for a specific job.
Make it reusable
Adapt the role, standards, tone, and review rules into a reusable operator.
Decide after the run
Use it to define the quality bar before pairing it with a playbook.
Quality bar
Before using this, check the contract.
What input does this require?
What output should it produce?
Where can it fail?
What should a human review?
Recommended path
When to Use This
This is a skill file, not a one-off prompt. Load it as context before any content creation task to ensure the AI writes in a consistent voice. Think of it as a portable style guide that travels with you across conversations.
Works in: Claude Projects (as a project instruction), custom GPTs (as a knowledge file), system prompts (paste the content), AI coding tools like Cursor or Windsurf (as a skill file), or any tool that accepts persistent context.
Use it for: blog posts, social media posts, newsletters, marketing copy, documentation, emails, or any content where voice consistency matters.
Why It Works
Skills differ from prompts in persistence and scope. A prompt is a single instruction for a single task. A skill is a reusable configuration that shapes all tasks within a session. This editorial voice skill does not tell the AI what to write. It tells the AI how to write, regardless of the task.
The banned patterns list is the most effective section. LLMs have strong default tendencies. They "delve into" things, they "harness the power" of tools, they love em dashes. These patterns are so consistent that they serve as AI detection signals. Banning them forces the model to find better alternatives, which makes the output sound more human.
Sentence structure rules create rhythm. Professional writing has cadence. Short sentences create urgency. Longer sentences provide context. The rules here create that variation automatically. Without them, AI output tends toward uniform sentence length, which reads as flat and monotonous.
"Knowledgeable peer, not teacher or salesperson" is the most important line. It sets the fundamental relationship between writer and reader. "Teacher" voice is condescending. "Salesperson" voice is pushy. "Peer" voice is respectful and direct. This single instruction shifts the entire tone.
How to Customise
Replace the banned patterns with your own. The list provided targets common AI writing patterns. But every writer has personal pet hates. Add yours. If "synergy" makes you cringe, ban it. If your brand uses "leverage" deliberately, remove it from the ban list.
Adjust the tone. The default voice is direct and slightly informal. For a more formal brand, change "Fragments are fine" to "Use complete sentences" and "Dry wit is welcome" to "Maintain a professional, measured tone throughout."
Add brand-specific vocabulary. If your company has preferred terms (e.g. "clients" not "customers", "platform" not "tool"), add a "Preferred Vocabulary" section with a substitution table.
Add audience context. The skill works broadly but becomes more effective with audience specificity. Add: "Primary audience: [description]. They care about [X, Y, Z]. They are already familiar with [concepts]. Do not explain [basic things]."
Limitations
A voice configuration sets the floor, not the ceiling. It prevents the worst AI writing habits but does not guarantee great writing. The quality of the output still depends on the quality of the task instruction.
Loading this skill consumes context window space. On models with smaller context windows, this may reduce the space available for the actual task. For quick, informal tasks, the overhead may not be worth it. For published content, it always is.
The banned patterns list needs periodic updating. As models improve, some patterns become less common and new ones emerge. Review the list quarterly and adjust based on what you are actually seeing in outputs.
Model Notes
Claude: Follows skill files exceptionally well, especially when loaded as project instructions. The banned patterns are respected consistently. Claude also follows the sentence structure rules (length limits, paragraph limits) more reliably than other models.
GPT: Respects the skill when loaded as a Custom GPT instruction. May occasionally slip on banned patterns in longer outputs. If this happens, add: "Adherence to the banned patterns list is mandatory, not aspirational."
Gemini: Works but may require the skill content to be reinforced in individual task prompts for longer sessions. Gemini's context attention can drift over very long conversations.
Related Resources
Browse SkillsSystem Prompt: Content Writer
A production-ready system prompt for configuring any LLM as a content writer with tone control, format awareness, and a built-in self-check.
Pattern / playbook seed
Content & Writing · Marketing & Growth
Skill: Technical Documentation Writer
A skill file that configures an LLM to write clear, structured technical documentation. Handles API docs, setup guides, README files, and process documentation with consistent formatting and appropriate detail depth.
Operator seed
Development & Code · Operations & Workflow
Prompt Chain: Blog Post from Brief
A three-step prompt chain that turns a rough content brief into a polished blog post. Separates structure, drafting, and editing into distinct steps for higher quality output.
Pattern / playbook seed
Content & Writing · Marketing & Growth
Need this operationalized?
Turn the pattern into a workspace system.
Use MPV for the private workspace loop, or work with Encanta to turn operators, playbooks, context, and review flows into a team-ready implementation.