adspirer-setup
Set up your brand workspace — connect to Adspirer, scan brand docs, pull campaign data, and create AGENTS.md. Use on first time in a new brand folder, or when the user wants to refresh brand context.
What this skill does
Run the full brand workspace setup. Follow these steps in order:
## Step 1: Connect to Adspirer
Call `get_connections_status` directly.
- **If it works**: continue to step 2.
- **If the MCP server is not found**: tell the user:
"The Adspirer MCP server isn't connected. Run:
`codex mcp add adspirer --url https://mcp.adspirer.com/mcp`
Then restart Codex, authenticate via `/mcp`, and run `$adspirer-setup` again."
- **If OAuth is triggered**: tell the user a browser window is opening for authentication. Wait for them to confirm, then retry.
- **If no platforms are connected**: tell the user to connect ad accounts at https://adspirer.ai/connections, then run setup again.
## Step 2: Scan local folder
Search for brand documentation files: `**/*.md`, `**/*.txt`, `**/*.csv`, `**/*.yaml`, `**/*.json`, `**/*.pdf`
Read all discovered files. Extract:
- Brand name and industry
- Products/services
- Target audience descriptions
- Brand voice and tone indicators
- Competitor mentions
- Budget information
- KPI targets or performance goals
- Previous campaign strategies or results
If the folder is empty, that's fine — we'll build context from Adspirer data alone.
## Step 3: Pull live campaign data
Call these Adspirer MCP tools (in parallel where possible):
1. `get_connections_status` — which platforms are connected
2. `get_business_profile` — saved brand profile
3. `list_campaigns` — existing campaigns across all platforms
4. `get_campaign_performance` (lookback_days: 30) — Google Ads performance
5. `get_linkedin_campaign_performance` (lookback_days: 30) — LinkedIn performance
6. `get_meta_campaign_performance` (lookback_days: 30) — Meta performance
7. `get_benchmark_context` — industry benchmarks
If any tool errors (platform not connected), skip it and note the gap.
## Step 4: Create AGENTS.md
Generate `AGENTS.md` at the project root. Combine local files + Adspirer data:
```markdown
# [Brand Name] — Paid Media Workspace
## Brand Overview
[From docs + Adspirer: what they sell, who they sell to, industry, company size]
## Brand Voice
[From docs: tone, language style, prohibited words, preferred phrases]
[If not found: "No brand voice docs found — add guidelines to this folder to improve ad copy quality"]
## Target Audiences
[From docs + Adspirer campaign targeting data]
[List each audience with platform-specific targeting parameters if available]
## Active Platforms
[From get_connections_status]
- Google Ads: [connected/not connected] — [X active campaigns]
- Meta Ads: [connected/not connected] — [X active campaigns]
- LinkedIn Ads: [connected/not connected] — [X active campaigns]
- TikTok Ads: [connected/not connected] — [X active campaigns]
## Budget & Guardrails
[From docs if available, otherwise from Adspirer campaign data]
- Monthly total: [amount or "Not specified — ask user"]
- Platform allocation: [percentages or "Based on current spend: ..."]
- Max CPC: [if specified]
- Target CPA: [if specified]
- Min ROAS: [if specified]
## KPI Targets
[From docs if available]
- Primary goal: [leads/sales/awareness/traffic]
- Target metrics: [CTR, CPA, ROAS targets]
## Current Performance Snapshot
[From get_campaign_performance — most recent data]
| Platform | Campaigns | Monthly Spend | CTR | CPA | ROAS |
|----------|-----------|---------------|-----|-----|------|
| ... | ... | ... | ... | ... | ... |
## Key Findings from Existing Campaigns
[From analyze_search_terms + performance data]
- Top performing keywords: ...
- Top performing campaigns: ...
- Wasted spend areas: ...
- Recommendations: ...
## Competitors
[From docs if available]
## Seasonality
[From docs if available]
## Notes
[Anything else relevant found in docs]
[Gaps: "No brand voice guide found", "No budget specified", etc.]
[Known constraints:
- Conversion action primary/secondary setup is configured manually in Google Ads UI (not via Adspirer MCP)
- Campaign creation should be considered complete only after post-create verification of ads, keywords, and extensions]
## Strategy
Active strategy directives are maintained in `STRATEGY.md`. All skills and agents read
that file before campaign creation, keyword research, and ad copy generation.
```
Fill in every section with real data. Leave placeholders only for sections where no data was found — and note the gap.
### Step 4.5: Create STRATEGY.md
Create `STRATEGY.md` at the project root alongside AGENTS.md:
```markdown
# [Brand Name] — Strategy Playbook
<!-- This file holds strategic decisions that guide campaign creation, keyword research,
audience targeting, and budget allocation across all platforms. Skills and agents
read this file before execution. Directives are guidance that informs research —
not rigid rules that bypass validation. Only save directives the user has confirmed. -->
## Active Directives
### Cross-Platform Strategy
[No active directives yet — run a strategy analysis to populate]
### Google Ads
[No active directives]
### Meta Ads
[No active directives]
### LinkedIn Ads
[No active directives]
### TikTok Ads
[No active directives]
### Budget Allocation
[No active directives]
---
## Decision Log
[No decisions yet — this log will be populated as strategy sessions occur]
---
## Archived Directives
[No archived directives]
```
## Step 5: Present summary
Tell the user:
- Which platforms are connected and how many campaigns are active
- A quick performance snapshot (spend, CTR, CPA, ROAS)
- Key findings (top campaigns, wasted spend, opportunities)
- Any gaps ("No brand voice docs found — drop guidelines in this folder anytime")
End with:
"Your brand workspace is set up! I've saved everything to AGENTS.md.
Here's what I can help with:
- Review campaign performance across all platforms
- Find and fix wasted ad spend
- Write brand-voice ad copy
- Create new campaigns
- Research keywords
- Set up monitoring and alerts
What would you like to start with?"
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".