agentleFS
posteverywhereposteverywhere/claude-plugin/skills/agency-clients/SKILL.md

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
  1. Distinctive:

    Match accounts to clients: If one workspace holds several clients' accounts, ask the user which accounts belong to which client.

    line 17
  2. Distinctive:

    Name the client before every action: Before you create, change, schedule, publish, retry or delete anything, say the client name and the …

    line 18
  3. Very specific:

    Filter by client: When listing or reporting, use list_posts_advanced with account_id (one call per account), or campaign_id, so one …

    line 21
  4. Very specific:

    Keep media apart: Check media belongs to the right client before you attach it.

    line 22
  5. Distinctive:

    If an account name is unclear (two similar pages), ask.

    line 26
  6. Very specific:

    Follow each client's own voice guide when the user has one (see brand-voice).

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Check where you are. At the start, call get_me and tell the user the workspace name. Call list_accounts and list the accounts by platform and username.
  2. 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.
  3. 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.
  4. 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.
  5. 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_campaigns and create_campaign (for example "Acme: October"), and pass its campaign_id on each post in bulk_create_posts. Drafts are not linked to campaigns. Don't add the client name to the post text unless the user wants it there.
  6. Filter by client. When listing or reporting, use list_posts_advanced with account_id (one call per account), or campaign_id, so one client's report never shows another client's posts.
  7. Keep media apart. Check media belongs to the right client before you attach it. list_media shows 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.