adserFB4
v1.0.0Expert playbook for Meta Ads campaign optimization decisions. Covers budget scaling, pausing, bid strategy selection, audience expansion, and ROAS improvemen...
⭐ 0· 92·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 and description match the SKILL.md content: all rules, thresholds, and checklists relate to Meta/Meta Ads campaign optimization for the Vietnam market. The skill asks for nothing outside that domain (no binaries, env vars, or config paths).
Instruction Scope
SKILL.md contains only decision rules, thresholds, and checklists. It does not instruct the agent to read system files, credentials, or external endpoints. A few items are phrased broadly (e.g., 'check competitor memory', 'create proposal for boss approval', 'monitor for 3 days') which grant human-like discretion — this is expected for a playbook but could lead an autonomous agent to take broad operational actions if paired with other skills that have execution privileges.
Install Mechanism
No install spec and no code files (instruction-only). Nothing will be written to disk or downloaded during install.
Credentials
The skill requests no environment variables, credentials, or config paths. All thresholds and parameters are self-contained in the document (VND, CPAs, ROAS).
Persistence & Privilege
always is false and the skill does not request persistent system presence or any system-wide configuration changes. Autonomous invocation is allowed by platform default but the skill itself contains no code to act on accounts.
Assessment
This is an instruction-only playbook (no code, no downloads, no credentials) so the direct technical risk is low. Before installing/using it: (1) review and adapt numeric thresholds (VND CPA, ROAS) to your business — these are opinionated defaults; (2) beware combining this playbook with other skills or automations that do have Meta API access or the ability to change ad accounts — the playbook could direct those agents to make real budget/pausing changes; (3) test recommendations in a staging or low-risk account and require human sign-off for large changes (e.g., >20–30% budget moves); (4) verify the truncated sections and any locale-specific seasonality notes to ensure nothing important was omitted. If you want stricter safety, restrict autonomous invocation or require manual approval steps before any account-modifying actions.Like a lobster shell, security has layers — review code before you run it.
latestvk97dzak087f34120zx8vv6ax6n83a8zd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.