Name: facebook-ads
Rating: 58.4 (1 reviews)
Author: membranedev

facebook-ads

Meta (Facebook) Ads integration. Manage Campaigns, Audiences, Pixels. Use when the user wants to interact with Meta (Facebook) Ads data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/facebook-ads/SKILL.md

Quality

Content

71%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 highly actionable with copy-paste-ready CLI commands and a clear connection-flow walkthrough, and is reasonably well-structured. Its weaknesses are modest over-explanation in spots and the absence of validation/verification steps around destructive and batch ad operations.

Suggestions

Add an explicit validation/verification checkpoint after create/update/delete actions (e.g. re-list or get the campaign to confirm the change took effect) to raise workflow clarity past the destructive/batch cap.

Tighten the overview paragraph and the clientAction state explanations — Claude can infer OAuth/auth-reconnect semantics; keep only the Membrane-specific behavior.

Consider moving the full popular-actions table and proxy flag reference into separate reference files (e.g. ACTIONS.md) to deepen progressive disclosure while keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient with concrete commands and tables, but the overview paragraph and the 'clientAction' state walkthrough over-explain mechanics Claude could infer, and some sections (proxy flag tables, best-practice rationale) could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request with flag tables) covering the common cases with concrete examples and the --json output convention.	5 / 5
Workflow Clarity	A rough connection lifecycle sequence is present with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED), but operations that are destructive or batch in nature (delete/update campaigns) lack explicit validation or verification checkpoints, capping workflow clarity at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with a popular-actions table and CLI subcommands grouped logically; there are no bundle files so it stays self-contained and shallow, though a couple of inline reference blocks (the large actions table, proxy flags) could arguably live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is strong and well-formed: it states concrete capabilities and includes an explicit 'Use when' trigger clause in third-person voice. Its main weakness is limited natural-keyword coverage and a trigger phrase that could name more concrete use cases.

Suggestions

Expand the trigger phrase to concrete user utterances, e.g. 'Use when managing Facebook/Meta ad campaigns, audiences, pixels, or ad performance and reporting'.

Add natural synonyms users say — 'Facebook Ads', 'Meta Ads', 'ad account', 'ad creatives' — to improve trigger-term coverage.

List a few more concrete actions (create/update/delete campaigns, pull insights) to round out capability coverage toward the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (Meta/Facebook Ads) and lists several concrete capabilities — 'Manage Campaigns, Audiences, Pixels' — which are specific, though the action list is brief and not exhaustive, leaving minor coverage gaps relative to a comprehensive enumeration.	4 / 5
Completeness	It has a clear 'what' ('Manage Campaigns, Audiences, Pixels') and an explicit 'when' ('Use when the user wants to interact with Meta (Facebook) Ads data'), satisfying both halves; the 'when' could be more specific with concrete trigger phrases, so it is strong but not maximal.	4 / 5
Trigger Term Quality	It surfaces 'Campaigns, Audiences, Pixels' and the trigger phrase 'Meta (Facebook) Ads data', but omits common natural variations and synonyms (e.g. 'Facebook Ads', 'ad campaigns', 'Meta Ads manager') users would actually say, so keyword coverage is only partial.	3 / 5
Distinctiveness Conflict Risk	The Meta/Facebook Ads niche is clearly distinct and unlikely to collide with unrelated skills; there is minor overlap risk only with a hypothetical general marketing/analytics skill, but its triggers are fairly specific.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/facebook-ads/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.