CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

campaign-structure-auditor

Audits Google Ads account structure including ad group strategy, keyword duplication, match type distribution, and naming conventions. Use when auditing campaigns, reviewing account structure, finding duplicate keywords, or checking naming conventions.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/campaign-structure-auditor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 concrete, mostly-executable GAQL queries and quantified decision rules with tight, table-driven writing, but it is a monolithic 340-line file with no progressive disclosure and no validation checkpoints around its batch data pulls. One GAQL query uses an unsupported subquery construct and the promotional footer wastes tokens.

Suggestions

Add validation checkpoints to the audit workflow: verify row counts / handle pagination for large accounts, check for empty API results before computing distributions, and cross-check totals across the campaign, ad group, and keyword pulls.

Move the Reference Data tables (Quality Score impact, Ad Group Health Scorecard) and the full example audit report into a references/ file linked from SKILL.md, keeping the main file to the workflows and key thresholds.

Fix the invalid GAQL subquery in the 'no enabled ads' query (GAQL does not support NOT IN with a nested SELECT) — e.g., pull ad_group_ad joins and diff the ad group IDs client-side instead.

DimensionReasoningScore

Conciseness

The core content (GAQL queries, threshold tables, severity rules) is dense with no re-explanation of concepts Claude already knows, but the trailing "About this skill" section (~10 lines of promotional Synter links with UTM parameters) is pure padding. This matches anchor 4 (efficient with minor trimmable instances) rather than 3, since the fluff is one contiguous off-topic block rather than scattered over-explanation.

4 / 5

Actionability

Six ready-to-run GAQL queries plus quantified thresholds ("cannibalization_rate > 15%: SEVERITY = HIGH") and decision tables provide mostly executable guidance, matching anchor 4. It is not anchor 5 because one query ("Find ad groups with no enabled ads") uses `ad_group.id NOT IN (SELECT ...)`, which GAQL does not support since subqueries are invalid.

4 / 5

Workflow Clarity

Workflow 1 has a clear Step 1-4 pull sequence and each analysis includes explicit severity classification logic, but checkpoints are missing or implicit: no validation of pulled data, no pagination/row-count handling for large accounts, and no empty-result or API-error feedback loops for the batch queries. This matches anchor 3 (sequence present, validation gaps) rather than 4, since the verification steps are entirely absent.

3 / 5

Progressive Disclosure

No bundle files exist and all ~340 lines are monolithic in SKILL.md. Sections are well-organized with clear headers (Capabilities, Workflows 1-6, Reference Data, Examples), but reference data tables (Quality Score impact, Ad Group Health Scorecard) and the full mock audit report are inline content that belongs in separate reference files, matching anchor 3. It is not anchor 4 because nothing is split out and the file exceeds overview size.

3 / 5

Total

14

/

20

Passed

Description

83%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 that clearly and explicitly states what the skill does and when to use it, with natural trigger phrases and third-person voice. Minor improvements possible: add common synonyms (e.g., "PPC audit", "paid search") and mention one or two of the body's other capabilities (RSA coverage, empty ad groups) for fuller coverage.

DimensionReasoningScore

Specificity

"Audits Google Ads account structure including ad group strategy, keyword duplication, match type distribution, and naming conventions" names the domain plus four specific audit areas, matching anchor 4 (several specific actions, minor gaps). It falls short of anchor 5 because a single verb governs a topic list and body-covered capabilities (RSA coverage, empty ad groups, quality score) are omitted.

4 / 5

Completeness

The description explicitly answers both "what" (audits Google Ads account structure incl. four concrete areas) and "when" ("Use when auditing campaigns, reviewing account structure, finding duplicate keywords, or checking naming conventions") with concrete trigger phrases, matching anchor 5. Anchor 4 does not apply since the "when" clause is already explicit and specific.

5 / 5

Trigger Term Quality

"Use when auditing campaigns, reviewing account structure, finding duplicate keywords, or checking naming conventions" provides natural phrases users would say, matching anchor 4. It is not anchor 5 because common variations like "PPC audit", "paid search", or "account review" are missing.

4 / 5

Distinctiveness Conflict Risk

"Google Ads account structure" plus audit-specific triggers establishes a clear niche, but "auditing campaigns" and "reviewing account structure" are broad enough to overlap with a general Google Ads performance-audit skill, matching anchor 4. It is not anchor 5 because those generic phrases carry minor conflict risk.

4 / 5

Total

17

/

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

Synter-Media-AI/free-skills

Path

skills/campaign-structure-auditor/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.