Update to Windsor.ai

{
  "description": "Analyze Facebook Page (organic) performance through Windsor.ai. Use when the user asks about their Facebook Page's organic insights: reach, impressions, engagement, reactions, follows/fans, or the performance of individual posts, videos, and Reels, by date/week/month or by country. It can also publish a photo post or a text and link post to a Page, always after the user approves the full draft. Do not use for Facebook Ads (those live in the Meta/Facebook Ads connector), boosting posts, Instagram, or other platforms. Also use when the user asks how to connect Facebook Pages (Facebook organic) to ChatGPT.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 379
    }
  ],
  "name": "facebook-pages",
  "skill_md_contents": "---\nname: facebook-pages\ndescription: \"Analyze Facebook Page (organic) performance through Windsor.ai. Use when the user asks about their Facebook Page's organic insights: reach, impressions, engagement, reactions, follows/fans, or the performance of individual posts, videos, and Reels, by date/week/month or by country. It can also publish a photo post or a text and link post to a Page, always after the user approves the full draft. Do not use for Facebook Ads (those live in the Meta/Facebook Ads connector), boosting posts, Instagram, or other platforms. Also use when the user asks how to connect Facebook Pages (Facebook organic) to ChatGPT.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Facebook Organic (Pages) via Windsor.ai\n\nWindsor.ai pulls Facebook **Page organic** insights from the Facebook Graph API.\nThe connector id is `facebook_organic`. Pass `facebook_organic` as the connector on every tool call; the Windsor.ai server\nserves all connectors, so it is never implied.\n\nReads are the main job. The connector also exposes write actions, currently\n`create_post` and `create_photo_post` (the live set is whatever `list_actions`\nreturns). It has **no ad or cost data** (Facebook Ads live in the Meta/Facebook\nAds connector, so route ad-spend and boost requests there), it does not cover\nInstagram, and it does not change Page settings; say those are out of scope\nhere.\n\nGolden rules:\n\n- **Never guess field, page, or option names**; get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- **Publishing is public and immediate.** Show the full post text (and the\n  photo URL) and call `execute_action` only after an explicit yes.\n- Report what the user asked for, concisely.\n\n## 1. Check what is connected\n\nCall `get_connectors` to see which Facebook Pages are connected (each has an id\nand 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 Pages are connected and the request is ambiguous, ask\nwhich one.\n\n## 2. Reading Page insights\n\n1. Call `get_fields` for `facebook_organic` to get valid field ids. These span\n   Page-level metrics (reach, impressions, engaged users, follows/fans, video\n   and Reels plays) and post-level fields (reactions, comments, shares, clicks,\n   post reach/impressions). Use the exact ids returned, not these examples.\n2. Call `get_data` with `fields`, the target Page/`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). Add `filters` as needed.\n\nFacebook Organic specifics to respect:\n\n- **One broken-down (segmented) metric per request.** The connector can't return\n  multiple broken-down metrics in one call; request them separately and combine\n  in your answer rather than asking for several at once.\n- **Weekly/monthly aggregation.** Requesting a week field (`week_iso`/\n  `year_week_iso`, or `week`/`year_week`) returns one row per week; a month field\n  (`month`/`year_month`) one row per month. Facebook **deduplicates** unique\n  metrics (reach, unique impressions) over the period, so use the week/month\n  field for weekly/monthly totals; do **not** sum daily rows, which over-counts\n  uniques.\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 a post\n\n1. Call `get_connectors` to pick the Page; ask if several are connected.\n2. Call `list_actions` for `facebook_organic` and read the schema of\n   `create_post` or `create_photo_post`; a photo post needs a publicly\n   reachable image URL.\n3. Draft the post as text first and show it in full, exactly as it will\n   appear, then wait for an explicit yes. Never publish placeholder text.\n4. Call `execute_action` once and report the result from the tool, including\n   any post id or URL it returns.\n5. If the action is refused because write actions are not enabled for the\n   account, send the user to https://onboard.windsor.ai/app/settings/account\n   and retry after they confirm.\n\n## 4. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/page), call the relevant discovery tool and\nretry with correct ids, or report the specific error. Never invent reach,\nengagement, follower counts, post ids, or post text.\n"
}