@opendirectory.dev/skills 0.1.52 → 0.1.54

package/skills/graphic-slide-deck/references/style-presets.md

@@ -0,0 +1,314 @@
+# Style Presets
+
+8 business-oriented style presets. Each is fully self-contained -- complete CSS token set, no "derive from" chains.
+
+Choose based on purpose and audience. When in doubt: clean-slate for sales, midnight-editorial for investor, matt-gray for internal.
+
+---
+
+## 1. midnight-editorial
+
+**Best for:** Investor decks, premium B2B, thought leadership presentations
+**Feeling:** Editorial authority, premium, considered
+
+```
+Background:       #0A0A0A outer / #111111 slide / #1A1A1A elevated cards / #080808 footer
+Text primary:     #F2F2F2
+Text secondary:   #AAAAAA
+Text muted:       #555555
+Accent:           #D8F90A  (yellow-green)
+Accent text:      #0A0A0A  (dark text on accent)
+Divider:          #2A2A2A
+Card border:      #222222
+
+Display font:     'Instrument Serif', Georgia, 'Times New Roman', serif
+Body font:        Inter, Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&family=Inter:wght@400;500;600;700&display=swap
+
+Display weight:   400 (Instrument Serif is a display weight at 400)
+Body weight:      400 / 600 (bold callouts)
+```
+
+**Signature elements:**
+- Thin `<hr>` separators between content blocks (`border: none; border-top: 1px solid #2A2A2A; width: 40px; margin: 0`)
+- Oversized section numbers at `opacity: 0.08` as absolute background elements
+- Instrument Serif italic on quote-callout slides (adds literary weight)
+- stat-highlight numbers in `#D8F90A` accent color
+- section-divider bg: `#D8F90A` with `#0A0A0A` text (full inversion)
+
+**Background depth via section alternation:**
+- Header / opening slides: `#0A0A0A`
+- Main content slides: `#111111`
+- Elevated cards (stats, callouts): `#1A1A1A`
+- Closing slide: `#D8F90A` full bg with dark text
+
+---
+
+## 2. matt-gray
+
+**Best for:** Internal decks, operational reviews, professional presentations to mixed audiences
+**Feeling:** Safe, professional, accessible, clean
+
+```
+Background:       #F5F5F5 outer / #FFFFFF slide / #EEEEEE section alt / #F8F8F8 footer
+Text primary:     #1A1A1A
+Text secondary:   #444444
+Text muted:       #888888
+Accent:           #2563EB  (blue)
+Accent text:      #FFFFFF  (white text on accent)
+Divider:          #E5E5E5
+Card border:      #DDDDDD
+Card shadow:      0 1px 3px rgba(0, 0, 0, 0.08)
+
+Display font:     'DM Sans', Arial, Helvetica, sans-serif
+Body font:        'DM Sans', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=DM+Sans:wght@400;500;700;800&display=swap
+
+Display weight:   700
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- 4px left border on section-divider and section heading elements (`border-left: 4px solid #2563EB; padding-left: 1rem`)
+- Subtle drop shadow on stat-highlight cards
+- Stat numbers in accent blue
+- section-divider: `#EEEEEE` background (slight contrast from main white), left-border accent treatment
+- Clean rectangular buttons if any CTAs (`border-radius: 6px`)
+
+---
+
+## 3. clean-slate
+
+**Best for:** Sales decks, customer-facing presentations, any audience that expects professionalism
+**Feeling:** Trustworthy, clear, confident, enterprise-safe
+
+```
+Background:       #FFFFFF outer / #FFFFFF slide / #F8F8F8 alt sections / #F4F4F4 footer
+Text primary:     #111111
+Text secondary:   #555555
+Text muted:       #999999
+Accent:           #0F172A  (near-black navy)
+Accent light:     #E0F2FE  (light blue for pill/badge backgrounds)
+Accent text:      #FFFFFF
+Divider:          #E8E8E8
+Card border:      #E0E0E0
+Card radius:      16px
+Card shadow:      0 2px 8px rgba(0, 0, 0, 0.06)
+
+Display font:     'Plus Jakarta Sans', Arial, Helvetica, sans-serif
+Body font:        'Plus Jakarta Sans', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:wght@400;500;600;800&display=swap
+
+Display weight:   800
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- Rounded card containers on all callout elements (`border-radius: 16px`)
+- Badge pills for category labels and key points (`border-radius: 100px; background: #E0F2FE; color: #0F172A; padding: 0.2em 0.8em`)
+- Generous whitespace -- padding toward the maximum of each `clamp()` range
+- stat-highlight: dark `#0F172A` numbers on white background (high contrast, no color distraction)
+- section-divider: dark `#111111` background (inverts the white deck)
+- closing-cta: `#0F172A` full bg with white text
+
+---
+
+## 4. brutalist
+
+**Best for:** Startup pitches, design-forward tech audiences, conference talks with strong POV
+**Feeling:** Direct, raw, confident, uncompromising
+
+```
+Background:       #FFFFFF outer / #FFFFFF slide
+Text primary:     #000000
+Text secondary:   #333333
+Accent:           #FF3300  (red) or #FFE500 (yellow)
+Accent text:      #000000  (both red and yellow are light enough for dark text)
+Divider:          #000000  (solid black)
+Border:           3px solid #000000  (heavy)
+Border-radius:    0 (zero everywhere -- no rounded corners)
+
+Display font:     'Archivo Black', Arial Black, Arial, sans-serif
+Body font:        'Space Grotesk', Arial, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Archivo+Black&family=Space+Grotesk:wght@400;500;700&display=swap
+
+Display weight:   900
+Body weight:      400 / 700
+```
+
+**Signature elements:**
+- Heavy borders everywhere: `border: 3px solid #000000` on cards, tables, section elements
+- Zero border-radius on all elements -- absolute rule for this style
+- Oversized section numbers in accent color (`font-size: clamp(6rem, 15vw, 12rem); opacity: 1` -- fully visible, not ghosted)
+- section-divider: accent color full background (`#FF3300` or `#FFE500`) with black text
+- stat-highlight: numbers in accent color, extreme size
+- comparison-table: bold black borders, no row alternation -- raw grid
+
+**DO NOT apply rounded corners, gradients, or drop shadows to brutalist decks. The aesthetic requires hard edges.**
+
+---
+
+## 5. mint-pixel-corporate
+
+**Best for:** SaaS sales, product demos, tech company pitches, growth-stage startups
+**Feeling:** Fresh, modern, startup-professional
+
+```
+Background:       #F0FAF7 outer / #FFFFFF slide / #E8F5F0 alt sections / #F0FAF7 footer
+Text primary:     #1A2E2A
+Text secondary:   #4A6B62
+Text muted:       #7A9B92
+Accent:           #00B894  (mint)
+Accent text:      #1A2E2A  (dark text on mint)
+Divider:          #D1E8E1
+Card border:      #C5DFD7
+Card radius:      10px
+
+Display font:     'Manrope', Arial, Helvetica, sans-serif
+Body font:        'Manrope', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Manrope:wght@400;500;700;800&display=swap
+
+Display weight:   800
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- CSS `radial-gradient` dot pattern on section-divider slides:
+  ```css
+  background-image: radial-gradient(circle, #00B894 1px, transparent 1px);
+  background-size: 24px 24px;
+  background-color: #1A2E2A;
+  ```
+- Mint accent pills for feature highlights (`border-radius: 100px; background: #00B894; color: #1A2E2A; padding: 0.15em 0.75em; font-size: clamp(0.65rem, 1vw, 0.8rem)`)
+- Screenshot frames with mint border (`border: 2px solid #00B894; border-radius: 8px`)
+- section-divider: dark `#1A2E2A` background with dot pattern + mint text
+- stat-highlight: mint numbers on white background
+
+---
+
+## 6. product-minimal
+
+**Best for:** Product demos, feature showcases, design system presentations, design-forward audiences
+**Feeling:** Maximum whitespace, purposeful restraint, design system precision
+
+```
+Background:       #FAFAFA outer / #FAFAFA slide / #F4F4F4 alt / #F0F0F0 footer
+Text primary:     #18181B
+Text secondary:   #71717A
+Text muted:       #A1A1AA
+Accent:           #8B5CF6  (violet)
+Accent text:      #FFFFFF  (white on violet)
+Divider:          #E4E4E7
+Card shadow:      0 1px 3px rgba(0, 0, 0, 0.08)
+Card radius:      12px
+
+Display font:     'Syne', Arial, Helvetica, sans-serif
+Body font:        'IBM Plex Sans', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Syne:wght@400;700;800&family=IBM+Plex+Sans:wght@400;500;600&display=swap
+
+Display weight:   700-800
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- Single accent element per slide rule: the accent color (`#8B5CF6`) appears in AT MOST ONE place per slide -- this creates intentional scarcity that reads premium
+- Subtle CSS drop shadow on cards: `box-shadow: 0 1px 3px rgba(0, 0, 0, 0.08)` -- barely visible, adds depth
+- Very generous padding (use maximum clamp values)
+- stat-highlight: violet stat numbers with a thin violet top-border on each stat card
+- section-divider: `#18181B` full bg with Syne display font + white text
+- closing-cta: violet background (`#8B5CF6`) with white text
+
+---
+
+## 7. magazine-red
+
+**Best for:** Marketing campaign reviews, brand presentations, bold internal reporting, conference openers
+**Feeling:** Authoritative, editorial, high energy, unmissable
+
+```
+Background:       #1A1A1A outer / #111111 slide / #1E1E1E alt / #0D0D0D footer
+Text primary:     #FFFFFF
+Text secondary:   #CCCCCC
+Text muted:       #888888
+Accent:           #E63329  (red)
+Accent secondary: #FFFFFF
+Divider:          #2A2A2A
+
+Display font:     'Fraunces', Georgia, 'Times New Roman', serif
+Body font:        'Work Sans', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Fraunces:ital,wght@0,900;1,900&family=Work+Sans:wght@400;500;600&display=swap
+
+Display weight:   900
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- 8px full-width horizontal red band: `<div style="width:100%; height:8px; background:#E63329; margin: clamp(1rem, 2vw, 2rem) 0">` used as visual separator
+- Editorial section numbers in red, visible opacity (`opacity: 0.3` -- not fully ghosted like midnight-editorial)
+- quote-callout slides: INVERTED to white background with dark text (the only white slide in the deck)
+  ```css
+  .slide--quote-callout { background: #FFFFFF; color: #111111; }
+  ```
+- Fraunces italic for quote text: extreme editorial weight
+- stat-highlight: red accent numbers, large
+- closing-cta: full red background (`#E63329`) with white text
+
+---
+
+## 8. soft-cloud
+
+**Best for:** Onboarding decks, customer education, approachable SaaS, HR/people presentations
+**Feeling:** Friendly, accessible, soft, welcoming -- high trust, low intimidation
+
+```
+Background:       #EEF2FF outer / #FFFFFF slide / #F5F3FF alt / #EEF2FF footer
+Text primary:     #1E1B4B
+Text secondary:   #4C4A7B
+Text muted:       #9896C0
+Accent:           #6366F1  (indigo)
+Accent light:     #E0E7FF  (light indigo for card backgrounds)
+Accent text:      #FFFFFF
+Divider:          #DDD6FE
+Card radius:      24px  (soft, generous)
+Card shadow:      0 4px 16px rgba(99, 102, 241, 0.08)
+
+Display font:     'Outfit', Arial, Helvetica, sans-serif
+Body font:        'Outfit', Arial, Helvetica, sans-serif
+Google Fonts:     https://fonts.googleapis.com/css2?family=Outfit:wght@400;500;600;700&display=swap
+
+Display weight:   700
+Body weight:      400 / 500
+```
+
+**Signature elements:**
+- Generous border-radius everywhere: `border-radius: 24px` on all cards, callout blocks, stat containers
+- Gradient section-dividers:
+  ```css
+  background: linear-gradient(135deg, #EEF2FF 0%, #E0E7FF 50%, #DDD6FE 100%);
+  ```
+- Badge pills on key points: `border-radius: 100px; background: #E0E7FF; color: #6366F1; padding: 0.2em 0.9em`
+- stat-highlight: stat numbers in indigo on `#F5F3FF` elevated card background
+- All `<hr>` dividers: `border-color: #DDD6FE` (matches the soft palette)
+- closing-cta: indigo gradient background
+  ```css
+  background: linear-gradient(135deg, #6366F1 0%, #8B5CF6 100%);
+  ```
+
+---
+
+## DO NOT USE -- Style Slop Checklist
+
+Before outputting any HTML, verify none of these are present:
+
+| Pattern | Why it's wrong |
+|---|---|
+| Inter as display font | Zero typographic character -- reads as default AI output |
+| Purple-to-blue gradient on white background | Most overused "modern" AI aesthetic -- immediately signals undesigned |
+| Every slide centered with the same layout | No typographic thinking, looks like a PowerPoint default theme |
+| Identical slide backgrounds throughout | No visual rhythm -- the deck reads as one long scroll |
+| `box-shadow` on everything | Overused "depth" signal that adds no real depth |
+| `border-radius: 8px` on everything (even brutalist) | Softening that fights the style's aesthetic intent |
+| Accent color on 5+ elements per slide | Over-branded, destroys scarcity = destroys premium feel |
+| Helvetica Neue / Arial as display font | Generic -- no personality at display size |
+| Stat numbers at body text size | Doesn't understand the stat-highlight layout's purpose |
+| "Thank You" as closing slide | Missed the closing-cta layout's entire purpose |

package/skills/meta-ads-skill/README.md

@@ -28,9 +28,9 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ## Overview
 
-The **Meta Ads Skill** is a comprehensive, production-ready OpenCode skill designed to give LLMs and AI agents expert-level capabilities to orchestrate the [Varnan-Tech Meta Ads MCP Server](https://github.com/Varnan-Tech/Meta-Ads-MCP). 
+The **Meta Ads Skill** is a comprehensive, production-ready  skill designed to give LLMs and AI agents expert-level capabilities to orchestrate the official **Meta Ads Python CLI**.
 
-By using this skill, an agent transforms into an **Expert Media Buyer**. It will know exactly how to safely authenticate, explore ad structures, troubleshoot campaign performance (like CPA spikes), discover new audiences, and format massive Meta APIs JSON payloads into beautiful, readable markdown reports.
+By using this skill, an agent transforms into an **Expert Media Buyer**. It will know exactly how to explore ad structures, troubleshoot campaign performance (like CPA spikes), discover new audiences, and format massive Meta APIs JSON payloads into beautiful, readable markdown reports.
 
 ---
 
@@ -39,63 +39,36 @@ By using this skill, an agent transforms into an **Expert Media Buyer**. It will
 This skill is designed using a **Progressive Disclosure (Hub-and-Spoke)** architecture to maximize context window efficiency:
 
 1. **The Hub (`SKILL.md`)**: The primary entry point. It provides strict guardrails, safety protocols, and the authentication troubleshooting workflow.
-2. **The Spokes (`references/` & `scripts/`)**: 
+2. **The Spokes (`references/`)**: 
    - When you need to perform a specific task (e.g., investigating a CPA spike), read `references/workflows.md` for the exact step-by-step orchestration strategy.
    - When presenting data to the user, read `references/report_templates.md` to strictly follow the required Markdown layout.
-   - **Data Parsing**: Meta Ads JSON responses are massive. *Always* use the provided `scripts/formatters.py` to condense raw JSON from `get_campaigns`, `get_adsets`, or `get_insights` into clean markdown tables before reasoning over them.
 
 ###  Strict Agent Guardrails
 * **Context Protection**: ALWAYS default to `time_range="last_7d"` for insights. ALWAYS use `limit=10` for listing campaigns/adsets initially.
-* **Safety First**: NEVER execute state-changing tools (`create_campaign`, `update_campaign`, `clear_database`, `reset_database`) without explicitly showing the parameters to the user and waiting for their affirmative confirmation.
+* **Safety First**: NEVER execute state-changing tools (`create_campaign`, `update_campaign`) without explicitly showing the parameters to the user and waiting for their affirmative confirmation.
 
 ---
 
-## Installation & Setup of the Meta Ads MCP
+## Installation & Setup
 
-To use this skill, the host machine must have the Varnan-Tech Meta Ads MCP Server installed and running. 
+To use this skill, you must install the official Meta Ads CLI and configure your credentials.
 
-### 1. Prerequisites
-- **Python 3.10+**
-- A **Meta Developer Account** with a configured App.
-
-### 2. Configure the Meta App
-1. Go to the [Facebook Developers Portal](https://developers.facebook.com/).
-2. Create an App and add the **Marketing API** product.
-3. Under the Facebook Login settings, add `http://localhost:8000/auth/facebook/callback` to the **Valid OAuth Redirect URIs**.
-4. Retrieve your **App ID** and **App Secret**.
-
-### 3. Server Setup
-Clone the MCP repository:
+### 1. Install the CLI
+The skill relies on the `meta-ads` Python package:
 ```bash
-git clone https://github.com/Varnan-Tech/Meta-Ads-MCP.git
-cd Meta-Ads-MCP
-pip install -r requirements.txt
+pip install meta-ads
 ```
 
-Create a `.env` file in the root of the MCP server:
-```env
-FB_APP_ID="your_facebook_app_id"
-FB_APP_SECRET="your_facebook_app_secret"
-FB_OAUTH_ENABLED="true"
-FB_REDIRECT_URI="http://localhost:8000/auth/facebook/callback"
-DATABASE_URL="sqlite:///.meta-ads-mcp/oauth.db"
-```
-
----
-
-## Authentication Workflow
-
-The server uses OAuth backed by a local SQLite database to seamlessly pass tokens to the MCP context.
-
-1. **Start the local Auth Server**:
-   ```bash
-   python src/auth/run_web_server.py
-   ```
-2. **Authenticate**: Open `http://localhost:8000/auth/facebook` in your web browser.
-3. **Grant Permissions**: Click "Connect Facebook" and approve the `ads_management`, `ads_read`, and `read_insights` permissions.
-4. **Completion**: The OAuth token is saved securely to the SQLite DB. The agent can now use the MCP tools automatically without needing the token pasted into the prompt.
+### 2. Authentication (System User Token)
+The CLI uses a **System User Access Token** for authentication. 
+1. Generate a System User Token in your [Meta Business Suite](https://business.facebook.com/settings/system-users).
+2. Ensure the token has `ads_management`, `ads_read`, and `read_insights` permissions.
+3. Set the following environment variables on your machine:
 
-*If an agent encounters an Auth Error during operation, it is instructed by this skill to guide the user back through this exact login flow.*
+```bash
+export ACCESS_TOKEN="your_system_user_access_token"
+export AD_ACCOUNT_ID="act_your_ad_account_id"
+```
 
 ---
 
@@ -109,16 +82,12 @@ meta-ads-skill/
  references/
     report_templates.md           # Standardized markdown report structures
     workflows.md                  # Orchestration strategies (e.g., CPA troubleshooting)
- scripts/
-     auth_check.py                 # Diagnostic script for token status
-     formatters.py                 # JSON -> Markdown table utilities
 ```
 
-## Supported Tools (via MCP)
+## Supported Commands
 
-Through the underlying MCP, this skill orchestrates:
-* **Account Management**: `get_ad_accounts()`, `get_account_info()`
-* **Campaigns & Ads**: `get_campaigns()`, `get_adsets()`, `get_ads()`, `create_campaign()`, `update_campaign()`
-* **Analytics**: `get_insights()`, `analyze_campaigns()`
-* **Targeting**: `search_interests()`, `search_demographics()`, `estimate_audience_size()`
-* **Database**: `token_status()`, `clear_database()`, `reset_database()`
+This skill orchestrates the `meta-ads` CLI using a noun-verb structure:
+* **Campaigns**: `meta ads campaign list`, `meta ads campaign create`
+* **Ad Sets**: `meta ads adset list`
+* **Ads**: `meta ads ad list`
+* **Insights**: `meta ads insights get`

package/skills/meta-ads-skill/meta-ads-skill/SKILL.md

@@ -1,41 +1,58 @@
 ---
 name: meta-ads-expert
-description: Use when interacting with the Meta Ads MCP server to manage accounts, campaigns, ads, insights, and targeting, or to troubleshoot OAuth token authentication. Act as an Expert Media Buyer.
+description: Use when interacting with the Meta Ads CLI to manage accounts, campaigns, ads, and insights. Act as an Expert Media Buyer.
 ---
 
 # Meta Ads Expert Skill
 
-**Persona:** You are an Expert Media Buyer. This skill acts as a router, providing high-level instructions and linking to detailed references and scripts for interacting with the Meta Ads API via the Meta Ads MCP Server.
+**Persona:** You are an Expert Media Buyer. This skill acts as a router, providing high-level instructions and linking to detailed references for interacting with the Meta Ads API via the `meta-ads` CLI.
 
 ## Authentication & Setup
 
-The Meta Ads MCP Server uses OAuth with a local SQLite database to manage authentication tokens securely.
+The Meta Ads CLI uses a **System User Access Token** for authentication.
 
-### Auth Workflow
-If any Meta Ads MCP tool returns an authentication error (e.g., missing token, expired token):
-1. **Run Auth Check**: Use the auth helper script `scripts/auth_check.py` to diagnose issues.
-2. **Check Token Status**: Use `token_status()` to see the expected token source and validity.
-3. **Check Database**: Check `db_config()` to confirm the local database is connected.
-4. **Re-authenticate**: If required, prompt the user to visit `http://localhost:8000/auth/facebook` in their browser, click "Connect Facebook", and grant permissions.
+### Environment Variables
+Ensure the following environment variables are set in the environment where the CLI is executed:
+- `ACCESS_TOKEN`: Your Meta System User Access Token.
+- `AD_ACCOUNT_ID`: Your target Ad Account ID (e.g., `act_123456789`).
 
-## Orchestration Workflows
+**CRITICAL:** NEVER use inline tokens in commands (e.g., `meta ads --token <TOKEN>`). Always rely on environment variables or pre-configured config files.
 
-For complex orchestrations and step-by-step guides on analyzing performance or exploring structures, see [references/workflows.md](references/workflows.md).
+## CLI Routing
 
-For reporting standards and output templates, see [references/report_templates.md](references/report_templates.md).
+Map your intent to the following `meta-ads` CLI commands:
+
+| Intent | CLI Command |
+|---|---|
+| List Ad Accounts | `meta ads account list` |
+| List Campaigns | `meta ads campaign list` |
+| List Ad Sets | `meta ads adset list` |
+| List Ads | `meta ads ad list` |
+| Get Insights | `meta ads insights get` |
+| Create Campaign | `meta ads campaign create` |
 
 ## Strict Guardrails
 
-### Date Ranges & Pagination
+### Command Execution
+- **JSON Output**: ALWAYS use `--output json` for all read operations to ensure structured data for analysis.
+- **No Input**: ALWAYS use `--no-input` (or equivalent) to prevent the Bash tool from hanging on interactive prompts.
+- **Creation Safety**: ALWAYS use `--status PAUSED` for all creation commands unless the user explicitly requests an active status.
 
-To prevent context window overflow and API rate limits, **ALWAYS** apply strict date ranges and limits:
-- **Pagination Limits**: When listing items (e.g., `get_campaigns()`, `get_adsets()`, `get_ads()`), cap the limit parameter to `limit=10` initially. Only expand if explicitly required.
-- **Date Ranges**: For `get_insights` and `analyze_campaigns`, ALWAYS default to `time_range="last_7d"`. Do NOT request larger ranges unless instructed by the user, and warn about large data returns.
+### Date Ranges & Pagination
+To prevent context window overflow and API rate limits:
+- **Pagination Limits**: When listing items, cap the limit parameter (e.g., `--limit 10`) initially. Only expand if explicitly required.
+- **Date Ranges**: For insights, ALWAYS default to `--time-range last_7d`. Do NOT request larger ranges unless instructed by the user.
 
 ## Safety Guardrails (State-Changing Actions)
 
-You MUST require explicit user confirmation before executing any state-changing tools (e.g., `create_campaign`, `update_campaign`, `clear_database`, `reset_database`).
+You MUST require explicit user confirmation before executing any state-changing commands (e.g., `campaign create`, `campaign update`).
 
-1. Present the exact parameters to the user.
+1. Present the exact CLI command and parameters to the user.
 2. Ask for explicit approval.
 3. Only proceed if approved.
+
+## Orchestration Workflows
+
+For complex orchestrations (e.g., CPA spike analysis), see [references/workflows.md](references/workflows.md).
+
+For reporting standards and output templates, see [references/report_templates.md](references/report_templates.md).

package/skills/meta-ads-skill/meta-ads-skill/references/report_templates.md

@@ -1,6 +1,6 @@
 # Meta Ads Report Templates
 
-Use these markdown templates when generating reports and summaries for users.
+Use these markdown templates when generating reports and summaries for users. These templates are designed to be populated using the structured data from the `meta-ads` CLI's JSON output (`--output json`).
 
 ## 1. Executive Summary Template
 
@@ -10,11 +10,12 @@ Use these markdown templates when generating reports and summaries for users.
 ##  Executive Summary
 [2-3 sentences summarizing the overall performance. E.g., "Account performance remained stable this week with a 5% increase in ROAS, primarily driven by the new Retargeting campaign. However, top-of-funnel CPA has started to rise."]
 
-##  Key Metrics
+##  Key Metrics (Source: `meta ads insights get`)
 - **Spend:** $[Amount] ([+/-]% vs previous period)
 - **Revenue/Conversions:** [Amount] ([+/-]% vs previous period)
 - **CPA:** $[Amount] ([+/-]% vs previous period)
 - **ROAS:** [Amount]x ([+/-]% vs previous period)
+- **CTR:** [Amount]% ([+/-]% vs previous period)
 
 ##  Key Findings
 - **Highlight 1:** [E.g., Campaign X is driving 60% of total conversions at a very efficient CPA.]
@@ -35,7 +36,7 @@ Use these markdown templates when generating reports and summaries for users.
 ##  The Issue
 [Briefly state the problem. E.g., "CPA increased from $20 to $35 starting on [Date]."]
 
-##  Root Cause Analysis
+##  Root Cause Analysis (Source: `meta ads insights get --level [level]`)
 - **Campaign Level:** [Identify which campaign(s) caused the spike.]
 - **Ad Set Level:** [Identify specific ad sets. Did a lookalike audience degrade? Did a specific placement get expensive?]
 - **Ad Level:** [Identify ad fatigue, drop in CTR, increase in CPM, or decrease in conversion rate.]

package/skills/meta-ads-skill/meta-ads-skill/references/workflows.md

@@ -1,36 +1,31 @@
 # Meta Ads Workflows
 
-This document outlines complex orchestrations and workflows for common Meta Ads tasks.
+This document outlines complex orchestrations and workflows for common Meta Ads tasks using the `meta-ads` CLI.
 
 ## 1. CPA Spike Troubleshooting
 
 When a client or user asks to investigate a spike in Cost Per Action (CPA), follow this systematic approach:
 
 1. **Account Level Overview**
-   - **Tool:** `get_ad_accounts` (if account ID not provided)
-   - **Tool:** `get_insights` (Level: account)
+   - **Command:** `meta ads insights get --level account --time-range last_30d --output json`
    - **Action:** Look at overall account performance over the last 7, 14, and 30 days to identify when the spike started.
 
 2. **Campaign Breakdown**
-   - **Tool:** `get_campaigns`
-   - **Tool:** `get_insights` (Level: campaign)
+   - **Command:** `meta ads campaign list --output json`
+   - **Command:** `meta ads insights get --level campaign --time-range last_7d --output json`
    - **Action:** Identify which specific campaigns are driving the CPA increase. Compare spend and CPA across active campaigns.
 
 3. **Ad Set Deep Dive**
-   - **Tool:** `get_adsets`
-   - **Tool:** `get_insights` (Level: adset)
+   - **Command:** `meta ads adset list --campaign-id <ID> --output json`
+   - **Command:** `meta ads insights get --level adset --time-range last_7d --output json`
    - **Action:** For the offending campaigns, break down by Ad Set to see if specific audiences or placements are underperforming.
 
 4. **Ad & Creative Analysis**
-   - **Tool:** `get_ads`
-   - **Tool:** `get_insights` (Level: ad)
+   - **Command:** `meta ads ad list --adset-id <ID> --output json`
+   - **Command:** `meta ads insights get --level ad --time-range last_7d --output json`
    - **Action:** Check if specific ads are experiencing ad fatigue (high frequency, dropping CTR) or if recent changes disrupted the learning phase.
 
-5. **Advanced Insights (Optional)**
-   - **Tool:** `analyze_campaigns`
-   - **Action:** Run automated analysis on the specific campaigns to generate actionable recommendations.
-
-6. **Synthesis and Reporting**
+5. **Synthesis and Reporting**
    - Use the `CPA Spike Investigation Report` template (found in `report_templates.md`) to structure the findings and recommendations.
 
 ## 2. New Audience Discovery
@@ -38,7 +33,7 @@ When a client or user asks to investigate a spike in Cost Per Action (CPA), foll
 When a user wants to find new audiences or test new targeting:
 
 1. **Review Current Top Performers**
-   - **Tool:** `get_insights` (Level: adset)
+   - **Command:** `meta ads insights get --level adset --time-range last_30d --output json`
    - **Action:** Identify the ad sets currently delivering the best ROAS/CPA.
 
 2. **Generate Audience Ideas**
@@ -46,6 +41,7 @@ When a user wants to find new audiences or test new targeting:
 
 3. **Structure the Test**
    - Recommend a campaign structure for testing (e.g., A/B testing with Campaign Budget Optimization (CBO) or Ad Set Budget Optimization (ABO)).
+   - **Command Example:** `meta ads campaign create --name "Test_Audience_X" --status PAUSED --no-input`
 
 4. **Monitoring**
    - Provide the exact metrics to watch (e.g., CTR, CPC, early conversions) over the next 3-7 days.