Update to Windsor.ai Instagram

{
  "description": "Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 462
    }
  ],
  "name": "instagram",
  "skill_md_contents": "---\nname: instagram\ndescription: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.\n---\n\n# Instagram (organic) via Windsor.ai\n\nWindsor.ai pulls Instagram **organic** insights from the Instagram Graph API. The\nconnector id is `instagram`. On the Instagram app the connector is already\nscoped, so you usually do not need to pass it; when a tool asks for a connector,\nuse `instagram`.\n\nThis connector is for **organic** Instagram analytics only — profile and media\ninsights. It has **no ad or cost data** (Instagram Ads live in the Meta/Facebook\nAds connector, so route ad-spend questions there), and **publishing is not\ncurrently enabled**, so treat it as read-only: if the user asks to post or\npublish, tell them that isn't available here rather than attempting it.\n\nGolden rules:\n\n- **Never guess field, account, or option names** — get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- This connector is read-only; there are no live write actions to run.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Instagram accounts are connected (each has an\nid and usually a name/username). The account must be an Instagram Professional\naccount (Business or Creator) linked to a Facebook Page. If none is connected,\nhelp the user connect: `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.\n\nIf several accounts are connected and the request is ambiguous, ask which one.\n\n## 2. Reading insights\n\n1. Call `get_fields` for `instagram` to get valid field ids. Typical ones\n   include account-level metrics (e.g. `followers_count`, `follows_count`,\n   `media_count`, reach, impressions, profile/website clicks, engagement) and\n   per-media metrics — use the exact ids returned, not these examples.\n2. Call `get_data` with `fields`, the target `account`(s), and a date range\n   (`date_from`/`date_to` or a `date_preset` like `last_7d`, `last_30d`,\n   `this_month`; append `T` to include today).\n\nInstagram date behaviour to keep in mind:\n\n- **Lifetime metrics** (e.g. total followers) ignore the date range — the API\n  always returns the latest value. Don't present them as period-specific.\n- **Daily metrics** are only available for roughly the **last 30 days**. Requests\n  for older daily data will return nothing.\n- **Stories** insights exist only for the **last 24 hours**.\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.\n\n## 3. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery tool\nand retry with correct values or report the specific error. Never invent\nfollower counts, engagement numbers, or media ids.\n"
}