| name | 34-ai-marketing-os-global |
| description | Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`. |
| metadata | {"version":"1.0.1","category":"operations"} |
| license | MIT |
| triggers | ["AI marketing OS","marketing AI system","Brand Hub","AI workflow","AI team SOP","MCP marketing","second brain marketing"] |
| related | ["product-marketing-context-global","00-marketing-plan-global","02-campaign-brief-global","07-marketing-report-global","10-reverse-kpi-global","13-data-analysis-global","21-ads-audit-global","31-offer-design-global"] |
AI Marketing OS (Global)
This skill designs the operating system for AI-assisted marketing: source of truth, roles, skill chains, data loops, review cadence, and handoffs. The goal is to help a team use AI as an operating system, not as scattered one-off prompts.
Information gathering
Read .agents/product-marketing-context-global.md if available. If the user has a plan, dashboard, SOP, Notion/Drive structure, ads report, or campaign brief, use it as input. Ask up to 4 questions: team structure, 90-day goal, current AI/tool stack, and biggest workflow pain. For detailed patterns, read references/ai-marketing-os-playbook.md.
When to use
Use this skill when the user needs to:
- Build an AI Marketing OS for an SMB, agency, SaaS team, creator-led business, education business, service business, or B2B team.
- Audit how the team uses AI: repeated prompts, lost context, disconnected chats, weak reporting, or no source of truth.
- Design a Brand Hub, skill chain, role-based agent/project setup, MCP/connectors, and Notion/Drive second brain.
- Create daily, weekly, and monthly SOPs for content, performance, campaigns, reporting, and handoffs.
Do not use this skill for a single artifact. Use the relevant older skill instead: 00-marketing-plan-global, 01-content-calendar-global, 02-campaign-brief-global, 05-ad-copy-global, 07-marketing-report-global, 10-reverse-kpi-global, or 31-offer-design-global.
Principles
- Brand Hub is the source of truth. Scattered context creates inconsistent agent output.
- Roles before tools. Define Strategy, Campaign, Content, Design, Performance, and Sales/RevOps before choosing tools.
- Skill chains beat one-off prompts. Every workflow should define input, skill, output, and next skill.
- Old data before new plans. New plans should read previous reports, dashboards, bottlenecks, and lessons.
- Human approval at risk points. Budget, claims, legal/privacy, brand voice, and campaign launch need review.
- Small cycles, steady review. Daily check, weekly decision review, monthly retro, quarterly refresh.
Workflow
1. Audit the current AI stack
Score maturity from 0-4:
