CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ads-setup

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, well-sequenced instruction-only workflow with strong safety boundaries and one concrete JSON example. Its weakness is incomplete executability: the central artifacts lack schemas, and mandated validation steps have no specified method or failure path.

Suggestions

Add a minimal schema or template for the setup profile (and the required fields of `data-lifecycle.json`) so the primary artifact is concretely defined rather than left to inference.

Specify how to validate the profile and `data-lifecycle.json` — a command, script, or checklist of pass criteria — plus what to do when validation fails, closing the missing feedback loop in workflow_clarity.

Give the concrete location of "the project's Claude Ads state directory" and a path or pointer for the referenced main `ads` contract and `ads-dna` skill, and move the floating paragraph on observed facts / operator decisions / provisional assumptions under its own heading.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and directive throughout: it never explains concepts Claude already knows, and every line states a domain-specific requirement, boundary, or example ("never store credential values, cookies, tokens, customer lists, or raw exports"; "Refuse remote pipe-to-shell installation, including `curl | bash` and `wget | sh`"). It matches the anchor-5 profile of assuming competence with every token earning its place; there is no padded or over-explained passage to justify a 4.

5 / 5

Actionability

Some guidance is concrete and executable — named artifacts (`data-lifecycle.json`, `brand-profile.json`), a copy-paste JSON snippet for secret references, and a specific verified-archive install procedure — but key details are missing: the setup profile's schema is never shown, "Create and validate" and "Validate the profile" give no validation command or criteria, and "the project's Claude Ads state directory" has no path. This matches anchor 3 (concrete but incomplete, missing key details) rather than anchor 4, whose gaps would be minor.

3 / 5

Workflow Clarity

The six numbered steps form a clear sequence with validation checkpoints explicitly ordered ("Create and validate `data-lifecycle.json` before persisting the setup profile"; "Validate the profile and write it atomically"), matching anchor 4. It falls short of anchor 5 because there is no error-recovery feedback loop (what to do when validation fails) and the validation method itself is unspecified, though validation steps are present so the missing-validation cap at 3 does not apply.

4 / 5

Progressive Disclosure

As an under-50-line single-file skill with no bundle files, the simple-skill exception applies, and the body is mostly well-organized (numbered workflow plus a dedicated "Secret and install boundary" section). It misses anchor 5 on organization details: the important guidance "Distinguish observed facts, operator decisions, and provisional assumptions" floats un-headered after the steps, and the reference to "the main `ads` contract" and `ads-dna` gives no path or location.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit "Use for" trigger list, third-person voice, and a clearly defined paid-media onboarding niche. Its main weaknesses are a few abstract composite terms in the capability list and some generic trigger phrases that slightly widen conflict risk and leave natural-synonym coverage incomplete.

DimensionReasoningScore

Specificity

The description enumerates several concrete setup actions and components ("Set up a paid-media client, account, data-source, privacy, and mutation-guardrail profile", "API tokens or credential profiles", "connecting exports or read adapters", "declaring KPIs"), but a few objects like "privacy... profile" and "mutation-guardrail profile" are abstract composites rather than distinct concrete actions, so it falls short of comprehensive.

4 / 5

Completeness

It clearly answers "what" ("Set up a paid-media client, account, data-source, privacy, and mutation-guardrail profile for Claude Ads") and explicitly answers "when" with a "Use for..." clause containing concrete trigger phrases ("onboarding", "curl-pipe-bash install requests", "preparing a new advertising project"). This matches the anchor-5 example structure; a 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The "Use for" list covers many natural phrases ("onboarding", "initial configuration", "API tokens", "keychain setup", "declaring KPIs", "preparing a new advertising project"), giving good keyword coverage. It stops short of anchor 5 because common synonyms like "ad account", "paid advertising", "PPC", or platform names are absent and a few terms ("read adapters", "mutation-guardrail") are internal jargon users would not naturally say.

4 / 5

Distinctiveness Conflict Risk

The niche is clear ("Claude Ads", "paid-media", "advertising project") with distinctive triggers ("curl-pipe-bash install requests", "connecting exports"), but generic trigger phrases like "onboarding", "initial configuration", and "environment-variable or keychain setup" create minor overlap risk with sibling setup or credential-management skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AgriciDaniel/claude-ads

Path

skills/ads-setup/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.