34 AI marketing os global skill

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.

by minhnv0807·MIT license·★ 599 Stars on the repo·GitHub ↗

Use now

Files of 34 AI marketing os global

minhnv0807/master1 file shown
SKILL.md
Show the full text187 lines

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

  1. Brand Hub is the source of truth. Scattered context creates inconsistent agent output.
  2. Roles before tools. Define Strategy, Campaign, Content, Design, Performance, and Sales/RevOps before choosing tools.
  3. Skill chains beat one-off prompts. Every workflow should define input, skill, output, and next skill.
  4. Old data before new plans. New plans should read previous reports, dashboards, bottlenecks, and lessons.
  5. Human approval at risk points. Budget, claims, legal/privacy, brand voice, and campaign launch need review.
  6. 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:

Level Signal
0 Ad hoc AI use, no saved context
1 Prompt templates, but manual copy/paste
2 Context files and individual skills exist
3 Brand Hub, role workspaces, and review cadence exist
4 Connectors/data loops, dashboards, second brain, and governance exist

If maturity is below 2, build foundation before adding automation.

2. Design the Brand Hub

Minimum Brand Hub:

  1. Brand Guidelines: logo, color, typography, tone, voice, do/don't.
  2. Customer Insight: persona, pain, trigger, objection, customer language.
  3. Positioning & Offer: promise, proof, path, offer ladder.
  4. Content Pillars: pillars, angles, source content, platform rules.
  5. KPI Framework: revenue target, funnel KPI, benchmarks, decision rules.
  6. Campaign Template: phases, budget split, asset list, approval flow.

When a file changes, update the relevant role workspaces.

3. Map role workspaces
Role Main work Common repo skills
Strategy Market, offer, budget, KPI 00, 08, 09, 10, 31
Campaign Lead Brief, timeline, assets, handoff, retro 02, 07, 20, 34
Content Calendar, scripts, copy, UGC, email 01, 04, 05, 06, 14
Design Visual brief, brand system, landing page 12, 30
Performance Tracking, audit, reporting, data decisions 03, 07, 13, 19, 21
Sales/RevOps Lead quality, handoff, outreach 18, 33

If the user uses Claude Projects, ChatGPT Projects/GPTs, NotebookLM, Notion, Drive, or MCP, map each tool to these roles. Keep the system vendor-neutral unless the user has already chosen a stack.

4. Build skill chains

Default workflow chains:

Workflow Suggested chain
Brand/client onboarding product-marketing-context-global -> 09 -> 08 -> 31 -> 10 -> 34
Campaign launch 02 -> 31 -> 10 -> 01/04/05/06 -> 12 -> 21 -> 07
Weekly performance 13 -> 03/21 -> 07 -> 34 updates Brand Hub
Content engine 09 -> 01 -> 04/05/06 -> 15 -> 07

If previous-period data exists, read it before creating a new plan.

5. Set up data and second brain

Minimum stack:

  • Storage: Drive/SharePoint/Dropbox for files and assets.
  • Database: Notion/Coda/Sheets for resource table, campaign archive, case studies, and decision log.
  • Analytics: Meta Ads, TikTok Ads, Google Ads, GA4, CRM, email, UTM.
  • Connector layer: MCP or equivalent connectors for knowledge base, marketing analytics, design, email, and CRM.

Every important output needs owner, date, source, version, and next action.

6. Create operating cadence
Cadence Focus Output
Daily 15m Spend, delivery, comments/inbox, tracking issues Blocker list
Weekly 30-60m KPI vs target, winners/losers, bottleneck, next actions Weekly decision log
Monthly Revenue, channel mix, offer, team load, Brand Hub changes OS retro + roadmap
Quarterly Market, positioning, offer ladder, tool stack Strategy refresh
7. Governance and risk

Check:

  • Access: who can see customer data, ads data, CRM, and revenue.
  • Claims and proof: do not let AI invent proof or regulated claims.
  • Privacy: do not paste PII into unapproved tools.
  • Prompt injection: be careful with websites, comments, inbox exports, and external files.
  • Brand drift: compare new outputs against the Brand Hub.

Output template

# AI Marketing OS — [Business/team]

## 1. Current diagnosis
| Area | Level 0-4 | Evidence | Priority |

## 2. Brand Hub
| File | Status | Owner | Update cadence |

## 3. Role workspaces
| Role | Tool/workspace | Context loaded | Main output |

## 4. Skill chains
| Workflow | Skill chain | Required input | Output |

## 5. Data loop and connectors
| Data source | Tool/connector | Metric | Cadence |

