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.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "openclaw-meta-ads" with this command: npx skills add sebclawops/openclaw-meta-ads

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

Usercentrics

Usercentrics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Usercentrics data.

Registry SourceRecently Updated
Automation

Session Cost

Analyze OpenClaw session logs to report token usage, costs, and performance metrics grouped by agent and model. Use when the user asks about API spending, to...

Registry SourceRecently Updated
Automation

Agented

Stateful, persistent text editor for LLM agents. Undo tree, marks, annotations, transactions. Backed by SQLite.

Registry SourceRecently Updated
Automation

Agent Memory System v8

Agent 记忆系统 — 6维坐标编码 + RRF双路检索 + sqlite-vec统一存储 + 写入时因果检测 + 多Agent共享 + 记忆蒸馏 + 时间旅行 + 情感编码 + 元认知 + 内在动机 + 叙事自我 + 数字孪生 + 角色模板

Registry SourceRecently Updated