brand-voice
Skill0 starsChanged 28 days agoMITView on GitHub
Learn how the user writes on social media and write a short voice guide from their own posts in PostEverywhere. Use when the user says posts don't sound like them, asks Claude to "write like me" or "match my brand voice", or wants a style guide for their social accounts.
57 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- ASNNetworks/floh-skillstheir own version, first seen Nov 1, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- RightBlogger/bloggingskillstheir own version, first seen Nov 1, 2026
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use brand-discovery, agent-sort and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ysyecustSkillbrand-discovery
Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).
Also in 6 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 14 projects that use this
akachandan1Skillbrand-story
Receipts-based marketing storytelling engine for LinkedIn and X personal-brand, founder, and brand accounts. Use when the user wants to plan social content, write a LinkedIn post or X thread, research what's being said on social platforms before writing, react to a trend, or build a content calendar. Triggers: "brand story", "plan my content", "write a post", "LinkedIn post", "X thread", "tweet", "content calendar", "what should I post", "social listening", "research this topic", "react to this", "post about", "founder content".
Also in 4 projects that use this
TironFoxSkillagent-payment-x402
Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.
Also in 5 projects that use this
arsalllsSkillnetwork-config-validation
Pre-deployment validation of Cisco IOS/IOS-XE configuration — catching missing saves, mismatched ACLs, overlapping subnets, duplicate IPs, missing route-maps, and dangerous commands before they cause outages.
Also in 5 projects that use this
jgertonSkillbrand-messaging
Build brand messaging using Donald Miller's StoryBrand 7-element BrandScript. Produces BrandScript, tagline, and Neumeier's trueline. Requires positioning to be at least draft status. Triggers when someone needs messaging, a tagline, brand story, or "what should we say" answers.
Also in 4 projects that use this
Other versions57 projects use a version of this.
Word for word · 2
- posteverywhere/claude-plugin★ 1100% same
- posteverywhere/copilot-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 55
- affaan-m/ECC★ 246ksame name
- HybridAIOne/hybridclaw★ 159same name
- runxhq/runx★ 97same name
- mturac/everything-openai-codex★ 89same name
- mit-network/everything-claude-code★ 76same name
- cofoundy/brand-skills★ 67same name
- jgerton/brand-toolkit★ 64same name
- Fmarzochi/EGC★ 61same name
- ysyecust/everything-claude-code★ 44same name
- MoizIbnYousaf/marketing-cli★ 33same name
45 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agency-clientsSkill
- approval-workflowSkill
- connect-social-accountsSkill
- cross-post-videoSkill
- fix-failed-postsSkill
- launch-announcementSkill
- plan-content-calendarSkill
- recycle-top-postsSkill
- repurpose-contentSkill
- review-post-performanceSkill
- schedule-social-postsSkill
- weekly-reportSkill
- write-blog-postSkill
- write-x-thread-or-articleSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the user's own published posts, describe how they write, and use that description for every post you write after.
- Very specific: line 12
Collect their posts: Call list_posts_advanced with status: "published", sort: "published_at", order: "desc" and limit: 50.
- Distinctive: line 14
Describe the voice: Write a guide of no more than 10 short lines.
- Distinctive: line 24
Confirm: Ask the user to correct anything that is wrong.
“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brand voice
Read the user's own published posts, describe how they write, and use that description for every post you write after.
Steps
- Collect their posts. Call
list_posts_advancedwithstatus: "published",sort: "published_at",order: "desc"andlimit: 50. If the user writes differently per platform, addplatform(for example"linkedin") and do one pass per platform. - Check there is enough. Fewer than about 10 posts is a thin sample. Say so, and ask the user for a few more examples they like, or a link to their website or newsletter to read.
- Describe the voice. Write a guide of no more than 10 short lines. Cover:
- Tone (for example: warm, direct, dry humour).
- Sentence length and structure.
- Point of view ("I", "we", or no person).
- How posts open and how they end (question, call to action, link).
- Emoji and hashtag use: how many, and where.
- Words and phrases they use often, and words they never use.
- Formatting: line breaks, lists, capital letters.
- Differences between platforms, if any.
- Show examples. Quote two or three of their posts that show the voice best.
- Confirm. Ask the user to correct anything that is wrong. Update the guide until they agree.
- Use it. Apply the guide to every post you write in this conversation, including with the other PostEverywhere skills.
- Keep it. PostEverywhere has no place to store the guide through the connector. Tell the user to save it where Claude can read it next time, for example as a project instruction or in a saved note, and to paste it in when they start a new conversation.
Be careful
- Describe what the posts actually do. Don't invent a voice the posts don't show.
- The guide is about style. Don't copy their old posts as new ones.
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.

