Update to Windsor.ai

{
  "description": "Set up recurring exports of data connected to Windsor.ai to BigQuery, Snowflake, Redshift, PostgreSQL, MySQL, Databricks, Google Sheets, Amazon S3, Azure Blob Storage and other destinations, and check existing export tasks. Use for scheduled, daily, weekly or automated exports, data pipelines and reporting feeds. Do not use for a one-off answer in the conversation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 366
    }
  ],
  "name": "scheduled-exports",
  "skill_md_contents": "---\nname: scheduled-exports\ndescription: \"Set up recurring exports of data connected to Windsor.ai to BigQuery, Snowflake, Redshift, PostgreSQL, MySQL, Databricks, Google Sheets, Amazon S3, Azure Blob Storage and other destinations, and check existing export tasks. Use for scheduled, daily, weekly or automated exports, data pipelines and reporting feeds. Do not use for a one-off answer in the conversation.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Export connected data on a schedule\n\nSet up recurring exports of connected data to a warehouse, database, spreadsheet, or cloud storage through Windsor.ai, for example daily ad spend to BigQuery, a weekly GA4 summary to Google Sheets, or Shopify orders to Snowflake.\n\n## Stay in scope\n- Use this skill for recurring, scheduled, daily, weekly, or automated exports and syncs, and for questions about existing export tasks.\n- A one-off answer is the marketing-performance-review skill, not an export.\n\n## Workflow\n1. Call get_destination_tasks to see existing exports and avoid duplicates.\n2. Call get_connectors to confirm the source connector and accounts to export.\n3. Call get_destinations to list destinations; note which have create_in_chat true and any reusable credentials.\n4. Call get_destination_setup_info for the chosen destination to get its target fields, allowed schedules, and credential_id options.\n5. Call get_fields for the source connector to get the exact field ids to export.\n6. Confirm source, accounts, fields, destination target, credential, and schedule with the user, and tell them that each run replaces matching rows in the destination target, then call create_destination_task once. If create_in_chat is false, hand the user the setup_url instead.\n\n## Rules\n- Prefer a rolling date_preset (for example last_7d) over fixed dates so each run stays fresh.\n- Never put secrets in config; sensitive values are entered by the user in the setup_url form.\n- Report the created task's id, schedule, and manage_url from the tool result.\n\n## Hand-offs\n- Reporting -> the marketing-performance-review skill. Connecting a source -> the get-started skill. Changing platform state -> the campaign-management skill.\n"
}