Update to Your Social Hub

{
  "description": "Connect and authorize the Your Social Hub connector, and diagnose missing tools, 401s or \"not found\" errors. Use right after installing this plugin, when the Your Social Hub tools are absent or failing, or when the user says \"connect to Your Social Hub\", \"authorize YSH\", \"reconnect\", \"I don't see the hub tools\".",
  "included_files": [],
  "name": "connect",
  "skill_md_contents": "---\nname: connect\ndescription: Connect and authorize the Your Social Hub connector, and diagnose missing tools, 401s or \"not found\" errors. Use right after installing this plugin, when the Your Social Hub tools are absent or failing, or when the user says \"connect to Your Social Hub\", \"authorize YSH\", \"reconnect\", \"I don't see the hub tools\".\n---\n\n# Connecting Your Social Hub\n\nRead `hub-model` for what the tools reach and what the scopes buy.\n\n## Before you start\n\nThe user needs a Your Social Hub account at <https://yoursocialhub.online> **and** the `content_creator` or `admin` role in at least one hub. A reviewer-only account can sign in, consent and list hubs, but hub-addressed tools and resources return \"not found\" because the role is too low.\n\nState the ceiling up front so nothing surprises them: this connector can read hubs, content calendars, content and ideas, and can create or edit drafts and ideas. It cannot publish, schedule, approve, reject or delete anything, and it cannot upload media.\n\n## Authorize\n\nOpen the Your Social Hub plugin connection in the host application's plugin settings and authenticate. A browser opens: sign in to Your Social Hub, then approve the requested scopes on the consent screen.\n\nThe consent screen lists each scope with a checkbox, all pre-ticked. What each one buys:\n\n| Scope                     | On the consent screen      | Unlocks                                    |\n| ------------------------- | -------------------------- | ------------------------------------------ |\n| `hubs:read`               | See your hubs              | `list_hubs` — lets workflows discover hub ids |\n| `content-calendars:read`  | See your content calendars | `list_content_calendars` — lets calendar workflows discover calendar ids |\n| `content:read`            | Read your content          | `list_content`, `get_content`              |\n| `ideas:read`              | Read your ideas            | `list_ideas`, `get_idea`                   |\n| `content-calendars:write` | Create content calendars   | `create_content_calendar`                  |\n| `content:write`           | Draft and edit content     | `create_content`, `update_content`         |\n| `ideas:write`             | Create and edit ideas      | `create_idea`, `update_idea`               |\n| both write scopes         | —                          | `promote_idea_to_content`                  |\n| `metrics:read`            | Read your metrics          | `list_social_accounts`, `get_hub_metrics_overview`, `list_top_performing_posts` |\n\nFour consequences worth saying out loud before they click:\n\n- **`hubs:read` and `content-calendars:read` are discovery scopes for calendar-based workflows.** Without them, the plugin cannot discover the hub or calendar ids those workflows need. Other MCP tools remain independently scope-gated and can work when the caller already has an authorized id.\n- **`promote_idea_to_content` needs `content:write` and `ideas:write` together.** Grant only one and the plugin's central workflow silently does not exist.\n- **`restore_file` appears under either write scope** but refuses per call for files on the other side, e.g. `ideas:write` alone cannot restore a content file.\n- **`metrics:read` is the one scope a role can override.** Its three tools also need the `admin` role on the hub, matching the app's admin-only metrics dashboard — a `content_creator` who ticks the box still gets \"not found\" from all three.\n\n## Verify\n\nCall `list_hubs`. Then list which of the 16 tools are actually present and tell the user plainly which workflows that leaves them:\n\n- no `hubs:read` **or** no `content-calendars:read` → calendar-based workflows cannot discover their starting ids; other MCP operations need known authorized ids and their own scopes;\n- all four content reads → `calendar-audit` works in full; `plan-week`, `draft-captions` and `promote-to-review` do not;\n- reads plus `ideas:write` → planning and drafting work, nothing reaches the review queue;\n- `ideas:read` missing → `plan-week` and `draft-captions` cannot see the backlog they date and rewrite;\n- `metrics:read` granted but `yourRole` is not `admin` → `metrics-review` and `top-posts-to-ideas` are unavailable in practice; say it is the role, not the consent.\n\n## Troubleshooting\n\n| Symptom                                                | Cause                                                      | Fix                                                                              |\n| ------------------------------------------------------ | ---------------------------------------------------------- | -------------------------------------------------------------------------------- |\n| A tool is missing from the toolset                     | Its scope was not granted                                  | Reconnect the Your Social Hub plugin and approve the needed scope                |\n| `\"Not found, or you do not have access to it.\"`        | Wrong id, another user's hub, or no `content_creator` role | Check the id and the membership in the app. Do not retry with other ids          |\n| The same error from the metrics tools only             | The role is `content_creator`; metrics need `admin`        | Ask a hub admin to raise the role, or run the metrics dashboard in the app       |\n| Calendar workflows cannot find a calendar              | `content-calendars:read` was not granted                   | Re-authorize and approve \"See your content calendars\"                           |\n| `list_hubs` returns `{items: []}`                       | The account belongs to no hub                              | Create or join a hub in the app                                                  |\n| 401 mid-session                                        | Token expired, or the Connection was revoked               | Re-authenticate; check Profile & Billing → Connected Apps                        |\n| `restore_file` errors with \"content:write is required\" | Only `ideas:write` was granted                             | Re-authorize with both write scopes                                              |\n| Server unreachable / connection failed                 | Endpoint or network, not consent                           | Confirm <https://yoursocialhub.online> is up; retry the connect                  |\n\nTo disconnect: Profile & Billing → **Connected Apps** → revoke. That deletes the grant and its tokens.\n"
}