← SkedCastCONTENT HISTORY
WHAT CHANGED
Update to SkedCast
Snapshot Nov 11, 2026 · 13:28 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save SkedCast and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Manage connected social accounts. Use when the user asks which accounts are connected, wants to connect a new account, or asks about posting limits and quota before a big batch.",
"included_files": [],
"name": "account-connect",
"skill_md_contents": "---\nname: account-connect\ndescription: Manage connected social accounts. Use when the user asks which accounts are connected, wants to connect a new account, or asks about posting limits and quota before a big batch.\n---\n\n# Connected Accounts\n\n## Seeing what's connected\n\nCall `list_accounts`, optionally filtered by client or platform. Each row shows the\nplatform, handle, and status. This is the source of truth for \"which accounts can I\npost to?\" — always check it before composing for a specific account. For one account\nin full — platform, handle, display name, avatar, status (including whether it needs\nre-authorisation), and owning client — call `get_account`.\n\n## Connecting a new account\n\nCall `create_connect_invite` to mint a shareable self-connect link for the requested\nplatforms. The client (or the user) opens the link and connects the account\nthemselves through each platform's official OAuth flow — SkedCast never sees their\nplatform password. The link has an expiry; mention it when sharing.\n\n## Before a big batch\n\nTwo read-only tools keep large operations safe:\n\n- **`get_posting_limits`** — per-account anti-ban cadence. Call with a\n `socialAccountId` for one account, or omit it for every active channel plus the\n tenant bypass flag. Respect these limits when pacing a batch.\n- **`get_quota`** — the adaptive quota pool: guaranteed slice, used amount, burst\n headroom, tomorrow's guarantee, and the reset clock. Read before planning any\n batch so you don't promise what the quota can't deliver.\n\n## Notes\n\n- Connecting accounts is done by the account owner through the invite link, not by\n the assistant — you mint the link, they complete the OAuth.\n- When a publish fails, `get_post_target` reports the platform's own failure reason;\n share it verbatim rather than guessing.\n"
}SHA-256 of public snapshot: 03a5ef402e44197105ab83c2747f91534a8ef4a146a2faaf17ec09b47f04ad6f