placement-exclusion-manager

Use when the user asks to "build my brand-safety exclusion lists", "set placement / topic / content exclusions before launch", "add network and audience exclusions", or "prep the A1 brand-safety evidence for the auditor"; produces a placement/network exclusion list, a content-suitability & sensitive-topic block list, an audience/negative-audience exclusion set, and a packaged A1 brand/placement-safety evidence file for the gate. Not for building the audiences you target — use audience-segment-builder; not for computing the RQS or issuing the A1 verdict — use ad-account-auditor. 品牌安全/排除位置/否定受众列表

Quality

100%

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

100%Weight 40%Scale 1-3

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-sequenced instruction skill with explicit validation gates and cleanly signaled references. It balances conciseness with actionable specificity throughout.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what brand-safety or exclusions are, and every section earns its tokens. Minor redundancy between the 'Scope guard' and step 6's negative scope is not enough to drop below the lean-and-efficient anchor.	3 / 3
Actionability	Concrete numbered steps, specific save paths (memory/ad/placement-exclusion-manager/YYYY-MM-DD-...), explicit connectors (~~ad platform), and a clear Reads/Writes/Done-when contract give fully actionable guidance; absence of executable code is unpenalized for an instruction-only skill per the rubric.	3 / 3
Workflow Clarity	The 7-step sequence has explicit validation checkpoints (mark A1 evidence Unknown, stop with NEEDS_INPUT, 'do not infer a safe list'), a Done-when gate, and a scope guard — matching the anchor for clear sequence with explicit validation and feedback loops.	3 / 3
Progressive Disclosure	Content is organized into well-signaled sections with one-level-deep references to real reference docs (roas-benchmark.md, CONNECTORS.md, SECURITY.md, skill-contract.md); no bundle directories exist but the SKILL.md stays an overview pointing outward rather than inlining detail.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and explicitly disambiguated from sibling skills, answering both what and when without padding. It is among the strongest examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete deliverables — 'placement/network exclusion list', 'content-suitability & sensitive-topic block list', 'audience/negative-audience exclusion set', and 'packaged A1 brand/placement-safety evidence file' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what it produces (the four exclusion/evidence artifacts) and when to use it via an explicit 'Use when...' clause with quoted triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	Embeds natural trigger phrases a user would actually say ('build my brand-safety exclusion lists', 'set placement / topic / content exclusions before launch', 'add network and audience exclusions', 'prep the A1 brand-safety evidence for the auditor'), giving good coverage of real phrasings.	3 / 3
Distinctiveness Conflict Risk	The 'Not for building the audiences you target — use audience-segment-builder; not for computing the RQS or issuing the A1 verdict — use ad-account-auditor' disambiguation carves a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 18 suspicious	Warning

	Total	13 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: ad/activate/placement-exclusion-manager/SKILL.md
Commit: 4a77c48

Reviewed: 9 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.