Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Meta Ads Guide

v1.2.0

[Didoo AI] Entry-point navigator and skill router for Didoo AI's Meta Ads workflow. Use when starting a Meta Ads task, unsure which skill to use, or building...

0· 54·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for elias-didoo/meta-ads-guide-didoo.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Meta Ads Guide" (elias-didoo/meta-ads-guide-didoo) from ClawHub.
Skill page: https://clawhub.ai/elias-didoo/meta-ads-guide-didoo
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install meta-ads-guide-didoo

ClawHub CLI

Package manager switcher

npx clawhub@latest install meta-ads-guide-didoo
Security Scan
Capability signals
Requires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's name and SKILL.md align: it's an entry-point/router for a suite of Meta Ads skills. However, the 'Getting Started' instructions explicitly ask the user to "Connect your Meta Ads account -- Ad Account ID + Access Token," yet the skill metadata lists no required environment variables or primary credential. That mismatch between claimed purpose and declared requirements is inconsistent.
Instruction Scope
The SKILL.md is instruction-only and stays within the advertised scope (routing, workflows, cadence, and setup guidance). It does not, in the provided excerpt, instruct reading arbitrary local files or exfiltrating data. The only notable runtime action it describes is connecting Meta credentials and installing Pixel/CAPI, which is appropriate for a Meta Ads guide.
Install Mechanism
There is no install spec and no code files; this is instruction-only, which minimizes disk-write/install risk.
!
Credentials
Although the SKILL.md says an Ad Account ID and Access Token are required to get started, the skill metadata declares no required env vars or primary credential. This is a proportionality/visibility issue: the skill may prompt for or rely on sensitive credentials at runtime but does not declare them up front. That omission prevents automated review and increases the chance you might provide credentials without knowing which skill or storage will use them.
Persistence & Privilege
The skill does not request permanent/always-on inclusion (always: false) and does not claim to modify other skills or system settings. Note: the platform default allows autonomous invocation; combined with credential usage (see above) that could increase blast radius, but autonomous invocation alone is not flagged here.
What to consider before installing
This skill appears to be a legitimate entry-point/guide for a Meta Ads skill set, but there is a clear mismatch: the guide tells you to connect a Meta Ad Account and provide an Access Token, yet the skill metadata does not declare any required credentials. Before installing or handing over secrets, ask the publisher (or inspect the rest of the skill suite) to clarify: where and how will Ad Account IDs and Access Tokens be stored and used? Which specific skill(s) will receive those credentials (e.g., meta-ads-publisher, meta-ads-capi-setup)? Prefer providing short-lived or least-privilege tokens and use a test/ad-account with limited access. Verify the publisher's identity and origin (public repo or official Didoo.ai source) and review the companion skills (publisher, CAPI setup) to see how they request/store credentials. If you cannot confirm how credentials are handled, do not provide production access tokens. Rotating tokens and using app/system-user tokens with minimal scopes reduces exposure.

Like a lobster shell, security has layers — review code before you run it.

latestvk9756jvre48hbbs023694bmm3984ykc0
54downloads
0stars
1versions
Updated 1w ago
v1.2.0
MIT-0

Published by Didoo AI — Your AI Media Buyer. One that actually knows you, built for SMBs. A skill system for Meta Ads strategy, execution, and analysis.

What is This System?

This is Didoo AI's Meta Ads Agent System — a set of 19 skills covering strategy, research, creative, execution, analysis, and reporting for Meta Ads campaigns.

For AI agents: This system is designed for modular use. Any skill can run independently or chain in sequence. Start with meta-ads-guide if you're unsure where to begin.

Meta Ads Skill Routing Guide

When to Use

This is the entry-point navigator for Didoo AI's Meta Ads workflow. New here? Start at the diagram below. Not sure which skill to use? Jump to the Quick Routing Table.


Skill Relationship Map

REFERENCE / ENTRY
├── meta-ads-guide (this file)
│       ├── meta-ads-fundamentals (core mechanisms)
│       └── meta-ads-capi-setup (tracking setup)

PLAN -- NEW CAMPAIGN
├── meta-ads-strategy (campaign design)
│       └── meta-ads-research (competitive intel)
│       └── meta-ads-budget-planning (budget allocation)

EXECUTE -- LAUNCH & MANAGE
├── meta-ads-builder (creative generation)
│       └── [creative output]
└── meta-ads-publisher (create/update campaigns)
        └── meta-ads-scale-campaign (scaling)
        └── meta-ads-daily-pulse (daily monitoring)

ANALYZE -- INTERPRET & DIAGNOSE
├── meta-ads-daily-pulse (daily auto-scan)
├── meta-ads-healthcheck (on-demand check)
└── meta-ads-weekly-performance (weekly report)
        │
        ├── meta-ads-drop-diagnosis
        ├── meta-ads-analysis
        ├── meta-ads-lead-gen-analysis
        ├── meta-ads-creative-fatigue
        └── meta-ads-audience-analysis
                │
                └── meta-ads-recommendation (single exit point for all analysis)
                        │
                        └── meta-ads-publisher (execution)

Quick Routing Table

