CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-ads-operator

Operate Meta (Facebook/Instagram) Ads via Synter MCP — pull performance, create/draft ads, and stage budget or creative changes with human approve ≠ activate. Use when diagnosing Learning Phase, creative fatigue, Advantage+, or Meta campaign ops through Synter.

Quality

77%

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/meta-ads-operator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 is a compact, well-sequenced operator playbook with concrete MCP tool mappings and a sound human-approval gate before enabling changes. Its weaknesses are padded promotional footer content, missing execution details (parameters, thresholds, outputs) in the operator loop, and the absence of error-recovery loops.

Suggestions

Cut the 'About this skill' footer and the duplicated 'Solo / Scale / Crucible Managed (never a Free cloud tier)' note; one link to synter-mcp-setup is sufficient context.

Add a short example invocation for pull_meta_ads_performance and meta_ads_create_ad (key parameters and expected output shape) so the operator loop is executable, not just directional.

Define concrete flagging criteria for the Read/Creative steps, e.g., 'flag CPA spikes' as a CPA increase above X% week-over-week and 'check fatigue' as frequency above N.

DimensionReasoningScore

Conciseness

Core sections are lean, but the 'About this skill' footer is promotional padding ('Skills files are free to clone; hosted Synter is never a Free cloud tier') and the 'Solo / Scale / Crucible Managed (never a Free cloud tier)' hosting note is repeated twice, matching 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not 2 because no concepts are over-explained.

3 / 5

Actionability

Concrete tool names throughout (pull_meta_ads_performance, meta_ads_create_ad, get_pixel_health) and a job-to-tool table give real guidance, but key execution details are missing: no invocation parameters, no output handling, and vague criteria like 'flag CPA spikes' without thresholds — 'concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The operator loop (Read → Creative → Draft → Measurement → Gate) is clearly sequenced with explicit checkpoints — 'leave paused until human approve', 'campaign-preflight + launch-gates before enable', 'confirm Pixel + CAPI' — so the destructive-operation cap does not apply. Falls short of 5 because no error-recovery or re-check feedback loops are described.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is short with clear sections (Prerequisites, Core MCP tools, Operator loop, Related skills), with sibling-skill references clearly signaled. Kept at 4 rather than the simple-skill 5 because the marketing footer is misplaced content that clutters otherwise good organization.

4 / 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: third-person, concrete about capabilities, and anchored by an explicit 'Use when' clause with natural Meta-ops trigger terms. The only blemishes are the grammatically odd 'human approve ≠ activate' phrasing and slight trigger overlap with sibling diagnostic skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'pull performance, create/draft ads, and stage budget or creative changes' — matching the anchor for several specific actions with minor gaps (pause and pixel-health operations from the body are absent, and 'with human approve ≠ activate' is garbled rather than a clear action).

4 / 5

Completeness

Explicitly answers both: the 'what' is concrete (pull performance, create/draft ads, stage budget/creative changes) and the 'when' is an explicit 'Use when' clause with concrete trigger phrases, matching the top anchor. Not 4 because the when-clause is specific, not merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'diagnosing Learning Phase, creative fatigue, Advantage+, or Meta campaign ops' are phrases a Meta ads manager would actually say, though a few common variations (CPA, scaling, Facebook ads manager, ad account) are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'via Synter MCP' / 'through Synter' with Meta-specific triggers, giving a clear niche; minor overlap risk remains with closely related sibling skills — 'creative fatigue' is also the trigger domain of ad-creative-fatigue-detector.

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/meta-ads-operator/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.