← PostEverywhereCONTENT HISTORY
WHAT CHANGED
Update to PostEverywhere
Snapshot Oct 29, 2026 · 19:13 UTC · version 1.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save PostEverywhere and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "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.",
"included_files": [],
"name": "agency-clients",
"skill_md_contents": "---\nname: agency-clients\ndescription: 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.\n---\n\n# Agency clients\n\nOne wrong account means a client's post goes out on another client's page. Check which client and which accounts before every action.\n\n## How the connection works\n\nThe PostEverywhere app works inside one PostEverywhere workspace: the one that was active when the user connected it in ChatGPT. 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 app again in ChatGPT. Say this plainly when the client they name isn't in the current workspace.\n\n## Steps\n\n1. **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.\n2. **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.\n3. **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.\n4. **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.\n5. **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.\n6. **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.\n7. **Keep media apart.** Check media belongs to the right client before you attach it. `list_media` shows the whole workspace library.\n\n## Be careful\n\n- If an account name is unclear (two similar pages), ask. Never guess.\n- Reports for a client show only that client's accounts. Don't mention other clients' results.\n- Follow each client's own voice guide when the user has one (see `brand-voice`). Don't reuse one client's voice for another.\n"
}SHA-256 of public snapshot: 125576c47ffd9c4057dd662e73a92c5e9d58c2f787068cf6c826f0f03595adea