agency-clients
Skill1 starsChanged 33 days agoMITView on GitHub
Work safely across several clients or brands in PostEverywhere. Use when the user manages social media for more than one client, brand or business, mentions a client by name, asks to switch clients, or when the connected accounts belong to different companies.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Match accounts to clients: If one workspace holds several clients' accounts, ask the user which accounts belong to which client.
- Distinctive: line 18
Name the client before every action: Before you create, change, schedule, publish, retry or delete anything, say the client name and the …
- Very specific: line 21
Filter by client: When listing or reporting, use list_posts_advanced with account_id (one call per account), or campaign_id, so one …
- Very specific: line 22
Keep media apart: Check media belongs to the right client before you attach it.
- Distinctive: line 26
If an account name is unclear (two similar pages), ask.
- Very specific: line 28
Follow each client's own voice guide when the user has one (see brand-voice).
≈ “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
Agency clients
One wrong account means a client's post goes out on another client's page. Check which client and which accounts before every action.
How the connector works
The connector works inside one PostEverywhere workspace: the one that was active when the user connected it in Claude. It sees only that workspace's accounts, posts, media and campaigns. It can't switch workspaces. To work on a client in another workspace, the user switches workspace in the PostEverywhere app, then disconnects and connects the PostEverywhere connector again in Claude. Say this plainly when the client they name isn't in the current workspace.
Steps
- Check where you are. At the start, call
get_meand tell the user the workspace name. Calllist_accountsand list the accounts by platform and username. - Match accounts to clients. If one workspace holds several clients' accounts, ask the user which accounts belong to which client. Write the map back to them, for example "Acme: Instagram @acme, LinkedIn Acme Ltd". Use it for the rest of the conversation.
- Name the client before every action. Before you create, change, schedule, publish, retry or delete anything, say the client name and the exact accounts, and ask the user to confirm.
- Never mix clients. One post goes to one client's accounts only. If the user asks for a post for two clients, make two separate posts, each written for its client.
- Label the work. Name the client next to every post id in your summaries. For scheduled posts, a campaign per client helps: find or make one with
list_campaignsandcreate_campaign(for example "Acme: October"), and pass itscampaign_idon each post inbulk_create_posts. Drafts are not linked to campaigns. Don't add the client name to the post text unless the user wants it there. - Filter by client. When listing or reporting, use
list_posts_advancedwithaccount_id(one call per account), orcampaign_id, so one client's report never shows another client's posts. - Keep media apart. Check media belongs to the right client before you attach it.
list_mediashows the whole workspace library.
Be careful
- If an account name is unclear (two similar pages), ask. Never guess.
- Reports for a client show only that client's accounts. Don't mention other clients' results.
- Follow each client's own voice guide when the user has one (see
brand-voice). Don't reuse one client's voice for another.
Other versions2 projects use a version of this.
Word for word · 2
- posteverywhere/copilot-plugin★ 0100% same
- posteverywhere/cursor-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
- approval-workflowSkill
- brand-voiceSkill
- 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
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.

