Update to loopthink

{
  "description": "Set up loopthink after installing it, or work out why the connector shows no tools. Use when the user has just added loopthink, asks what it can do, says it has no tools, or wants to connect Google Search Console, Google Ads, GA4, Stripe, HubSpot, their own API, database or MCP server.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Set up loopthink after installing it, or work out why the connector shows no tools. Use when the user has just added loopthink, asks what it can do, says it has no tools, or wants to connect Google Search Console, Google Ads, GA4, Stripe, HubSpot, their own API, database or MCP server.\n---\n\n# Get started with loopthink\n\nloopthink is a gateway. On its own it reads nothing — it exposes the systems a\nworkspace has connected, and only the ones the signed-in person's member group\nwas granted. So a fresh install is expected to show a single tool, and the job\nof this skill is to get the first real system connected.\n\n## 1. Check what the connector already exposes\n\nList the tools of the `loopthink` server.\n\n- **Only `get_started`** — the workspace has nothing connected yet. Call that\n  tool: it returns the link to the web app and the current list of ready-made\n  connectors. Then continue with step 2.\n- **Several tools, named `<server>__<tool>`** — the workspace is set up. Tell\n  the user which servers they can reach (the part before `__`) and stop here.\n  There is nothing to configure.\n- **No tools at all** — the person is signed in but their member group was\n  granted nothing. This is not something they can fix from ChatGPT; a workspace\n  owner has to grant their group access to a server in the web app.\n\n## 2. Connect the first system\n\nSend the user to the web app; do not try to do it for them, every path needs a\nbrowser sign-in or an API key they hold.\n\n1. Open https://app.eu.loopthink.ai/mcp\n2. Pick one of the ready-made connectors:\n   - **Google Search Console**, **Google Ads** or **Google Analytics 4** — sign\n     in with Google, then pick the properties or accounts the team may see.\n   - **Stripe** or **HubSpot** — paste an API key or private app token.\n   - **Your own REST API, PostgreSQL database or MCP server** — point loopthink\n     at it and choose which tools to publish.\n3. Grant the member group access to the new server, otherwise it stays invisible\n   to everyone including its creator.\n\n## 3. Make the new tools appear here\n\nThis is the step people miss, so say it unprompted.\n\nMCP clients cache the tool list when they connect. New tools do **not** show up\non their own, and loopthink cannot push an update. After connecting a system the\nuser has to refresh the list themselves: open the connector's settings in\nChatGPT and refresh it, or remove the connector and add it again.\n\nUntil they do, listing tools here will keep returning only `get_started`.\n\n## What loopthink does not do\n\n- It does not write to the connected systems unless a workspace admin\n  explicitly published a write tool, which is off by default.\n- It does not reach anything the signed-in person's member group was not\n  granted. \"I cannot see it\" usually means \"it was not granted\", not \"it is\n  broken\".\n- Personal fields may come back masked. That is a workspace rule applied\n  server-side before the result reaches the model; there is no unmasked variant\n  to ask for.\n"
}