agentleFS
Sign inStart free
windsor-aiwindsor-ai/claude-windsor-ai-plugin/skills/windsor-export/SKILL.md

windsor-export

Skill1 starsChanged 50 days agoMITView on GitHub

Set up and review recurring exports and syncs of data from any source connected to Windsor.ai (ads, organic social, analytics, CRM, e-commerce, finance) to warehouses, databases, spreadsheets, BI tools, or cloud storage - BigQuery, Snowflake, Redshift, PostgreSQL, MySQL, Google Sheets, Looker Studio, Amazon S3, and more. Use for scheduled, daily, hourly, weekly, or automated exports, data pipelines, and reporting feeds, and to check the status of existing export tasks. Do not use for a one-off answer in the conversation.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for recurring, scheduled, daily, weekly, or automated exports and syncs, and for questions about existing export tasks.

    line 11
  2. Distinctive:

    Call get_destination_tasks to see existing exports and avoid duplicates.

    line 15
  3. Distinctive:

    Call get_connectors to confirm the source connector and accounts to export.

    line 16
  4. Distinctive:

    Call get_destinations to list destinations.

    line 17
  5. Distinctive:

    Call get_destination_setup_info for the chosen destination to get its target fields, allowed schedules, and credential_id options.

    line 18
  6. Distinctive:

    Call get_fields for the source connector to get the exact field ids to export.

    line 19
  7. Distinctive:

    Prefer a rolling date_preset (for example last_7d) over fixed dates so each run stays fresh.

    line 23
  8. Distinctive:

    Never put secrets in config.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Export connected data on a schedule

Set 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.

Stay in scope

  • Use this skill for recurring, scheduled, daily, weekly, or automated exports and syncs, and for questions about existing export tasks.
  • A one-off answer is /windsor-insights, not an export.

Workflow

  1. Call get_destination_tasks to see existing exports and avoid duplicates.
  2. Call get_connectors to confirm the source connector and accounts to export.
  3. Call get_destinations to list destinations; note which have create_in_chat true and any reusable credentials.
  4. Call get_destination_setup_info for the chosen destination to get its target fields, allowed schedules, and credential_id options.
  5. Call get_fields for the source connector to get the exact field ids to export.
  6. Confirm source, accounts, fields, destination target, credential, and schedule with the user, then call create_destination_task once. If create_in_chat is false, hand the user the setup_url instead.

Rules

  • Prefer a rolling date_preset (for example last_7d) over fixed dates so each run stays fresh.
  • Never put secrets in config; sensitive values are entered by the user in the setup_url form.
  • Report the created task's id, schedule, and manage_url from the tool result.

Hand-offs

  • Reporting -> /windsor-insights. Connecting a source -> /windsor-connect. Changing platform state -> /windsor-manage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free