Update to Windsor.ai

{
  "description": "Report on organic social media across Instagram, Facebook Pages, TikTok, LinkedIn Pages, YouTube, Threads and Google Business Profile connected to Windsor.ai. Use for monthly social reports, best and worst posts, follower growth, reach and engagement trends, and comparing channels or periods. Read-only: does not post or change anything.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 365
    }
  ],
  "name": "social-media-report",
  "skill_md_contents": "---\nname: social-media-report\ndescription: \"Report on organic social media across Instagram, Facebook Pages, TikTok, LinkedIn Pages, YouTube, Threads and Google Business Profile connected to Windsor.ai. Use for monthly social reports, best and worst posts, follower growth, reach and engagement trends, and comparing channels or periods. Read-only: does not post or change anything.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Social Media insights\n\nRead live social media data from Instagram, Facebook Pages, TikTok, YouTube, LinkedIn Pages, Google Business Profile, and Threads through Windsor.ai and turn it\ninto a clear report, ranking, comparison, or trend. The main connector ids for this area are instagram, facebook_organic, tiktok_organic, youtube, linkedin_organic, google_my_business, threads. Other sources in the same category work the same way; find their ids with get_connectors.\n\n## Stay in scope\n- Use this skill for metrics, rankings, comparisons, trends, and breakdowns of reach, impressions, engagement (likes, comments, shares, saves), follower growth, video views, and watch time across account or page, and post or video.\n- If the user asks to create or publish something new, use the campaign-launch skill instead.\n- If the user asks to connect, reconnect, or add an account, use the get-started skill instead.\n- If the user asks for a recurring, scheduled, or automated export, use the scheduled-exports skill instead.\n\n## Resolve scope and time\n- Call get_connectors first to see which of these sources have connected accounts. If several accounts match the request, ask which one.\n- Read field ids from get_fields for the chosen connector, and get_options for date-filter columns and connector options. Never guess ids or field names.\n- Use the date range the user gave. If none, use a sensible preset (last_30d, this_month, last_7d), and state which one you used. Append T to a preset to include today.\n\n## Choose the smallest useful read\n- Channel comparison -> get_data per connector with fields [date, reach, engagement, followers], date_preset last_30d.\n- Best posts -> fields [post or media id, caption or title, engagement, reach], rank by the metric the user names (engagement rate = engagement / reach).\n- Follower trend -> fields [date, followers] over the preset; report net change.\n- Keep field sets small and request only the accounts you need. Check for truncated or paginated results before claiming complete coverage.\n\n## Accuracy guardrails\n- Organic metrics are platform-reported and not directly comparable across networks; say so when comparing.\n- Engagement rate needs a denominator; state whether you used reach or followers.\n- If a field the user wants is not in get_fields, say so rather than substituting a different metric.\n- If \"best\", \"top\", or \"worst\" lacks a metric, ask which metric should define the ranking.\n\n## Answer with evidence\nLead with the requested result, then state the account or source, the time window, and the numbers behind the conclusion. Keep internal ids and raw JSON out of the answer unless the user asks for them.\n\n## Hand-offs\nAfter a report the user is likely to want regularly, offer once to set it up as a recurring export with the scheduled-exports skill. Never offer plans, upgrades, or pricing. Never repeat an offer the user declined.\n"
}