Menu

Individual skill

ads-setup

0upvotes

Set up a paid-media client, account, data-source, privacy, and mutation-guardrail profile for Claude Ads. Use for onboarding, initial configuration, API tokens or credential profiles, environment-variable or keychain setup, connecting exports or read adapters, safe native or verified-local installation, curl-pipe-bash install requests, declaring KPIs, or preparing a new advertising project.

skills/ads-setup/SKILL.md

Read pinned source

Source commit fc3908e786c318776df89a3a098333da377364be

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
10,902
Repository last updated
Nov 1, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Paid Media Setup

1. Read the main `ads` contract. Website-derived brand profiles belong to `ads-dna`.
2. Collect business model, offer, geography, regulated categories, objective,
   conversion taxonomy, economics, active platforms, account IDs, date/time
   conventions, and reporting audience.
3. Record data-source type and whether required credentials are present, but never
   store credential values, cookies, tokens, customer lists, or raw exports.
4. Create and validate `data-lifecycle.json` before persisting the setup profile.
   Declare classification; explicit minimum retention and purpose-bound deletion
   deadline or documented exception; verified at-rest/in-transit controls and
   evidence; access owner and roles; deletion method and verification; and private
   incident owner/channel. This is an operational contract, not legal advice or a
   claim of regulatory compliance.
Back to top