Update to SimplePost for Social Media
Snapshot Oct 31, 2026 · 00:18 UTC · version 3.1.0
Collection source: downloaded plugin package.
Instructions updated for setup
Skill instructions — Now says: Use the platform the user already named; otherwise ask which platform they want to connect. Show that platform's URL from the workspace's `connectionLinks`...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 28, 2026 · 12:14 UTC
Send the user to the workspace's `accountsUrl` to connect at least one platform using SimplePost's existing OAuth flow. Do not call posting tools before they return. Refresh the workspace after the user connects an account.
Oct 31, 2026 · 00:18 UTC
Use the platform the user already named; otherwise ask which platform they want to connect. Show that platform's URL from the workspace's `connectionLinks` as a clickable “Connect X” (or the chosen platform) link, copied unchanged. These...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -7,7 +7,13 @@ Open `open_simplepost_workspace` and inspect its connected accounts and preferences. -If no social platform is connected, explain that connecting the assistant does not connect a publishing destination. Send the user to the workspace's `accountsUrl` to connect at least one platform using SimplePost's existing OAuth flow. Do not call posting tools before they return. Refresh the workspace after the user connects an account. +If no social platform is connected, explain that connecting the assistant does not connect a publishing destination. Use the platform the user already named; otherwise ask which platform they want to connect. Show that platform's URL from the workspace's `connectionLinks` as a clickable “Connect X” (or the chosen platform) link, copied unchanged. These links expire after one hour; refresh the workspace or `list_accounts` for a new link when needed. Never construct a connection URL yourself. + +For OAuth platforms, the link goes straight to provider authorization if the user is already signed into SimplePost; otherwise they sign into SimplePost first and continue automatically. They must use the same SimplePost account connected to this assistant. Manual platforms open their setup form in SimplePost. Never ask for social passwords, API keys, or tokens in chat. + +Ask the user to approve access in the browser, then return to this conversation and say “connected”. Do not promise automatic return or claim the connection succeeded before checking. Refresh the workspace or call `list_accounts` after they return, verify the requested platform appears with usable credentials, and continue with their first draft. If it is still missing, explain that the connection did not finish and offer a fresh link. Do not call posting tools before a destination is connected. + +When a returning user asks to add another destination, use the same `connectionLinks` flow without repeating the rest of setup. If platform links are unavailable, use the workspace's `accountsUrl` or `list_accounts`'s `connectAccountsUrl` as the generic account-picker fallback. If accounts already exist, preserve them and offer to continue with existing drafts. Do not force returning users through setup again.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: setup\ndescription: Set up SimplePost by connecting at least one social platform, configuring timezone preferences, and saving the first draft without publishing.\n---\n\n# Set up SimplePost\n\nOpen `open_simplepost_workspace` and inspect its connected accounts and preferences.\n\nIf no social platform is connected, explain that connecting the assistant does not connect a publishing destination. Send the user to the workspace's `accountsUrl` to connect at least one platform using SimplePost's existing OAuth flow. Do not call posting tools before they return. Refresh the workspace after the user connects an account.\n\nIf accounts already exist, preserve them and offer to continue with existing drafts. Do not force returning users through setup again.\n\nKeep an existing timezone preference. On first use, the workspace automatically saves the browser’s IANA timezone; do not ask users to confirm it. Ask only if their timezone cannot be inferred or they request a change. Save requested changes and optional default destinations with `update_simplepost_settings`; timezone changes do not move existing scheduled posts.\n\nOpen `open_post_editor`. Help the user write and preview one draft for their connected destinations. Use the editor's current session and revision when proposing changes. The user can apply the proposal and save the draft in the editor.\n\nSetup is complete when at least one destination is connected, the timezone is configured, and a draft is saved. Do not publish, schedule, discard, or retry a post as part of setup unless the user explicitly asks.\n\nIf extension tools are unavailable, use `list_accounts`, the SimplePost accounts web handoff, and the existing draft/preview tools. Never invent IDs, file references, or access tokens.\n"
"---\nname: setup\ndescription: Set up SimplePost by connecting at least one social platform, configuring timezone preferences, and saving the first draft without publishing.\n---\n\n# Set up SimplePost\n\nOpen `open_simplepost_workspace` and inspect its connected accounts and preferences.\n\nIf no social platform is connected, explain that connecting the assistant does not connect a publishing destination. Use the platform the user already named; otherwise ask which platform they want to connect. Show that platform's URL from the workspace's `connectionLinks` as a clickable “Connect X” (or the chosen platform) link, copied unchanged. These links expire after one hour; refresh the workspace or `list_accounts` for a new link when needed. Never construct a connection URL yourself.\n\nFor OAuth platforms, the link goes straight to provider authorization if the user is already signed into SimplePost; otherwise they sign into SimplePost first and continue automatically. They must use the same SimplePost account connected to this assistant. Manual platforms open their setup form in SimplePost. Never ask for social passwords, API keys, or tokens in chat.\n\nAsk the user to approve access in the browser, then return to this conversation and say “connected”. Do not promise automatic return or claim the connection succeeded before checking. Refresh the workspace or call `list_accounts` after they return, verify the requested platform appears with usable credentials, and continue with their first draft. If it is still missing, explain that the connection did not finish and offer a fresh link. Do not call posting tools before a destination is connected.\n\nWhen a returning user asks to add another destination, use the same `connectionLinks` flow without repeating the rest of setup. If platform links are unavailable, use the workspace's `accountsUrl` or `list_accounts`'s `connectAccountsUrl` as the generic account-picker fallback.\n\nIf accounts already exist, preserve them and offer to continue with existing drafts. Do not force returning users through setup again.\n\nKeep an existing timezone preference. On first use, the workspace automatically saves the browser’s IANA timezone; do not ask users to confirm it. Ask only if their timezone cannot be inferred or they request a change. Save requested changes and optional default destinations with `update_simplepost_settings`; timezone changes do not move existing scheduled posts.\n\nOpen `open_post_editor`. Help the user write and preview one draft for their connected destinations. Use the editor's current session and revision when proposing changes. The user can apply the proposal and save the draft in the editor.\n\nSetup is complete when at least one destination is connected, the timezone is configured, and a draft is saved. Do not publish, schedule, discard, or retry a post as part of setup unless the user explicitly asks.\n\nIf extension tools are unavailable, use `list_accounts`, the SimplePost accounts web handoff, and the existing draft/preview tools. Never invent IDs, file references, or access tokens.\n"
Full snapshot data
{
"description": "Set up SimplePost by connecting at least one social platform, configuring timezone preferences, and saving the first draft without publishing.",
"included_files": [],
"name": "setup",
"skill_md_contents": "---\nname: setup\ndescription: Set up SimplePost by connecting at least one social platform, configuring timezone preferences, and saving the first draft without publishing.\n---\n\n# Set up SimplePost\n\nOpen `open_simplepost_workspace` and inspect its connected accounts and preferences.\n\nIf no social platform is connected, explain that connecting the assistant does not connect a publishing destination. Use the platform the user already named; otherwise ask which platform they want to connect. Show that platform's URL from the workspace's `connectionLinks` as a clickable “Connect X” (or the chosen platform) link, copied unchanged. These links expire after one hour; refresh the workspace or `list_accounts` for a new link when needed. Never construct a connection URL yourself.\n\nFor OAuth platforms, the link goes straight to provider authorization if the user is already signed into SimplePost; otherwise they sign into SimplePost first and continue automatically. They must use the same SimplePost account connected to this assistant. Manual platforms open their setup form in SimplePost. Never ask for social passwords, API keys, or tokens in chat.\n\nAsk the user to approve access in the browser, then return to this conversation and say “connected”. Do not promise automatic return or claim the connection succeeded before checking. Refresh the workspace or call `list_accounts` after they return, verify the requested platform appears with usable credentials, and continue with their first draft. If it is still missing, explain that the connection did not finish and offer a fresh link. Do not call posting tools before a destination is connected.\n\nWhen a returning user asks to add another destination, use the same `connectionLinks` flow without repeating the rest of setup. If platform links are unavailable, use the workspace's `accountsUrl` or `list_accounts`'s `connectAccountsUrl` as the generic account-picker fallback.\n\nIf accounts already exist, preserve them and offer to continue with existing drafts. Do not force returning users through setup again.\n\nKeep an existing timezone preference. On first use, the workspace automatically saves the browser’s IANA timezone; do not ask users to confirm it. Ask only if their timezone cannot be inferred or they request a change. Save requested changes and optional default destinations with `update_simplepost_settings`; timezone changes do not move existing scheduled posts.\n\nOpen `open_post_editor`. Help the user write and preview one draft for their connected destinations. Use the editor's current session and revision when proposing changes. The user can apply the proposal and save the draft in the editor.\n\nSetup is complete when at least one destination is connected, the timezone is configured, and a draft is saved. Do not publish, schedule, discard, or retry a post as part of setup unless the user explicitly asks.\n\nIf extension tools are unavailable, use `list_accounts`, the SimplePost accounts web handoff, and the existing draft/preview tools. Never invent IDs, file references, or access tokens.\n"
}SHA-256 of public snapshot: 57832e423ba5b1369d32d0ae9103882e8411ec6194ad0031f3d911c189697447