paid-ads-setup

Connect NotFair paid-ad accounts and establish reusable campaign context. Use when setting up paid media in a new workspace, connecting Google, Meta, X, LinkedIn, Reddit, or TikTok Ads, refreshing brand context, or preparing an agent to work on ads safely.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 a tight, well-structured setup workflow that assumes Claude's intelligence and concentrates on what the model would not already know (platform-specific boundaries, the exact context checklist, and the gap-register handoff). Verification checkpoints and the explicit non-destructive guard make the workflow robust. The only mild gap is a couple of abstract/delegated steps in actionability.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with zero padding: every line is actionable instruction ('Do not alter campaigns during setup', 'List only accounts actually returned by the connected surface'), assumes Claude's competence, and never explains concepts Claude already knows.	5 / 5
Actionability	Concrete, specific guidance throughout (numbered steps, named platforms, exact data fields like 'target CPA or break-even ROAS, margin, and customer value'), but a few steps are abstract or delegated ('Read project documents that are clearly marketing-relevant', 'verify... from live data'), leaving minor gaps versus fully copy-paste-ready instruction.	4 / 5
Workflow Clarity	Three clearly sequenced phases (Establish access, Capture decision-quality context, Finish with a gap register) with explicit verification checkpoints ('verify the requested platform and account from live data', 'check the available tools before proposing a connection') and a gap-register checklist for error surfacing; the skill is explicitly non-destructive ('Do not alter campaigns during setup'), so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	A 31-line single-purpose skill organized into three well-headed sections, with one-level-deep, clearly signaled references (../shared/operating-contract.md, ../../docs/mcp-connection.md) and explicit handoff links to sibling skills; no nested references. Per the simple-skill exception this scores 5 with well-organized sections and no bundle files to traverse.	5 / 5
	Total	19 / 20 Passed

Description

91%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.

The description is strong: it pairs a concise what-statement with a rich, natural-language when-clause enumerating concrete platforms and scenarios. It uses third-person imperative voice with no first/second-person drift. The only soft spot is slight overlap risk with adjacent paid-ads skills.

Dimension	Reasoning	Score
Specificity	Names two concrete actions ('Connect NotFair paid-ad accounts and establish reusable campaign context') plus a platform enumeration, which is several specific actions with only minor coverage gaps; not the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicitly answers both what ('Connect NotFair paid-ad accounts and establish reusable campaign context') and when ('Use when setting up paid media... or preparing an agent to work on ads safely') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrasing a user would actually say is comprehensive: 'setting up paid media', 'connecting Google, Meta, X, LinkedIn, Reddit, or TikTok Ads', 'refreshing brand context', 'preparing an agent to work on ads safely'.	5 / 5
Distinctiveness Conflict Risk	The paid-ad-setup niche and setup-specific triggers are mostly distinct from sibling skills, but 'preparing an agent to work on ads' could overlap with paid-ads-review/launch, leaving minor overlap risk rather than the clean niche of a 5.	4 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: nowork-studio/notfair-plugin
Path: paid-ads/paid-ads-setup/SKILL.md
Commit: 5094263

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.