CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

campaign-architect

Use when the user asks to "plan my paid account structure", "pick Search vs PMax", "lay out ad groups / asset groups", or "audit paid-vs-organic cannibalization"; designs campaign-type selection, ad-group/asset-group layout, targeting + match types, negative/exclusion hygiene, and a paid↔organic overlap audit, and scores the ROAS A (Audience) dimension + structure. Not for computing the final RQS — use ad-account-auditor; not for budget split — use budget-optimizer; not for organic site architecture — use site-structure-optimizer. 付费广告账户结构/广告系列规划/否定关键词

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured instruction-only skill body: lean overview, tightly specified eight-step workflow with explicit validation and coverage gates, and clearly annotated one-level-deep references. The main weaknesses are repeated restatement of the delegation boundary and reliance on out-of-bundle files for the output templates and benchmarks.

DimensionReasoningScore

Conciseness

The body is dense and almost every line carries domain-specific rules Claude would not infer (typed A-weights of 0.15/0.30/0.10, one intent theme per group, no overlapping keyword sets), so it largely assumes Claude's competence. It is not a 5 because the RQS/budget delegation boundary is stated redundantly — in the intro paragraph, the Skill Contract, the Scope guard, and step 8 — and the Data Sources section spends tokens explaining transparency libraries that could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: step 6 specifies exact provenance fields ('account/campaign/ad-group refs plus source, observed time, window, attribution window, currency, timezone, and evidence label') and step 5 gives specific derivation rules for negatives. It stops short of a 5 because the actual output shape (handoff summary, save template) is delegated to external files rather than shown inline, leaving minor gaps for the common case.

4 / 5

Workflow Clarity

The eight numbered steps are clearly sequenced (profile → campaign type → groups → targeting → negatives → cannibalization audit → scoring → delegation) with explicit validation gates: 'If the placements report is absent, mark qualified ROAS-A1 Unknown with its gap reason' and 'Any applicable Unknown makes the run NEEDS_INPUT/UNDECIDED/NOT_SCORED'. A 'Done when' checklist and error paths for conflicting/missing exports (preserve conflicts, mark Unknown/NEEDS_INPUT) complete the feedback-loop pattern of the anchor-5 example.

5 / 5

Progressive Disclosure

The body is a lean ~70-line overview with a dedicated Reference Materials section where each link is annotated with its purpose (roas-benchmark.md for A-dimension items, CONNECTORS.md for export recipes, SECURITY.md for untrusted input), keeping references one level deep and well signaled. It is not a 5 because the referenced files (e.g. ../../../references/roas-benchmark.md, ../../activate/ad-account-auditor/SKILL.md) do not exist within this skill's bundle — no references/, scripts/, or assets/ directories are present — and several paths traverse into other skills' directories, so navigation cannot be fully verified and is mildly fragile.

4 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that pairs a concrete capability list with explicit quoted trigger phrases and crisp not-for boundaries against sibling skills. The only weakness is slightly incomplete English synonym coverage for its trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'designs campaign-type selection, ad-group/asset-group layout, targeting + match types, negative/exclusion hygiene, and a paid↔organic overlap audit, and scores the ROAS A (Audience) dimension' — giving comprehensive coverage of the skill's capabilities. It clearly matches the anchor for multiple specific actions with comprehensive coverage rather than the anchor-4 example, which implies minor gaps.

5 / 5

Completeness

It explicitly answers both 'what' (designs campaign types, group layout, targeting/match types, negative hygiene, overlap audit, scores ROAS A) and 'when' (a leading 'Use when the user asks to...' clause with concrete quoted trigger phrases). This directly matches the anchor-5 example structure with concrete triggers; it is above the anchor-4 case where 'when' could be more explicit.

5 / 5

Trigger Term Quality

It quotes natural user phrasings ('plan my paid account structure', 'pick Search vs PMax', 'lay out ad groups / asset groups', 'audit paid-vs-organic cannibalization') plus bilingual keywords (付费广告账户结构/否定关键词), which is good keyword coverage. It falls short of the comprehensive-synonyms anchor (5) because common variations like 'campaign structure', 'Performance Max', or 'negative keywords' in English are absent.

4 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (paid-ads account structure design) and explicitly disambiguates adjacent skills: 'Not for computing the final RQS — use ad-account-auditor; not for budget split — use budget-optimizer; not for organic site architecture — use site-structure-optimizer.' This minimal-conflict profile matches the anchor-5 example; without these carve-outs it would risk overlap with the auditor/budget skills.

5 / 5

Total

19

/

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: 17 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/research/campaign-architect/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.