Update to Windsor.ai

{
  "description": "Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights: views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos. Also use when the user asks how to connect YouTube to ChatGPT.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 370
    }
  ],
  "name": "youtube",
  "skill_md_contents": "---\nname: youtube\ndescription: \"Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights: views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos. Also use when the user asks how to connect YouTube to ChatGPT.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# YouTube via Windsor.ai\n\nWindsor.ai pulls YouTube channel, playlist, and video analytics from the\nYouTube Analytics API. The connector id is `youtube`. Pass `youtube` 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** YouTube analytics. It has **no ad or cost\ndata** (YouTube Ads run through Google Ads, so route ad-spend questions\nthere), and it does **not** publish or edit videos or change channel\nsettings; there are no write actions. If asked to upload, edit, or manage\nvideos, say that's out of scope here.\n\nGolden rules:\n\n- **Never guess field, account, or option names**; get them from\n  `get_fields`, `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 YouTube channels are connected (each has\nan id and usually a channel name). If none is connected, help the user\nconnect: call `get_connector_authorization_url` (or\n`get_connector_connect_info` for the auth type and steps) and give them the\nsetup link; don't describe manual dashboard navigation. If several channels\nare connected and the request is ambiguous, ask which one.\n\n## 2. Reading YouTube data\n\n1. Call `get_fields` for `youtube` to get valid field ids; channel,\n   playlist, and video metrics (views, watch time, average view duration,\n   subscribers gained and lost, likes, comments, shares) and dimensions\n   (e.g. video title, content type, traffic source). Use the exact ids\n   returned, not these examples.\n2. If the analysis needs segmentation controls, call `get_options` to see\n   the connector's options and valid values.\n3. Call `get_data` with `fields`, the target `account`(s) (channel), and a\n   date range (`date_from`/`date_to` or a `date_preset` like `last_7d`,\n   `last_30d`, `last_Xd`/`last_Xw`/`last_Xm`, `this_month`, `this_year`,\n   `last_year`; append `T` to include today, e.g. `last_30dT`). For ranges\n   without a preset (e.g. \"this quarter\"), compute explicit `date_from`/\n   `date_to`. Add `filters` as needed, e.g. to isolate Shorts vs. regular\n   videos.\n\nCommon requests → recipe:\n\n- **Channel overview / trend:** fields `date` + the metrics, over a preset\n  range.\n- **Top / worst videos:** fields `video` (or video title) + the metric\n  (e.g. watch time), then rank; return only what was asked.\n- **Shorts vs. regular videos:** fields for content type/format + the\n  metric (e.g. average view percentage), grouped by format.\n- **Traffic sources:** fields for traffic source + views, over the\n  requested range.\n\nIf a metric the user wants isn't in `get_fields`, say so rather than\nsubstituting a different one. There is no cost/spend data here, and\nYouTube Ads questions belong in the Google Ads connector.\n\n## 3. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery\ntool and retry with correct ids, or report the specific error. Never invent\nview counts, subscriber numbers, watch-time figures, or video ids.\n"
}