## 6. Operating SOP
| Cadence | Owner | Checklist | Output location |

## 7. 30-60-90 day roadmap
| Phase | Work | Owner | Done when |

## 8. Risks and governance
| Risk | Mitigation | Approver |
  • product-marketing-context-global: create the initial source context.
  • 00-marketing-plan-global: create marketing plans inside the OS.
  • 02-campaign-brief-global: convert strategy into campaign execution.
  • 07-marketing-report-global: create the reporting layer for the data loop.
  • 13-data-analysis-global and 21-ads-audit-global: analyze data and find bottlenecks.
  • 31-offer-design-global, 32-seo-growth-global, 33-b2b-lead-gen-global: growth modules inside the OS.

Quality checklist

  • Has a clear Brand Hub, not scattered chat context.
  • Has role workspaces and skill chains, not just a tool list.
  • Uses previous data before creating new plans.
  • Defines daily/weekly/monthly cadence and output locations.
  • Includes owners, deadlines, and approval gates for campaigns, budget, and claims.
  • Covers privacy, access, prompt injection, and brand drift.
1---
2name: 34-ai-marketing-os-global
3description: "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`."
4metadata:
5 version: 1.0.1
6 category: operations
7license: MIT
8triggers:
9 - "AI marketing OS"
10 - "marketing AI system"
11 - "Brand Hub"
12 - "AI workflow"
13 - "AI team SOP"
14 - "MCP marketing"
15 - "second brain marketing"
16related:
17 - product-marketing-context-global
18 - 00-marketing-plan-global
19 - 02-campaign-brief-global
20 - 07-marketing-report-global
21 - 10-reverse-kpi-global
22 - 13-data-analysis-global
23 - 21-ads-audit-global
24 - 31-offer-design-global
25---
26 
27# AI Marketing OS (Global)
28 
29This 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.
30 
31## Information gathering
32 
33Read `.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`.
34 
35## When to use
36 
37Use this skill when the user needs to:
38 
39- Build an AI Marketing OS for an SMB, agency, SaaS team, creator-led business, education business, service business, or B2B team.
40- Audit how the team uses AI: repeated prompts, lost context, disconnected chats, weak reporting, or no source of truth.
41- Design a Brand Hub, skill chain, role-based agent/project setup, MCP/connectors, and Notion/Drive second brain.
42- Create daily, weekly, and monthly SOPs for content, performance, campaigns, reporting, and handoffs.
43 
44Do 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`.
45 
46## Principles
47 
481. **Brand Hub is the source of truth.** Scattered context creates inconsistent agent output.
492. **Roles before tools.** Define Strategy, Campaign, Content, Design, Performance, and Sales/RevOps before choosing tools.
503. **Skill chains beat one-off prompts.** Every workflow should define input, skill, output, and next skill.
514. **Old data before new plans.** New plans should read previous reports, dashboards, bottlenecks, and lessons.
525. **Human approval at risk points.** Budget, claims, legal/privacy, brand voice, and campaign launch need review.
536. **Small cycles, steady review.** Daily check, weekly decision review, monthly retro, quarterly refresh.
54 
55## Workflow
56 
57### 1. Audit the current AI stack
58 
59Score maturity from 0-4:
60 
61| Level | Signal |
62|-------|--------|
63| 0 | Ad hoc AI use, no saved context |
64| 1 | Prompt templates, but manual copy/paste |
65| 2 | Context files and individual skills exist |
66| 3 | Brand Hub, role workspaces, and review cadence exist |
67| 4 | Connectors/data loops, dashboards, second brain, and governance exist |
68 
69If maturity is below 2, build foundation before adding automation.
70 
71### 2. Design the Brand Hub
72 
73Minimum Brand Hub:
74 
751. Brand Guidelines: logo, color, typography, tone, voice, do/don't.
762. Customer Insight: persona, pain, trigger, objection, customer language.
773. Positioning & Offer: promise, proof, path, offer ladder.
784. Content Pillars: pillars, angles, source content, platform rules.
795. KPI Framework: revenue target, funnel KPI, benchmarks, decision rules.
806. Campaign Template: phases, budget split, asset list, approval flow.
81 
82When a file changes, update the relevant role workspaces.
83 
84### 3. Map role workspaces
85 
86| Role | Main work | Common repo skills |
87|------|-----------|--------------------|
88| Strategy | Market, offer, budget, KPI | 00, 08, 09, 10, 31 |
89| Campaign Lead | Brief, timeline, assets, handoff, retro | 02, 07, 20, 34 |
90| Content | Calendar, scripts, copy, UGC, email | 01, 04, 05, 06, 14 |
91| Design | Visual brief, brand system, landing page | 12, 30 |
92| Performance | Tracking, audit, reporting, data decisions | 03, 07, 13, 19, 21 |
93| Sales/RevOps | Lead quality, handoff, outreach | 18, 33 |
94 
95If the user uses Claude Projects, ChatGPT Projects/GPTs, NotebookLM, Notion, Drive, or MCP, map each tool to these roles. Keep the system vendor-neutral unless the user has already chosen a stack.
96 
97### 4. Build skill chains
98 
99Default workflow chains:
100 
101| Workflow | Suggested chain |
102|----------|-----------------|
103| Brand/client onboarding | product-marketing-context-global -> 09 -> 08 -> 31 -> 10 -> 34 |
104| Campaign launch | 02 -> 31 -> 10 -> 01/04/05/06 -> 12 -> 21 -> 07 |
105| Weekly performance | 13 -> 03/21 -> 07 -> 34 updates Brand Hub |
106| Content engine | 09 -> 01 -> 04/05/06 -> 15 -> 07 |
107 
108If previous-period data exists, read it before creating a new plan.
109 
110### 5. Set up data and second brain
111 
112Minimum stack:
113 
114- Storage: Drive/SharePoint/Dropbox for files and assets.
115- Database: Notion/Coda/Sheets for resource table, campaign archive, case studies, and decision log.
116- Analytics: Meta Ads, TikTok Ads, Google Ads, GA4, CRM, email, UTM.
117- Connector layer: MCP or equivalent connectors for knowledge base, marketing analytics, design, email, and CRM.
118 
119Every important output needs owner, date, source, version, and next action.
120 
121### 6. Create operating cadence
122 
123| Cadence | Focus | Output |
124|---------|-------|--------|
125| Daily 15m | Spend, delivery, comments/inbox, tracking issues | Blocker list |
126| Weekly 30-60m | KPI vs target, winners/losers, bottleneck, next actions | Weekly decision log |
127| Monthly | Revenue, channel mix, offer, team load, Brand Hub changes | OS retro + roadmap |
128| Quarterly | Market, positioning, offer ladder, tool stack | Strategy refresh |
129 
130### 7. Governance and risk
131 
132Check:
133 
134- Access: who can see customer data, ads data, CRM, and revenue.
135- Claims and proof: do not let AI invent proof or regulated claims.
136- Privacy: do not paste PII into unapproved tools.
137- Prompt injection: be careful with websites, comments, inbox exports, and external files.
138- Brand drift: compare new outputs against the Brand Hub.
139 
140## Output template
141 
142```markdown
143# AI Marketing OS — [Business/team]
144 
145## 1. Current diagnosis
146| Area | Level 0-4 | Evidence | Priority |
147 
148## 2. Brand Hub
149| File | Status | Owner | Update cadence |
150 
151## 3. Role workspaces
152| Role | Tool/workspace | Context loaded | Main output |
153 
154## 4. Skill chains
155| Workflow | Skill chain | Required input | Output |
156 
157## 5. Data loop and connectors
158| Data source | Tool/connector | Metric | Cadence |
159 
160## 6. Operating SOP
161| Cadence | Owner | Checklist | Output location |
162 
163## 7. 30-60-90 day roadmap
164| Phase | Work | Owner | Done when |
165 
166## 8. Risks and governance
167| Risk | Mitigation | Approver |
168```
169 
170## Related skills
171 
172- `product-marketing-context-global`: create the initial source context.
173- `00-marketing-plan-global`: create marketing plans inside the OS.
174- `02-campaign-brief-global`: convert strategy into campaign execution.
175- `07-marketing-report-global`: create the reporting layer for the data loop.
176- `13-data-analysis-global` and `21-ads-audit-global`: analyze data and find bottlenecks.
177- `31-offer-design-global`, `32-seo-growth-global`, `33-b2b-lead-gen-global`: growth modules inside the OS.
178 
179## Quality checklist
180 
181- Has a clear Brand Hub, not scattered chat context.
182- Has role workspaces and skill chains, not just a tool list.
183- Uses previous data before creating new plans.
184- Defines daily/weekly/monthly cadence and output locations.
185- Includes owners, deadlines, and approval gates for campaigns, budget, and claims.
186- Covers privacy, access, prompt injection, and brand drift.
187 

Discussion

Alternatives

/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly. · MITPath A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Creator · MIT