← PostZenCONTENT HISTORY
WHAT CHANGED
Update to PostZen
Snapshot Nov 4, 2026 · 00:12 UTC · version 1.0.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save PostZen 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": "Connect a new social media account to PostZen (X, Instagram, TikTok, LinkedIn, Facebook, YouTube, Threads, Pinterest, Bluesky, Telegram) or review/disconnect existing connections.",
"included_files": [],
"name": "connect",
"skill_md_contents": "---\nname: connect\ndescription: Connect a new social media account to PostZen (X, Instagram, TikTok, LinkedIn, Facebook, YouTube, Threads, Pinterest, Bluesky, Telegram) or review/disconnect existing connections.\n---\n\n# Connect a social account to PostZen\n\nWalk the user through linking a social account so posts can target it. The user's request follows: \"$ARGUMENTS\"\n\n## Workflow\n\n1. **Show current state.** Call `listAccounts` and summarize what's already connected (platform + username) so the user doesn't double-connect.\n2. **Start the connection.** Call `createConnectUrl` for the requested platform. Give the user the returned auth URL as a clickable link and tell them to open it in their browser, sign in to the platform, and approve access. Do not try to complete the OAuth flow for them.\n3. **Finish and verify.** The browser callback completes authorization. After the user says they have approved, call `listAccounts` again. Never request or exchange authorization codes in chat. Check the resulting account's `status` — not just that it appears. Potential pitfall:\n - A `connected` status proves auth, not publishing. If the user is connecting because publishing failed, suggest a quick test post (a draft, or a real post they confirm) to exercise the publish path. Sometimes users will forget to approve all permissions requested by the platform's OAuth flow.\n4. **Platform-specific follow-ups:**\n - **Pinterest**: after connecting, a default board should be selected — use `listPinterestBoardsForSelection` and `selectPinterestBoard` (or `createPinterestBoard` for a new one). The board-selection window is time-limited, so do this right after connecting.\n - **Bluesky**: uses an app password rather than OAuth — direct the user to the connect URL, where they'll paste an app password generated in their Bluesky settings. Never ask the user to paste the app password into this chat.\n\n## Disconnecting\n\n`disconnectAccount` removes a connection. Confirm with the user first — scheduled posts targeting that account will no longer be able to publish.\n\n## Cautions\n\n- Never ask for or handle the user's social media passwords, app passwords, or tokens directly; the browser-based connect flow is the only path.\n- If a connection repeatedly fails, point the user to the PostZen dashboard (https://app.postzen.dev) where the same flow exists with more error detail.\n"
}SHA-256 of public snapshot: 212d8e9deefd0df16fe0d003ccea309a9b7b0fc07a28023fc4c52cde9dd88d1b