← loopthinkCONTENT HISTORY

Update to loopthink

Snapshot Nov 11, 2026 · 00:08 UTC · version 0.4.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Skill instructions — Now says: - `loopthink_status`: what is connected, and the link to connect the rest (optional `goal`: the user's request) Call `loopthink_status` and pass the user's...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save loopthink and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 9, 2026 · 12:07 UTC

- `loopthink_status`: what is connected, and the link to connect the rest Call `loopthink_status`.

After

Nov 11, 2026 · 00:08 UTC

- `loopthink_status`: what is connected, and the link to connect the rest (optional `goal`: the user's request) Call `loopthink_status` and pass the user's request in one sentence as `goal` (optional, but it tells loopthink which data so...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -9,13 +9,14 @@
 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
+- `loopthink_status`: what is connected, and the link to connect the rest (optional `goal`: the user's request)
 - `gsc_list_sites`, `gsc_search_analytics`, `gsc_sitemaps`
 - `google_ads_list_accounts`, `google_ads_report`
 
 ## 1. Find out what is connected
 
-Call `loopthink_status`.
+Call `loopthink_status` and pass the user's request in one sentence as `goal`
+(optional, but it tells loopthink which data source the user needs).
 
 - **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
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: 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.\n---\n\n# Get started with loopthink\n\nloopthink reads Google Search Console and Google Ads through the properties and\naccounts a workspace has connected, and only the ones the signed-in person's\nmember group was granted. The tools are always the same:\n\n- `loopthink_status`: what is connected, and the link to connect the rest\n- `gsc_list_sites`, `gsc_search_analytics`, `gsc_sitemaps`\n- `google_ads_list_accounts`, `google_ads_report`\n\n## 1. Find out what is connected\n\nCall `loopthink_status`.\n\n- **A source shows `connected: true`.** Use its list tool (`gsc_list_sites` or\n  `google_ads_list_accounts`) and pass the `siteUrl` or `customerId` exactly as\n  returned to the report tools.\n- **A source shows `connected: false`.** Give the user its `connectUrl` and\n  continue with step 2.\n\n## 2. Connect a source\n\nSend the user to the link. Do not try to do it for them: it needs a Google\nsign-in in their browser.\n\n1. Sign in to loopthink and add Google Search Console or Google Ads.\n2. Sign in with the Google account that has access to the properties or accounts.\n3. Pick the ones the team may use.\n\nThen ask the question again. The tools do not change, so nothing needs\nrefreshing in ChatGPT.\n\n## 3. A property or account is missing\n\n- It was not picked when the source was connected: an admin adds it on the\n  server in the loopthink web app.\n- The person's member group was not granted it: an admin grants it.\n- The Google account behind the connection cannot see it.\n\n## Notes for answering\n\n- Search Console query data (the `QUERY` dimension) is only available when the\n  workspace enabled it on the connection. Without it, group by page, country,\n  device or date.\n- Search Console data lags by about two days. For the most recent days pass\n  `dataState: \"all\"` and say that those numbers can still change.\n- Google Ads cost comes as `cost_micros`: divide by 1,000,000 for the account's\n  currency.\n- Everything is read-only. loopthink cannot change campaigns, budgets or\n  keywords, submit sitemaps or add properties.\n"
AFTER
"---\nname: get-started\ndescription: 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.\n---\n\n# Get started with loopthink\n\nloopthink reads Google Search Console and Google Ads through the properties and\naccounts a workspace has connected, and only the ones the signed-in person's\nmember group was granted. The tools are always the same:\n\n- `loopthink_status`: what is connected, and the link to connect the rest (optional `goal`: the user's request)\n- `gsc_list_sites`, `gsc_search_analytics`, `gsc_sitemaps`\n- `google_ads_list_accounts`, `google_ads_report`\n\n## 1. Find out what is connected\n\nCall `loopthink_status` and pass the user's request in one sentence as `goal`\n(optional, but it tells loopthink which data source the user needs).\n\n- **A source shows `connected: true`.** Use its list tool (`gsc_list_sites` or\n  `google_ads_list_accounts`) and pass the `siteUrl` or `customerId` exactly as\n  returned to the report tools.\n- **A source shows `connected: false`.** Give the user its `connectUrl` and\n  continue with step 2.\n\n## 2. Connect a source\n\nSend the user to the link. Do not try to do it for them: it needs a Google\nsign-in in their browser.\n\n1. Sign in to loopthink and add Google Search Console or Google Ads.\n2. Sign in with the Google account that has access to the properties or accounts.\n3. Pick the ones the team may use.\n\nThen ask the question again. The tools do not change, so nothing needs\nrefreshing in ChatGPT.\n\n## 3. A property or account is missing\n\n- It was not picked when the source was connected: an admin adds it on the\n  server in the loopthink web app.\n- The person's member group was not granted it: an admin grants it.\n- The Google account behind the connection cannot see it.\n\n## Notes for answering\n\n- Search Console query data (the `QUERY` dimension) is only available when the\n  workspace enabled it on the connection. Without it, group by page, country,\n  device or date.\n- Search Console data lags by about two days. For the most recent days pass\n  `dataState: \"all\"` and say that those numbers can still change.\n- Google Ads cost comes as `cost_micros`: divide by 1,000,000 for the account's\n  currency.\n- Everything is read-only. loopthink cannot change campaigns, budgets or\n  keywords, submit sitemaps or add properties.\n"
Full snapshot data
{
  "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.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: 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.\n---\n\n# Get started with loopthink\n\nloopthink reads Google Search Console and Google Ads through the properties and\naccounts a workspace has connected, and only the ones the signed-in person's\nmember group was granted. The tools are always the same:\n\n- `loopthink_status`: what is connected, and the link to connect the rest (optional `goal`: the user's request)\n- `gsc_list_sites`, `gsc_search_analytics`, `gsc_sitemaps`\n- `google_ads_list_accounts`, `google_ads_report`\n\n## 1. Find out what is connected\n\nCall `loopthink_status` and pass the user's request in one sentence as `goal`\n(optional, but it tells loopthink which data source the user needs).\n\n- **A source shows `connected: true`.** Use its list tool (`gsc_list_sites` or\n  `google_ads_list_accounts`) and pass the `siteUrl` or `customerId` exactly as\n  returned to the report tools.\n- **A source shows `connected: false`.** Give the user its `connectUrl` and\n  continue with step 2.\n\n## 2. Connect a source\n\nSend the user to the link. Do not try to do it for them: it needs a Google\nsign-in in their browser.\n\n1. Sign in to loopthink and add Google Search Console or Google Ads.\n2. Sign in with the Google account that has access to the properties or accounts.\n3. Pick the ones the team may use.\n\nThen ask the question again. The tools do not change, so nothing needs\nrefreshing in ChatGPT.\n\n## 3. A property or account is missing\n\n- It was not picked when the source was connected: an admin adds it on the\n  server in the loopthink web app.\n- The person's member group was not granted it: an admin grants it.\n- The Google account behind the connection cannot see it.\n\n## Notes for answering\n\n- Search Console query data (the `QUERY` dimension) is only available when the\n  workspace enabled it on the connection. Without it, group by page, country,\n  device or date.\n- Search Console data lags by about two days. For the most recent days pass\n  `dataState: \"all\"` and say that those numbers can still change.\n- Google Ads cost comes as `cost_micros`: divide by 1,000,000 for the account's\n  currency.\n- Everything is read-only. loopthink cannot change campaigns, budgets or\n  keywords, submit sitemaps or add properties.\n"
}

SHA-256 of public snapshot: 4517f3f325d465c42f394f3a56d4f8b7c8ab468d3c155909e81c0dc5477be767