Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when the user needs to design, audit, upgrade, or operate an AI Marketing OS for a marketing team: Brand Hub/source of truth, role-based AI agents/projects, skill chains, ChatGPT x Claude x NotebookLM workflows, MCP/connectors, Notion/Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'marketing AI system', 'Brand Hub', 'AI workflow for marketers', 'AI team SOP', 'MCP marketing', 'marketing agent', or 'second brain marketing'.
.claude/skills/minhnv0807-34-ai-marketing-os-global/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | 104% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 96% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 108% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 43% | 0% |
| case-18 | ✗→✓ | ▲ Improved | -13% | 0% |
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.
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.
Use this skill when the user needs to:
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.
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.
Minimum Brand Hub:
When a file changes, update the relevant 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.
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.
Minimum stack:
Every important output needs owner, date, source, version, and next action.
| 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 |
Check:
markdown# 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.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-14 | fail→pass | 14,589 | 19,884 | +36% | 1 | 1 | 0% | 2,536 | 5,182 | +104% | 0 | 0 | — |
case-01 | fail→fail | 49,318 | 48,833 | -1% | 1 | 1 | 0% | 8,316 | 10,272 | +24% | 0 | 0 | — |
case-02 | fail→fail | 51,559 | 40,019 | -22% | 1 | 1 | 0% | 8,320 | 9,337 | +12% | 0 | 0 | — |
case-03 | fail→fail | 48,185 | 40,099 | -17% | 1 | 1 | 0% | 8,314 | 8,208 | -1% | 0 | 0 | — |
case-04 | fail→fail | 18,286 | 13,389 | -27% | 1 | 1 | 0% | 2,108 | 4,052 | +92% | 0 | 0 | — |
case-05 | pass→pass | 14,108 | 17,858 | +27% | 1 | 1 | 0% | 1,809 | 4,214 | +133% | 0 | 0 | — |
case-06 | pass→fail | 22,378 | 22,106 | -1% | 1 | 1 | 0% | 2,882 | 5,795 | +101% | 0 | 0 | — |
case-07 | pass→pass | 15,252 | 21,687 | +42% | 1 | 1 | 0% | 2,443 | 4,820 | +97% | 0 | 0 | — |
case-08 | fail→fail | 15,011 | 13,837 | -8% | 1 | 1 | 0% | 2,396 | 4,201 | +75% | 0 | 0 | — |
case-09 | fail→pass | 12,922 | 11,169 | -14% | 1 | 1 | 0% | 2,040 | 4,008 | +96% | 0 | 0 | — |
case-10 | fail→fail | 15,609 | 18,068 | +16% | 1 | 1 | 0% | 2,680 | 5,148 | +92% | 0 | 0 | — |
case-11 | fail→fail | 16,724 | 15,485 | -7% | 1 | 1 | 0% | 2,900 | 4,791 | +65% | 0 | 0 | — |
case-12 | fail→pass | 11,660 | 12,442 | +7% | 1 | 1 | 0% | 1,990 | 4,145 | +108% | 0 | 0 | — |
case-13 | fail→fail | 17,093 | 20,078 | +17% | 1 | 1 | 0% | 2,802 | 5,406 | +93% | 0 | 0 | — |
case-15 | pass→pass | 21,228 | 26,167 | +23% | 1 | 1 | 0% | 3,534 | 5,964 | +69% | 0 | 0 | — |
case-16 | pass→pass | 10,870 | 11,475 | +6% | 1 | 1 | 0% | 1,698 | 3,757 | +121% | 0 | 0 | — |
case-17 | fail→pass | 10,347 | 3,869 | -63% | 1 | 1 | 0% | 1,866 | 2,661 | +43% | 0 | 0 | — |
case-18 | fail→pass | 15,266 | 5,000 | -67% | 1 | 1 | 0% | 3,420 | 2,982 | -13% | 0 | 0 | — |
case-19 | fail→fail | 13,816 | 9,357 | -32% | 1 | 1 | 0% | 2,140 | 3,585 | +68% | 0 | 0 | — |
case-20 | fail→pass | 13,863 | 5,123 | -63% | 1 | 1 | 0% | 1,918 | 2,964 | +55% | 0 | 0 | — |
case-21 | fail→pass | 11,902 | 2,792 | -77% | 1 | 1 | 0% | 2,059 | 2,414 | +17% | 0 | 0 | — |
case-22 | fail→pass | 7,414 | 2,603 | -65% | 1 | 1 | 0% | 1,330 | 2,500 | +88% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +32 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.