CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-ads

Manage Meta Ads (Facebook + Instagram) — performance, ROAS, CPM, frequency, audience overlap, learning phase, creative fatigue, budgets, ad sets, campaigns, ads. Use for any mention of Meta Ads, Facebook Ads, Instagram Ads, ROAS, CPM, ad spend, or campaign settings on Meta.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, lean analytical skill that delegates detail to one-level-deep references and provides highly actionable thresholds, formulas, and tool names. The only notable gap is the absence of an explicit linear pipeline with error-recovery feedback loops, though validation checkpoints for mutations are present.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude knows paid-social basics (no definitions of ROAS/ad sets), and every section earns its place; the inline account-baseline JSON schema and tool-surface listing are slightly long but justified, keeping it just below a 5.

4 / 5

Actionability

Concrete decision rules with numeric thresholds ("frequency > 3.0 with rising CPM", "50-events-in-7-days", ">30% anomaly"), an explicit update formula (`rolling30d = (0.7 × previous_rolling30d) + (0.3 × recent7d × (30/7))`), and exact tool names (`runScript`, `ads.graphParallel`, `pauseAdSet`) make the instruction-only guidance highly executable.

5 / 5

Workflow Clarity

Operating principles #1 ("Confirm before writing") and #4 ("Recommend, then act — wait for approval before mutating") provide explicit validation checkpoints for mutation operations, and the reference-framework table plus conditional handoffs sequence the workflow; it lacks a single strict numbered pipeline with error-recovery loops, so it stops at 4.

4 / 5

Progressive Disclosure

A clear "Reference framework — when to read what" table routes user intent to one-level-deep, real bundle files (analysis-heuristics.md, creative-fatigue.md, learning-phase.md, audience-strategy.md, industry-benchmarks.md, campaign-structure-guide.md), keeping the SKILL.md an overview with well-signaled, easy navigation.

5 / 5

Total

18

/

20

Passed

Description

95%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 crisply states what the skill manages and when to invoke it, with comprehensive natural trigger terms and minimal conflict risk. The only weakness is reliance on a single action verb rather than enumerating several distinct concrete operations.

DimensionReasoningScore

Specificity

"Manage Meta Ads (Facebook + Instagram) — performance, ROAS, CPM, frequency, audience overlap, learning phase, creative fatigue, budgets, ad sets, campaigns, ads" enumerates many specific capability areas, but relies on a single action verb ("Manage") rather than multiple distinct concrete actions, so it sits just below a 5.

4 / 5

Completeness

It explicitly answers both what ("Manage Meta Ads ... budgets, ad sets, campaigns, ads") and when ("Use for any mention of Meta Ads, Facebook Ads, Instagram Ads, ROAS, CPM, ad spend...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use for any mention of Meta Ads, Facebook Ads, Instagram Ads, ROAS, CPM, ad spend, or campaign settings on Meta" covers natural synonyms (Meta/Facebook/Instagram) plus concrete metric keywords a user would actually say, giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

The Meta Ads niche with branded platform terms (Meta/Facebook/Instagram Ads, ROAS, CPM, ABO/CBO) is clearly distinct and unlikely to trigger for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nowork-studio/NotFair
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.