TypingMindTypingMindThe best frontend for AI
Ad Syncs logo

Ad Syncs

Organization
clay-run
ad-syncs

Clay ad syncs — push an audience segment to ad platforms (LinkedIn, Meta, Google, Bing, Reddit, Vibe) as a custom audience. Use to create, edit, pause, or map the fields of an ad sync, or to check its status, match rate, or run history.

Overview

Publisherclay-run
Repositoryagent-plugins
Skill namead-syncs
Stars
145
Forks
24
Bundled files
1
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by clay-run on GitHub. Read the source before you install it.

Installation

Install the Ad Syncs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/clay-run/agent-plugins/tree/main/clay/skills/ad-syncs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/clay-run/agent-plugins.git /tmp/agent-plugins
mkdir -p .claude/skills
cp -r /tmp/agent-plugins/clay/skills/ad-syncs .claude/skills/ad-syncs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ad Syncs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ad Syncs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ad Syncs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ad syncs

An ad sync pushes an audience segment to ad accounts on ad platforms, called its destinations. Each platform matches the records and builds an audience to advertise to.

Supported commands

  • clay ad-syncs list [--limit <n>] [--cursor <cursor>]
  • clay ad-syncs get <adSyncId>
  • clay ad-syncs get-by-source --source-id <segmentId> --entity-type <people|companies>
  • clay audiences get <segmentId>
  • clay ad-syncs create --name <name> --source-id <segmentId> --entity-type <people|companies> --schedule-type <ONE_TIME|RECURRING>
  • clay ad-syncs update <adSyncId> [--name <name>] [--schedule <ONE_TIME|RECURRING>] [--tier <PREMIUM|STANDARD>]
  • clay app-accounts list --filter type=<provider>-ad-audience
  • clay ad-syncs ad-accounts list <appAccountId> --provider <provider>
  • clay ad-syncs destinations create <adSyncId> --provider <provider> --app-account-id <appAccountId> --ad-account-id <accountId> [--ad-user-data-consent <status> --ad-personalization-consent <status>]
  • clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> [--app-account-id <appAccountId>] [--ad-account-id <accountId>] [--ad-user-data-consent <status>] [--ad-personalization-consent <status>]
  • clay ad-syncs destinations delete <adSyncId> --destination-id <destinationId>
  • clay ad-syncs field-mapping update <adSyncId> --input '<json>'
  • clay ad-syncs pause <adSyncId>
  • clay ad-syncs runs list <adSyncId> [--limit <n>]

Run clay ad-syncs <subcommand> --help before a subcommand's first use. It has the exact output shape, value sets, and error codes. <provider> is LinkedIn, Meta, Google, Bing, Reddit, or Vibe, written in lowercase inside type=<provider>-ad-audience (e.g. type=linkedin-ad-audience). An <accountId> is an accountId from ad-accounts list, and a <destinationId> is a providerSyncConfigs[].id from get.

Limits

  • You can always create an ad sync, and edit it while it is a draft or paused.
  • You cannot delete an ad sync: the user deletes it in the Clay app. A segment can have only one ad sync, so create one only for a segment the user confirmed.
  • Pause a running sync only when the user asks. Before running pause, tell them what pausing does (see Statuses) and ask them to confirm, even when they asked for it. Never start or resume one: the user does that in the Clay app, from the sync's url.

Schedules

  • ONE_TIME: it exports once, when the user starts it.
  • RECURRING: it syncs continuously to its destinations, so they stay up to date with the people or companies the user wants to target.

Statuses

Tell the user the label in parentheses, not the raw value.

  • DRAFT (Draft): not started yet.
  • PROCESSING (Processing): an export is running, including enrichment when the sync has a tier.
  • ACTIVE (Active): a recurring sync whose latest export reached every destination. It exports again on its schedule.
  • DONE (Exported): a one-time sync that reached every destination.
  • WARNING (Warning): some destinations failed. A one-time sync reached only some of them, or a later export of a recurring sync failed on at least one, and the sync stays live. runs list shows which destinations failed.
  • FAILED (Failed): a one-time sync that failed on every destination, or a recurring sync whose first export failed on any destination.
  • BULK_ENRICHMENT_FAILED (Enrichment failed): the enrichment step failed.
  • PAUSED (Paused): the user paused it. Clay stops enriching new records in the segment, so it stops spending credits, and stops pushing new records to the ad platforms. The audiences already on the platforms stay as they are until the user resumes the sync in the Clay app.

Create

