CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-ads-audiences

Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal email hashes', 'increase Facebook match rate', 'Google ads audience', 'Meta audience', 'FB audience', or any workflow that turns CRM/customer/contact data into paid ads upload lists. Skip for outbound prospecting sequences, cold email, or pure campaign copywriting.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 delivers outstanding actionability and workflow discipline — exact commands, validation gates, and failure-mode handling for a risky batch-upload domain. Its weaknesses are token efficiency and structure: ~330 lines with padded prose, and deep operational detail inlined in SKILL.md that belongs in the shared/ and recipes/ files it already points to, several of which are not present in the bundle.

Suggestions

Move the ContactOut quick reference, the LinkedIn URL backfill query ladder, and the 'Normalize LinkedIn URLs' rules into the referenced shared/ files, leaving only a one-line pointer and trigger condition in SKILL.md.

Cut the repeated '→ Read shared/upload-failure-modes.md' pointers down to a single mention in the reading guide, and trim strategic prose sections (suppression rationale, per-platform lift expectations) to one sentence each with detail in a reference file.

Compress the coverage-modes table cells (currently multi-sentence paragraphs) to short waterfall summaries, linking to a reference file for the full ladder definitions.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious operational knowledge (hash pass-through rules, provider billing behavior, platform quirks) rather than concepts Claude already knows, but at ~330 lines / 38KB it includes padded strategic prose ("Users rarely volunteer it, and a list that was never built or silently failed to sync spends budget on people who already bought") and repeats the pointer "→ Read shared/upload-failure-modes.md" five-plus times. It fits the score-3 anchor 'mostly efficient but could be tightened'; score 4 would require only minor trimming, whereas whole sections (coverage-mode table cells, expectation-setting prose) could move to reference files.

3 / 5

Actionability

Guidance is fully executable: exact CLI commands with complete input JSON (e.g., the google_ads_audiences_sync_audience_members invocation with consent fields), a copy-paste recommended play sequence, and concrete validation rules ("64-character lowercase SHA-256", "SHA-256 of `+<digits>` for Google"). This matches the score-5 anchor of copy-paste-ready commands covering common cases, including failure handling such as the append-vs-replace fallback and the one-call Meta upload pattern.

5 / 5

Workflow Clarity

The 7-step default workflow is expanded into detailed Steps 1–6 with explicit validation checkpoints: rights confirmation before spend, account discovery before every upload, the no-double-hash audit before upload, `check` before `run` for each play, and post-upload status readback with the rule "Do not say the audience worked unless create, sync, and readback status all succeeded". Error-recovery feedback loops (e.g., drop encoded LinkedIn URLs and recover vanity ones, re-run validation after fixes) satisfy the score-5 anchor for batch operations.

5 / 5

Progressive Disclosure

References are clearly signaled one level deep via the decision matrix and reading guide, but substantial content that clearly belongs in those referenced files is inlined: the full ContactOut quick reference (which simultaneously says to read shared/contactout-hash-pool.md), the LinkedIn URL backfill query ladder, and the URL-normalization rules. Additionally, none of the referenced paths (recipes/, shared/, plays/) exist in the provided bundle, so the structure cannot be verified against actual files. This fits the score-3 anchor of 'content that should be separate is inline'; it does not reach score 4's 'most content is appropriately placed'.

3 / 5

Total

16

/

20

Passed

Description

100%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 exemplary: it states concrete capabilities with named platforms, provides comprehensive natural trigger phrases including synonyms and abbreviations, and adds an explicit skip boundary that reduces conflict risk. Both 'what' and 'when' are clearly and explicitly answered.

DimensionReasoningScore

Specificity

The description lists four concrete lifecycle actions ("building, enriching, auditing, or uploading") and names the three exact platform targets ("Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences"), giving comprehensive coverage of the skill's capabilities. It matches the score-5 anchor for multiple specific concrete actions; score 4 ('minor gaps in coverage') does not apply since the full build→enrich→audit→upload pipeline plus all three platforms are enumerated.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the named actions and platforms, and 'when' via "Use this skill when... Triggers on phrases like..." with concrete trigger phrases, plus an explicit skip clause ("Skip for outbound prospecting sequences, cold email, or pure campaign copywriting"). This exceeds the score-5 anchor example, which lacks the skip boundary.

5 / 5

Trigger Term Quality

Trigger phrases include natural user language with synonyms and abbreviations: "upload this audience", "create custom audiences", "personal email hashes", "increase Facebook match rate", "Google ads audience", "Meta audience", "FB audience", plus the slash-command forms. This is comprehensive natural-term coverage per the score-5 anchor; nothing a user would plausibly say in this domain is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (B2B paid ads audience upload from CRM/contact data) with distinct triggers and an explicit skip clause that fences off adjacent skills (outbound prospecting, cold email, copywriting). Minimal conflict risk per the score-5 anchor; the description would not plausibly fire for the wrong skill.

5 / 5

Total

20

/

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

getaero-io/gtm-eng-skills

Path

skills/deepline-ads-audiences/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.