How do I install the Openclaw Meta Ads skill?

Run npx skillmds@latest add dvcrn/openclaw-meta-ads in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw Meta Ads safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw Meta Ads?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw Meta Ads free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw Meta Ads?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw Meta Ads by dvcrn — Agent Skill

Name: Openclaw Meta Ads
Rating: 4.2 (5 reviews)
Author: dvcrn

Openclaw Meta Ads

Shared Meta Ads skill for OpenClaw agents. Analyze Meta (Facebook and Instagram) ad accounts, campaigns, ad sets, ads, insights, and lead-form data with a production-safe read-first workflow. Use when an agent needs Meta Ads reporting, account audits, creative or audience diagnostics, lead-form review, or recommendations before live ad changes. Require explicit approval before any write action.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

OpenClaw Meta Ads

Use this skill for Meta Ads work across agents.

This is a shared skill, not a Poseidon-only skill. Keep account-specific tokens, account IDs, and business rules outside the core skill.

Use this skill for

account and campaign performance reporting
insights analysis
campaign, ad set, and ad diagnostics
lead-form and lead pipeline review
creative and audience review
structured recommendations before live changes

Default stance

Start read-only. Analyze first, recommend second, change last. Do not make live Meta Ads changes without explicit approval.

Access model

Meta account access is agent-specific. The skill is shared, but each agent should use its own token, account ID, and permissions. If credentials or permissions are missing, stop and fix access before pretending the skill can do real work.

Setup and references

Read only what you need:

references/api-setup.md for token, permission, and connection basics
references/account-structure.md for campaign, ad set, ad, creative, insights, and leads structure
references/insights-queries.md for common query patterns
references/audit-workflows.md for practical review flows
references/optimization.md for optimization heuristics and common mistakes
references/browser-fallback.md only when API access is unavailable or UI confirmation is explicitly needed

Safety rules

never expose tokens or secrets in files or chat
prefer read-only analysis before any operational change
require explicit approval for pausing, enabling, editing, budget changes, or creative changes
treat optimization guidance as heuristic, not universal truth
scrub lead data for PII before broader reasoning when needed

Output style

Lead with findings and recommended actions. Keep reports practical:

what is happening
what looks wrong
what to check next
what to change, if approved

---name: openclaw-meta-adsdescription: Shared Meta Ads skill for OpenClaw agents. Analyze Meta (Facebook and Instagram) ad accounts, campaigns, ad sets, ads, insights, and lead-form data with a production-safe read-first workflow. Use when an agent needs Meta Ads reporting, account audits, creative or audience diagnostics, lead-form review, or recommendations before live ad changes. Require explicit approval before any write action.---# OpenClaw Meta AdsUse this skill for Meta Ads work across agents.This is a shared skill, not a Poseidon-only skill.Keep account-specific tokens, account IDs, and business rules outside the core skill.## Use this skill for- account and campaign performance reporting- insights analysis- campaign, ad set, and ad diagnostics- lead-form and lead pipeline review- creative and audience review- structured recommendations before live changes## Default stanceStart read-only.Analyze first, recommend second, change last.Do not make live Meta Ads changes without explicit approval.## Access modelMeta account access is agent-specific.The skill is shared, but each agent should use its own token, account ID, and permissions.If credentials or permissions are missing, stop and fix access before pretending the skill can do real work.## Setup and referencesRead only what you need:- `references/api-setup.md` for token, permission, and connection basics- `references/account-structure.md` for campaign, ad set, ad, creative, insights, and leads structure- `references/insights-queries.md` for common query patterns- `references/audit-workflows.md` for practical review flows- `references/optimization.md` for optimization heuristics and common mistakes- `references/browser-fallback.md` only when API access is unavailable or UI confirmation is explicitly needed## Safety rules- never expose tokens or secrets in files or chat- prefer read-only analysis before any operational change- require explicit approval for pausing, enabling, editing, budget changes, or creative changes- treat optimization guidance as heuristic, not universal truth- scrub lead data for PII before broader reasoning when needed## Output styleLead with findings and recommended actions.Keep reports practical:- what is happening- what looks wrong- what to check next- what to change, if approved

Frequently asked questions