Update to loopthink

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,62 +1,55 @@
 ---
 name: get-started
-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.
+description: Set up loopthink for Google Search Console and Google Ads, or work out why it returns no data. Use when the user has just added loopthink, asks what it can do, gets a "connect it at …" message, or cannot find one of their properties or accounts.
 ---
 
 # Get started with loopthink
 
-loopthink is a gateway. On its own it reads nothing — it exposes the systems a
-workspace has connected, and only the ones the signed-in person's member group
-was granted. So a fresh install is expected to show a single tool, and the job
-of this skill is to get the first real system connected.
-
-## 1. Check what the connector already exposes
-
-List the tools of the `loopthink` server.
-
-- **Only `get_started`** — the workspace has nothing connected yet. Call that
-  tool: it returns the link to the web app and the current list of ready-made
-  connectors. Then continue with step 2.
-- **Several tools, named `<server>__<tool>`** — the workspace is set up. Tell
-  the user which servers they can reach (the part before `__`) and stop here.
-  There is nothing to configure.
-- **No tools at all** — the person is signed in but their member group was
-  granted nothing. This is not something they can fix from ChatGPT; a workspace
-  owner has to grant their group access to a server in the web app.
-
-## 2. Connect the first system
-
-Send the user to the web app; do not try to do it for them, every path needs a
-browser sign-in or an API key they hold.
-
-1. Open https://app.eu.loopthink.ai/mcp
-2. Pick one of the ready-made connectors:
-   - **Google Search Console**, **Google Ads** or **Google Analytics 4** — sign
-     in with Google, then pick the properties or accounts the team may see.
-   - **Stripe** or **HubSpot** — paste an API key or private app token.
-   - **Your own REST API, PostgreSQL database or MCP server** — point loopthink
-     at it and choose which tools to publish.
-3. Grant the member group access to the new server, otherwise it stays invisible
-   to everyone including its creator.
-
-## 3. Make the new tools appear here
-
-This is the step people miss, so say it unprompted.
-
-MCP clients cache the tool list when they connect. New tools do **not** show up
-on their own, and loopthink cannot push an update. After connecting a system the
-user has to refresh the list themselves: open the connector's settings in
-ChatGPT and refresh it, or remove the connector and add it again.
-
-Until they do, listing tools here will keep returning only `get_started`.
-
-## What loopthink does not do
-
-- It does not write to the connected systems unless a workspace admin
-  explicitly published a write tool, which is off by default.
-- It does not reach anything the signed-in person's member group was not
-  granted. "I cannot see it" usually means "it was not granted", not "it is
-  broken".
-- Personal fields may come back masked. That is a workspace rule applied
-  server-side before the result reaches the model; there is no unmasked variant
-  to ask for.
+loopthink reads Google Search Console and Google Ads through the properties and
+accounts a workspace has connected, and only the ones the signed-in person's
+member group was granted. The tools are always the same:
+
+- `loopthink_status`: what is connected, and the link to connect the rest
+- `gsc_list_sites`, `gsc_search_analytics`, `gsc_sitemaps`
+- `google_ads_list_accounts`, `google_ads_report`
+
+## 1. Find out what is connected
+
+Call `loopthink_status`.
+
+- **A source shows `connected: true`.** Use its list tool (`gsc_list_sites` or
+  `google_ads_list_accounts`) and pass the `siteUrl` or `customerId` exactly as
+  returned to the report tools.
+- **A source shows `connected: false`.** Give the user its `connectUrl` and
+  continue with step 2.
+
+## 2. Connect a source
+
+Send the user to the link. Do not try to do it for them: it needs a Google
+sign-in in their browser.
+
+1. Sign in to loopthink and add Google Search Console or Google Ads.
+2. Sign in with the Google account that has access to the properties or accounts.
+3. Pick the ones the team may use.
+
+Then ask the question again. The tools do not change, so nothing needs
+refreshing in ChatGPT.
+
+## 3. A property or account is missing
+
+- It was not picked when the source was connected: an admin adds it on the
+  server in the loopthink web app.
+- The person's member group was not granted it: an admin grants it.
+- The Google account behind the connection cannot see it.
+
+## Notes for answering
+
+- Search Console query data (the `QUERY` dimension) is only available when the
+  workspace enabled it on the connection. Without it, group by page, country,
+  device or date.
+- Search Console data lags by about two days. For the most recent days pass
+  `dataState: "all"` and say that those numbers can still change.
+- Google Ads cost comes as `cost_micros`: divide by 1,000,000 for the account's
+  currency.
+- Everything is read-only. loopthink cannot change campaigns, budgets or
+  keywords, submit sitemaps or add properties.