What does this skill do, and when should you use it?
This skill supports the activation phase of paid advertising by preparing brand-safety controls before spend starts. It covers site, app, channel, network opt-out, content-suitability, and sensitive-topic exclusions. It consumes the audience exclusion set produced by the audience-segment-builder and packages evidence for the ROAS A1 brand and placement safety gate. It does not build target audiences, re-derive audience exclusions, calculate RQS, or issue the A1 verdict.
Reads the account or campaign goal, brand-safety constraints, placement report, and campaign and search-terms reports; identifies low-quality, off-brand, made-for-advertising, or irrelevant sites, apps, and channels when placement data is available; decides on Search-partner, Display-expansion, and Audience-network opt-outs; lists content-suitability tiers, sensitive topics, and keyword blocks; references the audience exclusion set from audience-segment-builder; and packages the placement report plus rationale-backed exclusion decisions as an A1 evidence file with a handoff summary. If the placement report is missing, it marks the work NEEDS_INPUT.
- A paid media manager preparing a Google Ads or other advertising campaign needs to remove unsafe or irrelevant placements before launch.
- A brand with rules against news, politics, user-generated content, or tragedy adjacency needs reusable topic and content blocks.
- An advertising team preparing for a ROAS A1 review needs to organize placement evidence and exclusion rationales.
- An ad operator has audience segments already defined but needs to align placement and network controls with them.
How do you install this skill?
- Confirm the placements report, account goal, sensitive-topic constraints, and audience-exclusion dependency before use; without the placements report the result should remain NEEDS_INPUT.
- Do not treat the A1 evidence package as an audit verdict, and do not re-derive the audience exclusion set in this skill.
- Reconcile the skill's 18.0.0 version with SECURITY.md's 17.x support statement, and manually verify network choices, content-suitability tiers, and exclusions on the actual platforms.
- Minimize or redact personal data, audience identifiers, and platform credentials before providing account exports.
- Local filesystem
For Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On other Agent Skills-compatible hosts, run npx skills add aaron-he-zhu/aaron-marketing-skills, or clone the repository with git clone https://github.com/aaron-he-zhu/aaron-marketing-skills. The skill is located at ad/activate/placement-exclusion-manager/SKILL.md.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/ad/activate/placement-exclusion-manager" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Provide the account or campaign goal, platforms, brand-safety constraints, and a placement report. Example: Build brand-safety exclusion lists for [goal] on [platforms] before launch. Here is my placements report: [paste/path]. To package audit evidence, use: Package the A1 brand/placement-safety evidence for the auditor from this placements + campaign export: [paths].
What are this skill's strengths and limitations?
- Covers placements, sites, apps, channels, network opt-outs, content suitability, and sensitive-topic blocks.
- Separates measured findings from the placement report from user-provided constraints.
- Packages exclusion decisions and rationales into evidence for the A1 gate.
- Works with pasted or exported user data and does not require paid advertising APIs.
- The placement report is a load-bearing input; without it, A1 evidence cannot be built and the result is NEEDS_INPUT.
- It does not create or re-derive audience exclusion sets and depends on audience-segment-builder for that work.
- It does not calculate RQS or issue a Pass, Partial, or Fail decision for A1.
- The supplied material provides no platform-specific test results or standalone test suite evidence.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Brand Safety Exclusion Manager this page | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Ad Fatigue & Frequency Manager | 58 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Paid Ads Campaign Architect | 57 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Paid Ads Audience Segment Builder | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Creator Content Auditor | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill treats exports as untrusted data, forbids following embedded instructions, stops A1 evidence construction when the placements report is absent, saves only after user confirmation, and keeps connectors optional. Deductions reflect missing detail on sensitive-data handling, exact pre-write confirmation, rollback, and external-platform mutation boundaries; publisher identity is unverified.
The contract, input dependencies, NEEDS_INPUT behavior, scope guard, and handoff path are clear, with repository-level tests and CI evidence. Static review cannot reproduce the key path, and malformed-report handling, platform-rule failures, and output/error diagnostics are not sufficiently specified; the static cap keeps this at 9.
Audience, trigger phrases, inputs, outputs, non-goals, and multi-platform use cases are clearly stated, including a manual-export path without connectors. Deductions reflect limited Chinese-language coverage, no evidence of mainland-China platform reachability, and insufficiently specified differences among platform exclusion fields and policies.
The skill provides versioning, Apache-2.0 licensing, a shared contract structure, quick starts, input/output notes, references, a save template, and repository documentation. Deductions reflect no skill-specific changelog, clearly assigned maintainer, or explicit update path; SECURITY.md says the supported line is 17.x while the skill and README state 18.0.0.
The skill targets a concrete task and produces exclusion lists, content and sensitive-topic blocks, an A1 evidence package, and a handoff summary while avoiding audience construction and audit verdicts; missing reports do not default to pass. Deductions reflect no skill-specific representative output or third-party execution evidence, and insufficient output-template detail means manual review may remain substantial; the static cap keeps this at 7.
The skill identifies placements, campaign/search-term exports, contract references, and security guidance, and distinguishes measured report data from user constraints. Deductions reflect no dedicated tests, sample result, or independent third-party validation, while static reading cannot establish end-to-end reproducibility; the static cap keeps this at 5.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →