Update to Windsor.ai

{
  "description": "Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights: followers, reach, views, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics. Also use when the user asks how to connect Instagram to ChatGPT.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 377
    }
  ],
  "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, views, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics. Also use when the user asks how to connect Instagram to ChatGPT.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Instagram (organic) via Windsor.ai\n\nWindsor.ai pulls Instagram **organic** insights from the Instagram Graph API. The\nconnector id is `instagram`. Pass `instagram` as the connector on every tool call; the Windsor.ai server\nserves all connectors, so it is never implied.\n\nThis connector covers **organic** Instagram: profile and media insights, plus\npublishing and comment moderation. It has **no ad or cost data** (Instagram Ads\nlive in the Meta/Facebook Ads connector, so route ad-spend questions there).\nWrite actions today are `create_image_post`, `create_carousel_post`,\n`create_video_post`, `create_story`, `create_comment`, `reply_to_comment`,\n`hide_comment`, `unhide_comment` and `delete_comment`; the live set is whatever\n`list_actions` returns.\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- **Publishing and comment changes are public and immediate.** Show the exact\n  caption, media URLs, or reply text and call `execute_action` only after an\n  explicit yes. `delete_comment` cannot be undone; prefer `hide_comment` unless\n  the user asks to delete.\n- Report what the user asked for, concisely.\n\n## 1. Check what is connected\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, views, 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 id(s) in `accounts`, 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- Instagram no longer returns impressions (`impressions` and\n  `media_impressions` come back empty or 0); use `views` and `media_views`.\n- Some **daily metrics** (for example `follower_count_1d`) only go back about\n  **30 days**; check the field description. Others, such as reach, return\n  older dates.\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. Publishing and moderating comments\n\n1. Call `get_connectors` to pick the account; ask if several are connected.\n2. Call `list_actions` for `instagram` and build the params from the returned\n   schema. Media must be publicly reachable URLs (images JPEG, videos MP4 or\n   MOV); a carousel takes 2 to 10 images; a story takes exactly one image or\n   video. Comment actions need a `media_id` or `comment_id` from a `get_data`\n   read, never a guessed id.\n3. Show the post or the comment change in full, exactly as it will appear, and\n   wait for an explicit yes. Never publish placeholder text.\n4. Call `execute_action` once and report the result from the tool, including\n   any media or comment id it returns.\n5. If commenting is refused with a permission error, the account was connected\n   before comment access was added: ask the user to reconnect it with\n   `get_connector_authorization_url`. If write actions are not enabled for the\n   account, send the user to https://onboard.windsor.ai/app/settings/account.\n\n## 4. 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"
}