meta_ad
v1.0.0This skill automates the creation of Meta (Facebook/Instagram) ads using the Marketing API. It handles campaign setup, audience targeting, media upload, and...
⭐ 0· 88·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Meta ads automation) align with included scripts (campaign/adset/ad/media upload/one‑shot flow). Required credentials (access token, ad account ID) are used by the code and documented in SKILL.md; nothing unrelated (e.g., AWS keys) is requested.
Instruction Scope
SKILL.md instructs running the bundled Python scripts and to run an interactive config step; the scripts only read local files (images/config), write a local config, and call the Meta Graph API endpoints documented in references. Note: the config is stored in plaintext under ~/.workbuddy/meta_ads_config.json which contains the access token, ad account ID, and optional app secret (sensitive).
Install Mechanism
There is no install spec (instruction-only install), which is low risk. However, the skill includes Python scripts that require the 'requests' library but the registry metadata does not declare dependencies—this may cause runtime errors if requests is absent. No external install URLs or archives are used.
Credentials
No environment variables are required (the code uses a local config file). The credential access requested (Meta Access Token, Ad Account ID, optional App ID/Secret) is proportionate to the task. Warning: credentials are persisted to a local file in the user's home directory in cleartext; protect or remove that file if needed.
Persistence & Privilege
always is false and the skill does not attempt to modify other skills or system-wide settings. It persists its own config under ~/.workbuddy/meta_ads_config.json (self-contained).
Assessment
This skill appears to do what it says, but before installing use a safe workflow: (1) review the bundled scripts (you already have them) and run them in a sandbox or virtualenv; (2) ensure Python 'requests' is installed; (3) create and use a token with minimal scopes and, if possible, a test ad account to avoid accidental spend; (4) be aware the Access Token and optional App Secret are saved to ~/.workbuddy/meta_ads_config.json in plaintext — delete or securely store that file when finished; (5) verify network calls (they go to graph.facebook.com) and confirm you trust the skill source (no homepage/author details provided). If you need higher assurance, request provenance (repository or author info) or run the scripts in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97bjbhjanbjnzwnaq4bb1bryx835czm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.