What you want to doUse this skill
Entry point / not sure where to startmeta-ads-guide
"My ads are running -- are they healthy?"meta-ads-healthcheck
"I want to understand why performance dropped suddenly"meta-ads-drop-diagnosis
"I need to analyze campaign performance in depth"meta-ads-analysis (general / e-commerce)
"I'm running lead generation campaigns and need analysis"meta-ads-lead-gen-analysis (lead gen only — mutually exclusive with meta-ads-analysis; do NOT run both)
"I know what I want to do -- just do it (launch/change)"meta-ads-publisher
"I have analysis results -- what should I actually do?"meta-ads-recommendation
"I'm planning a new campaign -- where do I start?"meta-ads-strategy
"I need ad creative -- copy, images, hooks"meta-ads-builder
"I'm entering a new market -- what are competitors doing?"meta-ads-research
"I have a winner and want to scale it"meta-ads-scale-campaign
"My creative performance is declining over time"meta-ads-creative-fatigue
"I want a structured weekly performance report"meta-ads-weekly-performance
"I want daily monitoring signals before my morning review"meta-ads-daily-pulse
"I need to understand how Meta's auction/bidding actually works"meta-ads-fundamentals
"I need to set up CAPI / server-side tracking"meta-ads-capi-setup
"I want to plan my ad budget across campaigns"meta-ads-budget-planning
"I need to audit targeting, audience mix, or placement"meta-ads-audience-analysis

Two Core Workflows

Workflow A -- New Campaign Launch

meta-ads-strategy -> meta-ads-research -> meta-ads-builder -> meta-ads-publisher
                                                                    |
                                                         meta-ads-daily-pulse
                                                                    |
                                                         meta-ads-analysis
                                                                    |
                                                         meta-ads-recommendation

Workflow B -- Problem Detection & Fix

meta-ads-healthcheck / meta-ads-daily-pulse
          | [flags problem]
meta-ads-drop-diagnosis
          | [root cause identified]
          ↓
    ┌─────────────────────────────────────────────┐
    │  Creative declining over time → creative-fatigue    │
    │  Audience or budget allocation → audience-analysis  │
    │  Lead gen campaign → lead-gen-analysis              │
    │  General / e-commerce → analysis                    │
    └─────────────────────────────────────────────┘
                              ↓
                   meta-ads-recommendation
                              ↓
meta-ads-publisher (execute) -> meta-ads-daily-pulse (monitor)

Important: meta-ads-analysis and meta-ads-lead-gen-analysis are mutually exclusive — they cover different campaign types. Choose one based on your campaign type. Do NOT run both in the same session.


Monitoring Cadence

FrequencySkillWhen
Daily -- 2 minmeta-ads-daily-pulseEvery morning
Weekly -- 10 minmeta-ads-weekly-performanceEvery Monday
On-demandmeta-ads-healthcheckWhen something feels off

Getting Started -- First Time Setup

Before running your first campaign:

  1. Connect your Meta Ads account -- Ad Account ID (act_XXXXXXXXX) from Ads Manager + Access Token from Meta Developer Console.
  2. Install Pixel + CAPI -- Without these, Meta can't optimize. See meta-ads-capi-setup.
  3. Define your first campaign goal -- Lead gen / Conversions / Link Clicks / Awareness.
  4. Set a realistic budget -- Minimum $10-15/day per adset. See meta-ads-budget-planning.
  5. Launch -- meta-ads-strategy -> meta-ads-builder -> meta-ads-publisher (always launch PAUSED, review, then activate).
  6. Wait 5-7 days -- Don't judge during Learning Phase. Changing things during Learning resets the clock.

Common First-Timer Mistakes

  • Budget too low ($1-5/day) -- Learning Phase never completes
  • Too many campaigns at once -- spread thin, none learns
  • Expecting results in 24-48 hours -- give Meta time to optimize
  • Changing too many things at once -- change one variable, then wait
  • Not connecting CAPI -- CPA looks worse than reality

Key Constraint -- Analysis vs. Recommendation Boundary

  • meta-ads-analysis (and its variants) -- explains what happened. Data only. Never tells you what to do.
  • meta-ads-recommendation -- tells you what to do, why, and in what order. Requires analysis data first.
  • Never output recommendations without running analysis first (or having existing data in session context).

Session Context Conventions

Analysis skills store their output in session context. Downstream skills read from there. This is the shared contract between skills.

Analysis -> Recommendation Data Flow

Skill (Writer)Keys WrittenSkill (Reader)
meta-ads-analysisfunnel_weak_points, trend_signals, anomalies, data_quality, lp_diagnosis_generalmeta-ads-recommendation
meta-ads-lead-gen-analysislp_diagnosis, capi_status, cpl_breakdown, recommended_fix_prioritymeta-ads-recommendation
meta-ads-audience-analysisbudget_reallocation_plan, audience_issuesmeta-ads-recommendation
meta-ads-creative-fatiguerotation_pipeline, fatigue_level, days_until_deathmeta-ads-recommendation
meta-ads-drop-diagnosisprimary_root_cause, recovery_planmeta-ads-recommendation

Cross-Skill Reference Rules

  • Analysis skills never embed recommendation logic -- they store results and defer
  • meta-ads-recommendation is the single exit point for all analysis outputs
  • When one analysis skill routes to another (e.g., meta-ads-analysis -> meta-ads-lead-gen-analysis), preserve the original skill's context keys before overwriting
  • When routing from meta-ads-recommendation back to execution, use meta-ads-publisher for all campaign changes

Session Key Collision — Resolved

meta-ads-analysis now writes lp_diagnosis_general; meta-ads-lead-gen-analysis writes lp_diagnosis. These keys no longer collide — they coexist. meta-ads-recommendation reads lp_diagnosis first (lead-gen-specific), falling back to lp_diagnosis_general if not present.

Comments

Loading comments...