brand-voice-pass
Skill95 starsChanged 6 days agoMITView on GitHub
Use this skill when the user asks to rewrite, humanise, de-AI, polish, localise, or align draft text to a brand voice, house style, named audience, or writing profile.
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to transform draft copy into a defined brand or personal voice while preserving the user's meaning, evidence, terminology, …
- Distinctive: line 12
Preserve the truth: Do not invent facts, proof points, dates, clients, figures, quotes, or outcomes.
- Distinctive: line 14
Remove generic AI tells: Avoid empty intensifiers, inflated claims, tidy-but-bland phrasing, excessive signposting, and repetitive short …
- Distinctive: line 15
Use the requested variant of English: Default to the user's language and regional spelling.
- Distinctive: line 27
If the user has not supplied a full voice guide, infer only light stylistic choices from the draft and clearly avoid claiming a detailed …
- Distinctive: line 31
Read the full draft before editing.
- Distinctive: line 35
Remove generic AI phrasing and replace it with concrete, human language.
- Distinctive: line 36
Check the output against the original for meaning drift.
- Distinctive: line 41
Use these controls unless the user provides a different profile:
- Distinctive: line 43
Prefer concrete language over abstract positioning.
- Distinctive: line 44
Prefer lived-experience phrasing over consultancy jargon.
- Distinctive: line 45
Use natural paragraphing rather than long blocks or a list of fragments.
- Distinctive: line 46
Avoid repetitive, overly neat sentence structures.
- Distinctive: line 47
Avoid claims such as "game-changing", "revolutionary", "unlock", "seamless", "in today's fast-paced world", and similar filler unless they …
- Distinctive: line 48
Keep the user's level of confidence: do not over-polish into corporate blandness.
- Distinctive: line 79
No new evidence or claims have been invented.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brand Voice Pass
Use this skill to transform draft copy into a defined brand or personal voice while preserving the user's meaning, evidence, terminology, and intent.
Operating principles
- Preserve the truth. Do not invent facts, proof points, dates, clients, figures, quotes, or outcomes.
- Preserve the argument. Improve expression without changing the user's position unless they explicitly ask for a stronger or softer stance.
- Remove generic AI tells. Avoid empty intensifiers, inflated claims, tidy-but-bland phrasing, excessive signposting, and repetitive short sentences.
- Use the requested variant of English. Default to the user's language and regional spelling. If unspecified and the surrounding material uses UK English, use UK English.
- Respect the destination. Adjust length, cadence, paragraphing, and directness for the intended channel.
- Keep it usable. Return the rewritten copy first. Add notes only when useful.
Inputs to look for
- Draft text or notes to rewrite.
- Brand or personal voice guidance.
- Audience, channel, objective, and desired length.
- Words or phrases to avoid.
- Required terminology, source facts, or claims that must remain intact.
If the user has not supplied a full voice guide, infer only light stylistic choices from the draft and clearly avoid claiming a detailed brand profile exists.
Workflow
- Read the full draft before editing.
- Identify the core message, supporting evidence, and intended action.
- Apply the voice rules without adding unsupported content.
- Improve flow, transitions, sentence rhythm, and paragraph shape.
- Remove generic AI phrasing and replace it with concrete, human language.
- Check the output against the original for meaning drift.
- Return the final copy in a copy-ready format.
Default voice controls
Use these controls unless the user provides a different profile:
- Prefer concrete language over abstract positioning.
- Prefer lived-experience phrasing over consultancy jargon.
- Use natural paragraphing rather than long blocks or a list of fragments.
- Avoid repetitive, overly neat sentence structures.
- Avoid claims such as "game-changing", "revolutionary", "unlock", "seamless", "in today's fast-paced world", and similar filler unless they are in source text and must be retained.
- Keep the user's level of confidence: do not over-polish into corporate blandness.
Output patterns
For a simple rewrite, output only:
[Rewritten copy]For a rewrite where useful issues were found, output:
[Rewritten copy]
Notes:
- [Short note on any assumption, ambiguity, or retained risk.]References
This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support.
references/voice-profile-template.md- use this when additional structure, examples, or checks are useful for the task.
Quality checklist
Before responding, check:
- The rewritten text keeps the original meaning.
- No new evidence or claims have been invented.
- The copy sounds like a person, not a generic assistant.
- The requested language variant and channel fit are respected.
- The result is ready for the user to paste or publish.
In this repository199 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- accessibility-passSkill
- acroform-writerSkill
- action-items-todoSkill
- agent-evaluation-designerSkill
- agent-harness-explorerSkill
- agent-performance-triageSkill
- agent-red-teamSkill
- ai-demo-assistantSkill
- ai-first-process-redesignSkill
- ai-usecase-assessmentSkill
- anonymised-case-study-writerSkill
- evidence-gatherSkill
- gap-checkSkill
- readiness-packSkill
- scope-mapSkill
- b2b-outreach-suiteSkill
- blog-content-auditorSkill
- blog-post-structure-passSkill
- booth-loop-videoSkill
- brand-template-enforcerSkill
- breathing-roomSkill
- browser-uat-analystSkill
- business-osSkill
- call-for-speakers-digestSkill
- campaign-deck-builderSkill
- chart-builderSkill
- classic-text-adventureSkill
- clipchamp-videoSkill
- clt-hr-assistantSkill
- commenting-contentSkill
- competitive-battlecard-builderSkill
- conditional-chat-reminderSkill
- conference-session-abstract-packSkill
- contradiction-flagSkill
- insight-briefSkill
- provenance-checkSkill
- research-retrieveSkill
- trend-compareSkill
- content-quality-auditorSkill
- copilot-agent-advisorSkill
- copilot-studio-adaptive-card-builderSkill
- copilot-studio-agent-testSkill
- copilot-studio-harness-pickerSkill
- copilot-studio-knowledge-readinessSkill
- copilot-studio-mcp-readinessSkill
- copilot-studio-topic-blueprintSkill
- cowork-plugin-engineerSkill
- cowork-use-case-one-pagerSkill
- create-copilot-adoption-dashboardSkill
- context-assembleSkill
- handoff-packetSkill
- inquiry-intakeSkill
- knowledge-retrieveSkill
- resolution-draftSkill
- doc-format-converterSkill
- bom-impactSkill
- ecn-draftSkill
- ecr-ingestSkill
- standards-checkSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

