CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./ad/activate/placement-exclusion-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 presents a clear, well-sequenced workflow with strong failure-path handling and concrete decision guidance, appropriate for a contract-style orchestration skill. Its weaknesses are redundancy (scope boundaries and the missing-report rule repeated three to four times) and heavy dependence on reference files that are not part of the bundle, including for the shape of its primary deliverable.

Suggestions

State the scope boundary (owns placement/network/content-suitability exclusions + A1 evidence only; audience exclusions and the RQS/A1 verdict belong to sibling skills) once in a single Scope section, and cut its repetitions from the intro paragraph, step 6, and the Scope guard; likewise state the NEEDS_INPUT/Unknown rule once and reference it.

Add a short inline template or annotated example of the A1 evidence file (the report reference + exclusion decisions with rationale) so the primary deliverable's shape does not depend entirely on the external roas-benchmark.md evidence contract.

Fix or bundle the reference paths: no references/ directory, CONNECTORS.md, or SECURITY.md ships with the skill, and the multi-hop ../../../ relative paths break when the skill is installed standalone — either include the load-bearing templates in the bundle or point to stable, skill-relative locations.

DimensionReasoningScore

Conciseness

There is no tutorial filler, but the scope boundary (audience exclusions owned by audience-segment-builder; RQS/A1 verdict owned by ad-account-auditor) is repeated in the intro paragraph, step 6, and the Scope guard, and the "NEEDS_INPUT / mark A1 evidence Unknown" rule is stated four times (Skill Contract, Data Sources, step 2, Next Best Skill) — the body could be tightened by roughly a third without losing information.

3 / 5

Actionability

Steps are concretely executable for an instruction-only skill — e.g. "flag low-quality, off-brand, made-for-advertising… with a one-line rationale each (label each Measured from the report vs User-provided constraint)", named network toggles (Search-partner, Display-expansion, Audience-network), and a concrete save path — but the primary deliverable (the A1 evidence file) has no inline format or example, only a pointer to an external reference.

4 / 5

Workflow Clarity

Seven steps are clearly sequenced with an explicit failure checkpoint ("If it is absent, mark qualified A1 evidence Unknown, stop the run with NEEDS_INPUT, and do not infer a safe list from the campaign export alone") and a "Done when" checklist, but there is no step validating that the packaged evidence file is complete before handoff, so it stops short of the explicit-validation anchor.

4 / 5

Progressive Disclosure

Sections are well organized with a clearly labeled one-level-deep Reference Materials list, but the skill ships no bundle — every referenced path (../../../references/skill-contract.md, ../../../references/roas-benchmark.md, ../../../CONNECTORS.md, ../../../SECURITY.md, sibling SKILL.md files) is a multi-hop relative path to files not present in the skill directory, so navigation is fragile and the templates the body depends on cannot be verified.

4 / 5

Total

15

/

20

Passed

Description

88%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 explicit what/when structure, quoted natural trigger phrases, and clear negative-scope routing to sibling skills. Its one real defect is internal: it claims to produce an audience/negative-audience exclusion set, which the skill body contradicts (that set is owned by audience-segment-builder and only referenced here).

DimensionReasoningScore

Specificity

The description lists four concrete deliverables — "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" — which is comprehensive, specific coverage of the niche, matching the top anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: "Use when the user asks to …" for when, and "produces …" enumerating the outputs for what — the exact pattern of the top anchor, clearly above the anchor-4 example where 'when' is less specific.

5 / 5

Trigger Term Quality

Four quoted natural user phrasings ("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") give good keyword coverage, but common synonyms such as "blocklist" or "block sites/apps" are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Explicit negative-scope clauses ("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") create a mostly distinct niche, but claiming to produce "an audience/negative-audience exclusion set" overlaps the sibling skill that owns audience exclusions (the body says this skill only consumes that set), leaving minor conflict risk rather than minimal.

4 / 5

Total

18

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

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.