Confirm each choice with the user before running the command that makes it.

  1. Draft. Read the segment's entityType with clay audiences get <segmentId>, then run clay ad-syncs get-by-source --source-id <segmentId> --entity-type <entityType>. If it returns a sync, use that one. If it returns not_found, ask whether the sync should run once or on a recurring schedule, and create it:

    bash
    clay ad-syncs create --name "<name>" --source-id <segmentId> --entity-type <entityType> --schedule-type <ONE_TIME|RECURRING>

  2. Accounts. For each platform, run clay app-accounts list --filter type=<provider>-ad-audience. If it returns one connection, pick it. If it returns more than one, list them by name and ask the user which to use. Don't check any connection's ad accounts before the user picks one, even if you expect only one to work.

    You MUST check the picked connection before using it, every time, including when it is the only one: run clay ad-syncs ad-accounts list <appAccountId> --provider <provider>. Never pass an --app-account-id to any command until that check has succeeded for it in this conversation. If the check errors, don't use the connection: tell the user it couldn't load its ad accounts and ask them to pick another one.

    An ad account is usable when canManageAudiences is true, restrictions is empty, and it has not already been added to this ad sync: compare its accountId with the providerSyncConfigs[].providerAdAccount.id values from clay ad-syncs get <adSyncId>. If there are none, the user sets them up in the Clay app from the sync's url. Continue once they're done.

  3. Destinations. Ask which ad accounts to advertise to, then add each one:

    bash
    clay ad-syncs destinations create <adSyncId> --provider <provider> --app-account-id <appAccountId> --ad-account-id <accountId>

    Company syncs go to LinkedIn only. For Google, ask the user for both consent values and add --ad-user-data-consent <status> --ad-personalization-consent <status>. Send UNSPECIFIED if they don't track consent.

  4. Enrichment tier (people syncs only). Best match rates is clay ad-syncs update <adSyncId> --tier PREMIUM, Good match rates is clay ad-syncs update <adSyncId> --tier STANDARD, and none means skipping this step. A tier costs credits and can't be changed once set. To see what each tier costs, the user opens the sync's url in the Clay app.

  5. Field mapping. Read field-mapping.md and follow it.

Then give the user the sync's url so they can review it and start it in the Clay app.

Edit

Check adSync.status with clay ad-syncs get <adSyncId> first. DRAFT and PAUSED syncs can be edited. A running sync (PROCESSING, ACTIVE, or WARNING) has to be paused first. Tell the user it has to be paused and what pausing does, and ask them to confirm before running clay ad-syncs pause <adSyncId>. DONE, FAILED, and BULK_ENRICHMENT_FAILED syncs can't be edited.

  • Rename: clay ad-syncs update <adSyncId> --name "<name>"
  • Change the schedule: clay ad-syncs update <adSyncId> --schedule <ONE_TIME|RECURRING>
  • Set a tier, only if it has none: clay ad-syncs update <adSyncId> --tier <PREMIUM|STANDARD>
  • Add a destination: follow steps 2 and 3 of Create.
  • Change the ad account for a destination: clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> --ad-account-id <accountId>, adding --app-account-id <appAccountId> if that ad account is under another connection. The synced audience will then exist in a different ad account, so confirm the change with the user first. A Google destination needs both consent flags again when its ad account changes.
  • Switch the connection a destination syncs through, keeping its ad account: clay ad-syncs destinations update <adSyncId> --destination-id <destinationId> --app-account-id <appAccountId>
  • Remove a destination, on drafts only: clay ad-syncs destinations delete <adSyncId> --destination-id <destinationId>
  • Change the field mapping: follow field-mapping.md.

A paused sync stays paused. The edit takes effect once the user resumes it in the Clay app.

Read

  1. Find the sync with clay ad-syncs list, paging with --cursor <cursor>, or with clay ad-syncs get-by-source --source-id <segmentId> --entity-type <people|companies> when the user names the segment.
  2. Read its setup with clay ad-syncs get <adSyncId>.
  3. Read its results with clay ad-syncs runs list <adSyncId> --limit 100. The default returns only the 20 newest runs across all destinations, so a destination's latest run can be missing without the higher limit. If a destination has no run in the result, say so rather than guessing. Report each destination's latest run in plain words (status, match rate, and audience size), and link the sync's url.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ad Syncs AI skill do?

Clay ad syncs — push an audience segment to ad platforms (LinkedIn, Meta, Google, Bing, Reddit, Vibe) as a custom audience. Use to create, edit, pause, or map the fields of an ad sync, or to check its status, match rate, or run history.

Why use Ad Syncs on TypingMind?

Because you install it once and use it with any model. Ad Syncs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ad Syncs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/clay-run/agent-plugins/tree/main/clay/skills/ad-syncs. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ad Syncs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ad Syncs?

As many as you like. As long as a model supports skills, you can use Ad Syncs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ad Syncs AI skill free?

It is published on GitHub by clay-run. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Pptx Author

NousResearch
OrganizationPopular

Build PowerPoint decks headless with python-pptx.

53.5K
250.4K
Instructions
View
NousResearch logo

Pokemon Player

NousResearch
OrganizationPopular

Play Pokemon via headless emulator + RAM reads.

53.5K
250.4K
Instructions
View
anthropics logo

Docx

anthropics
OrganizationPopular

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document',…

21.8K
184K
59 files
View
openclaw logo

Openclaw Docker E2e Authoring

openclaw
OrganizationPopular

Author OpenClaw Docker E2E and live provider Docker lanes.

82.2K
391K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