Update to Windsor.ai

{
  "description": "Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance: clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings. Also use when the user asks how to connect Google Search Console to ChatGPT.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 377
    }
  ],
  "name": "google-search-console",
  "skill_md_contents": "---\nname: google-search-console\ndescription: \"Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance: clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings. Also use when the user asks how to connect Google Search Console to ChatGPT.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Google Search Console via Windsor.ai\n\nWindsor.ai pulls live **read-only** Google Search Console data through the Search\nAnalytics API. The connector id is `searchconsole`. Pass `searchconsole` as the connector on every tool call; the Windsor.ai server\nserves all connectors, so it is never implied.\n\nThis connector is **read-only** organic-search analytics. It reports Search\nConsole metrics and dimensions; it does **not** cover paid search or ad cost\n(that lives in the Google Ads connector), and it does **not** submit sitemaps or\nchange any Search Console setting; there are no write actions. If asked to\nsubmit a sitemap or change settings, say that's out of scope here.\n\nGolden rules:\n\n- **Never guess field, site, or option names**; get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- Read-only connector; there are no live write actions to run.\n- Report what the user asked for, concisely.\n\n## 1. Check what is connected\n\nCall `get_connectors` to see which Search Console sites/properties are connected\n(each has an id and usually a name). If none is connected, help the user connect:\n`get_connector_authorization_url` (or `get_connector_connect_info` for the auth\ntype and steps) and give them the setup link; don't describe manual dashboard\nnavigation. If several sites are connected and the request is ambiguous, ask\nwhich one.\n\n## 2. Reading Search Console data\n\n1. Call `get_fields` for `searchconsole` to get valid field ids. Search Console\n   splits into **dimensions** (e.g. query, page/URL, country, device, search\n   appearance, date) and **metrics** (clicks, impressions, CTR, average\n   position). Use the exact ids returned, not these examples.\n2. Call `get_data` with the `fields` you need (dimensions + metrics), the target\n   site/account id(s) in `accounts`, and a date range; `date_from`/`date_to` (`\"2026-02-01\"`)\n   or a `date_preset` like `last_7d`, `last_28d`, `last_30d`, `this_month`.\n   Add `filters` for conditions (e.g. branded vs non-branded queries, a country).\n\nCommon requests → recipe:\n\n- **Search performance overview / trend:** `date` + clicks/impressions/CTR/\n  position over a preset range.\n- **Top queries or pages:** the query or page dimension + clicks/impressions,\n  then rank in your answer.\n- **By country/device:** that dimension + the metrics.\n- Position is an **average position** (lower is better); CTR is clicks ÷\n  impressions. Compute derived figures from returned fields.\n\nWatch out: Search Console data typically lags by **~2 to 3 days** (very recent days\nmay be missing or partial) and history is limited to about **16 months**. It is\n**organic** search only; there is no cost/spend data. If a field the user wants\nisn't in `get_fields`, say so rather than substituting a different metric.\n\n## 3. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/site), call the relevant discovery tool and\nretry with correct ids, or report the specific error. Never invent click counts,\npositions, query strings, or site ids.\n"
}