ads-setup creates the client profile that every other Claude Ads skill works from. It collects the business model, offer, geography, regulated categories, objective, conversion taxonomy, economics, active platforms, account IDs, date conventions and reporting audience.
It records whether credentials are present without storing their values, writes and validates a data lifecycle contract, declares who may approve changes and within which ceilings, and saves the validated profile in the project’s Claude Ads state directory. The profile authorizes no live account write.
What You Get
- A validated client and account profile saved in the project’s Claude Ads state directory
- A data-lifecycle.json covering classification, retention, deletion, access, encryption evidence and incident owner
- Declared approvers, budget and policy ceilings and a rollback owner
- Secret presence recorded as a non-secret reference such as an environment variable name
- Facts, decisions and assumptions kept apart
Common Use Cases
- Starting a new advertising client before a first audit
- Declaring KPIs and conversion definitions for a project
- Connecting exports or read adapters while keeping tokens out of files
- Setting approval limits before any campaign change is drafted
What Makes It Unique
It refuses to put API keys, tokens, cookies or passwords in the brand profile or any generated artifact, and stores only a reference to where a secret lives. It also refuses remote pipe-to-shell installs such as curl piped to bash, and points to the host’s native plugin installer or a checksum-verified archive. The data lifecycle contract is described as an operating record and not as legal advice.
Under The Hood
The skill is written instructions with no scripts of its own. The agent asks you questions, reads the main ads contract, creates and validates data-lifecycle.json, and writes the setup profile as files inside the project’s Claude Ads state directory. It does not call ad platform APIs or change accounts. Websites and uploaded material are treated as untrusted data, and secret values are never printed, logged or committed.