CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ads-plan

Create a professional paid-advertising strategy covering objectives, economics, platform selection, campaign architecture, audiences, budget, creative, measurement, experiments, governance, rollout, and reporting. Use for ad plan, media plan, PPC strategy, paid-social strategy, campaign architecture, advertising roadmap, or channel planning.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-sequenced planning workflow that is unusually lean and specific for an instruction-only skill. Its main weaknesses are navigational: the bundled assets/ industry templates are never pointed to by path, and the required canonical JSON output format is undefined.

Suggestions

Point step 1 at the bundled templates by path (e.g., "load the matching vertical template from `assets/<vertical>.md`") and name the available verticals so the 12 files in assets/ are discoverable from SKILL.md.

Specify or reference the schema for the required "Return canonical JSON" output (e.g., a path to a schema file or an inline minimal example), since the format is currently undefined.

Add an explicit validation checkpoint before returning the plan (e.g., verify every action has owner/timing/rollback and every cold-start dimension is labeled) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is a lean 8-step imperative workflow with zero padding: no concept explanations, no filler, and every line instructs (e.g., "Assign every action an owner, timing, dependency, guardrail, evidence, success measure, and rollback or exit condition"). It fully assumes Claude's competence, matching anchor 5.

5 / 5

Actionability

Mostly concrete instruction guidance: named contract files ("skills/ads-meta/SKILL.md", "ads/references/additional-platforms.md"), enumerated deliverables ("owner, timing, dependency, guardrail, evidence, success measure"), and a defined output ("Return canonical JSON"). Gaps keep it below anchor 5: the "relevant industry template" in step 1 has no path to the bundle's assets/ files, and the canonical JSON format is never specified or referenced.

4 / 5

Workflow Clarity

The 8 steps are clearly sequenced (inputs → definitions → channel evaluation → cold-start gate → specification → phasing → assignment → output) with an explicit conditional branch in step 4 ("When any dimension is cold or `unknown`... do not apply mature-account benchmarks") and rollback/exit conditions in step 7. There is no explicit output-validation step before returning, so it sits at anchor 4 rather than anchor 5's validate-and-retry feedback loop; the advisory-only closing note means the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

Scored against the actual bundle: 12 industry templates exist under assets/ but the body only says "relevant industry template as optional input" with no path or listing, leaving the bundle's main reference material undiscoverable from SKILL.md. The two external references are clearly signaled with full paths, so this matches anchor 3 (references present but not clearly signaled) rather than anchor 4's mostly-clear navigation.

3 / 5

Total

16

/

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: concrete, third-person, with a comprehensive enumerated scope and an explicit "Use for..." trigger clause covering natural synonyms. Distinctiveness is good, with only minor overlap risk from the broadest trigger terms.

DimensionReasoningScore

Specificity

"Create a professional paid-advertising strategy covering objectives, economics, platform selection, campaign architecture, audiences, budget, creative, measurement, experiments, governance, rollout, and reporting" enumerates twelve concrete coverage areas in third person. It is a single concrete action rather than multiple distinct actions (anchor 5), but far more specific than anchor 3's 1-2 actions.

4 / 5

Completeness

The description explicitly answers both "what" (creates a paid-advertising strategy covering twelve enumerated areas) and "when" ("Use for ad plan, media plan, PPC strategy...") with concrete trigger phrases, exactly matching the anchor 5 example pattern. It clearly exceeds anchor 4, where the when-clause is present but less specific.

5 / 5

Trigger Term Quality

"Use for ad plan, media plan, PPC strategy, paid-social strategy, campaign architecture, advertising roadmap, or channel planning" lists natural phrases users would say. A few common variations ("ad strategy", "paid search", "advertising plan", "media buying") are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"PPC strategy", "paid-social strategy", "media plan" carve a clear paid-media niche, but "campaign architecture" and "channel planning" are broad enough to overlap with organic marketing or general strategy skills. Mostly distinct with minor overlap risk against closely related skills, matching anchor 4.

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

AgriciDaniel/claude-ads

Path

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