{"id":13909,"plugin_id":"plugin_asdk_app_6aa1e36d0a108191b38d12b95e3d5568","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:08:25.631Z","digest":"fb832c695da98e8bdaaa5743b8d9eea0214af69ecb9cd3a493b8449eaf00a280","against":null,"payload":{"name":"manage-channels","description":"List connected social media channels and check what the caller may do with them in BulkPublish. Use when the user asks about their connected accounts.","included_files":[],"skill_md_contents":"---\nname: manage-channels\ndescription: List connected social media channels and check what the caller may do with them in BulkPublish. Use when the user asks about their connected accounts.\n---\n\n# BulkPublish — Connected Channels\n\n## Tools\n\n| Tool | Use for | Key params |\n|---|---|---|\n| `list_channels` | Connected accounts as data | `active` (default true) |\n| `view_channels` | The same list as an interactive view | none |\n\nPrefer `view_channels` when the user wants to look at their accounts, and\n`list_channels` when you need the IDs to build a post.\n\n## What comes back\n\nEach channel carries its ID, platform, account name and connection status. Use\nthe channel ID in `create_post` — never the account name.\n\nThe response also carries a `capabilities` object saying whether this caller may\ncreate, publish or approve posts. Check it before attempting a write, rather\nthan discovering the limit from a 403.\n\n## Reconnecting\n\nA channel can be connected but no longer usable, because the account's\nauthorization expired or was revoked on the platform's side. Those channels are\nflagged in the response. A publish to one will fail, so surface it before\nscheduling: tell the user which account needs reconnecting and that it is done\nin BulkPublish under Channels. You cannot reconnect an account from here.\n\n## LinkedIn\n\nA LinkedIn channel is either a personal profile or a company page\n(`accountType`: `personal` / `organization`). Both are posted to the same way,\nbut they are gated separately — one can be unavailable while the other works.\nWhen that is what blocks a write, the 403 `PLATFORM_DISABLED` error names the\n`accountType`.\n\n## Notes\n\n- `active: false` includes channels the user has switched off.\n- If the user has no channels, say so plainly and point them to connecting one\n  in BulkPublish; do not invent channel IDs.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}