ads-setup

Configure paid-media client profiles with data-lifecycle, privacy, and mutation-guardrail settings.

8.6k|1.3k|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/AgriciDaniel/claude-ads --skill ads-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ads-setup
Source: https://github.com/AgriciDaniel/claude-ads/tree/main/skills/ads-setup
Command: npx skills add https://github.com/AgriciDaniel/claude-ads --skill ads-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding a new advertising client requires collecting business context, account IDs, KPIs, credentials, and safety guardrails in a consistent, validated structure. This Skill standardizes that setup so every paid-media project starts with a complete, atomic, and secure configuration profile.

Core Features & Use Cases

  • Structured Onboarding: Collects business model, offer, geography, conversion taxonomy, economics, active platforms, and account IDs into a validated profile.
  • Data-Lifecycle Contract: Creates and validates data-lifecycle.json declaring classification, retention, deletion deadlines, access roles, and incident ownership before persisting anything.
  • Secret-Safe Credential Handling: Records only the presence and non-secret reference of API tokens (e.g., environment variable names), never storing secret values in generated artifacts.
  • Mutation Guardrails: Declares mutation authority, approvers, budget ceilings, and rollback owners so no live account write is ever implicitly authorized.
  • Use Case: When starting work for a new Meta Ads client, run the setup to capture their KPIs, connect export sources, and define who may approve budget changes before any audit or campaign work begins.

Quick Start

Set up a new Claude Ads client profile for my Meta Ads account, including KPIs, data sources, and approval guardrails.

Frequently Asked Questions about ads-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a new paid-media client profile?

Run the ads setup flow to collect business model, geography, conversion taxonomy, active platforms, account IDs, and KPIs. The profile is validated and written atomically beneath the project's Claude Ads state directory.

How should I store API tokens for ad platform connections?

Store secret values only in environment variables, an OS keychain, or an approved secret manager. The profile records just a non-secret reference such as {"configured": true, "source": "environment", "secret_ref": "META_API_TOKEN"}.

Does the setup profile authorize live changes to ad accounts?

No. A setup profile authorizes no live account write. Mutation authority, approvers, budget ceilings, and rollback owners must be explicitly declared, and changes remain gated behind approval and verification controls.

Can I install Claude Ads with a curl pipe to bash command?

No. Remote pipe-to-shell installation such as curl | bash or wget | sh is refused. Use the host-native plugin installer or a verified local checkout with a SHA-256 checksum validated against a trusted release channel.

What is the data-lifecycle.json file required during setup?

It is an operational contract declaring data classification, minimum retention, deletion deadlines, at-rest and in-transit controls, access owners, deletion verification, and an incident contact. It must be validated before the setup profile is persisted.