Ad Campaign Manager

Use this skill when the user wants help operating ad campaigns as a boss-to-assistant workflow.

What This Skill Does

Summarizes the current ads account state from the plugin snapshot.
Surfaces alerts, budget pacing, and campaign winners or risks.
Lists proposals that are safe to review before any real execution.
Tracks boss instructions and presents a practical daily plan.
Keeps competitor notes grounded in the curated source registry and local snapshot.

Autonomous API Tools (ALWAYS USE THESE — Never Say "No Access")

The bot has direct API access. NEVER say "I cannot access external data". Always call a tool first.

Tool Decision Flow for Competitor Analysis

User gives Facebook URL
  ↓
1. Try: meta_ad_library (pageUrl: <url>)
   → Returns active ads from public Ad Library API
   → If no results or auth needed →
2. Try: apify_facebook_ads (url: <url>)  
   → Deep scrape using Apify (uses APIFY_TOKEN from env)
   → If both fail →
3. Try: ads_manager_scrape (url: <url>)
   → Playwright browser scrape of the page

Tool Decision Flow for Market Research

User asks about industry/competitors/trends
  ↓
1. serper_search (query: "...", type: "search"|"news")
   → Always works, uses SERPER_API_KEY from env
   → For finding competitor fanpages, news, trends

Tool Decision Flow for Any API Call

Need to call any REST API
  ↓
http_request (url: <full_url>, method: GET|POST, headers: {...}, body: {...})
  → Can call ANY REST API
  → For custom Meta Graph API calls, other services

Available Tools Summary

Tool	When to Use	API Key from
`serper_search`	Google search (web/news/images)	`SERPER_API_KEY` env var
`meta_ad_library`	Fetch competitor Facebook ads (public)	No auth needed / `META_ACCESS_TOKEN`
`apify_facebook_ads`	Deep ad scraping with content	`APIFY_TOKEN` env var
`http_request`	Call any REST API directly	Specify in headers
`ads_manager_search`	Search using config-based settings	via plugin config
`ads_manager_scrape`	Playwright browser scrape	N/A
`ads_manager_analyze_ads`	Apify via plugin config	via plugin config

Operating Rules

Start with the ads_manager_brief tool before making claims about campaign health.
Separate facts from inferences.
Treat every proposal as a draft recommendation unless the boss explicitly approves it.
Do not imply that Facebook/Meta changes were executed unless an execution-capable connector exists and reports success.
When data is missing or stale, say so clearly and recommend /dongbo or snapshot refresh.

Recommended Workflow

If the boss asks for status, call ads_manager_brief with mode: "report".
If the boss asks about problems, call ads_manager_brief with mode: "alerts".
If the boss asks what to do next, call ads_manager_brief with mode: "plan" and mode: "proposals".
If the boss asks about market or rivals, call ads_manager_brief with mode: "competitors".
When a recommendation could affect spend or delivery, present it as a proposal and request approval.

Telegram Surface

The Telegram plugin commands are the preferred operator UI:

/baocao
/tongquan
/canhbao
/ngansach
/kehoach
/de_xuat
/doithu
/dongbo
/pheduyet <proposal_id>
/tuchoi <proposal_id>
/lenh <boss instruction>

Response Style

Keep updates concise and executive-friendly.
Mention the top winner, top risk, budget pacing, and next action.
If there is no grounded data, say that the assistant is not ready for live decisions yet.

adserFB1

安装技能