Approach and advantage
The routing matrix distinguishes campaign and audit requests so the assistant can hand work to the appropriate specialist. This is useful when one business goal contains several tasks that require different methods and inputs.
Organize a marketing operations workflow across campaigns, audits and specialist tasks. Give your assistant the goal, channels, owners and timeline; this Skill helps route each request to the relevant marketing Skill and maintain a local campaign tracker, making it clearer who handles the next step and which work is still pending.
Marketing Ops acts as a coordinator for a set of specialist Skills. Its routing matrix helps select the appropriate workflow, while the campaign tracker keeps the operating context available instead of scattering status across separate requests.
Use it when your assistant already has the relevant marketing Skills installed and a campaign involves several types of work. Installing this router alone does not add every specialist capability or connect advertising and email platforms. Its value is in organizing the handoffs and campaign state.
The routing matrix distinguishes campaign and audit requests so the assistant can hand work to the appropriate specialist. This is useful when one business goal contains several tasks that require different methods and inputs.
A local tracker makes campaign owners, dates and status explicit. Keep the specialist Skills available and record handoff needs in the campaign context, so the next task can continue from the current state instead of restarting the brief.
Marketing context, campaign goal, channel plan, owners, dates, and the relevant specialist Skills.
Use a Skill-capable agent with file access. Python 3 is required for the bundled Python helpers; inspect their sample schemas before supplying data.
The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.
Copy this request into Codex or Claude Code. The assistant downloads the original repository at the specified commit, installs the complete files and checks required dependencies.
Install marketing-ops in the app I am using and carry out the file installation, not just explain it.
Original repository: https://github.com/alirezarezvani/claude-skills.git
Commit: 6d2f02ea077eead1bee5411a31bcc6db5a11a70c
Skill folder: marketing-skill/skills/marketing-ops
1. Download this exact source into a new directory. Read SKILL.md and its setup references before running any bundled scripts. Do not substitute another author’s package.
2. For Codex, use ~/.agents/skills/marketing-ops; for Claude Code, use ~/.claude/skills/marketing-ops. Install only for my current app. This router requires the sibling Skills in marketing-skill/skills; install every direct child folder containing SKILL.md, and retain the repository checkout for repository-relative references. Separately distributed plugins are not automatically installed. Check all destination folders first; if any already exist, report differences before replacing them.
3. Compare the source and installed file lists and hashes. Inspect documented runtimes, dependencies and required connections. Configure only the local dependencies needed for this Skill; use an isolated environment when appropriate. Ask me to complete any account login locally, without putting credentials in chat.
4. Report the source commit, actual installation path, file-check results and any remaining runtime setup. Explain how to invoke marketing-ops in this app. Check discovery separately from file copying; start a new session if needed. Do not run production tasks or claim a successful business outcome from installation alone.This is the unchanged source SKILL.md for the reviewed version. Install the complete package to retain referenced scripts, assets, and instructions. Starter prompts below are EcomAgentTools examples.
---
name: "marketing-ops"
description: "Central router for the marketing skill ecosystem. Use when unsure which marketing skill to use, when orchestrating a multi-skill campaign, or when coordinating across content, SEO, CRO, channels, and analytics. Also use when the user mentions 'marketing help,' 'campaign plan,' 'what should I do next,' 'marketing priorities,' or 'coordinate marketing.'"
license: MIT
metadata:
version: 1.0.0
author: Alireza Rezvani
category: marketing
updated: 2026-03-06
---
# Marketing Ops
You are a senior marketing operations leader. Your goal is to route marketing questions to the right specialist skill, orchestrate multi-skill campaigns, and ensure quality across all marketing output.
## Before Starting
**Check for marketing context first:**
If `.claude/product-marketing-context.md` exists, read it. If it doesn't, recommend running the **marketing-context** skill first — everything works better with context.
## How This Skill Works
### Mode 1: Route a Question
User has a marketing question → you identify the right skill and route them.
### Mode 2: Campaign Orchestration
User wants to plan or execute a campaign → you coordinate across multiple skills in sequence.
### Mode 3: Marketing Audit
User wants to assess their marketing → you run a cross-functional audit touching SEO, content, CRO, and channels.
---
## Routing Matrix
### Content Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "Write a blog post," "content ideas," "what should I write" | **content-strategy** | Not copywriting (that's for page copy) |
| "Write copy for my homepage," "landing page copy," "headline" | **copywriting** | Not content-strategy (that's for planning) |
| "Edit this copy," "proofread," "polish this" | **copy-editing** | Not copywriting (that's for writing new) |
| "Social media post," "LinkedIn post," "tweet" | **social-content** | Not social-media-manager (that's for strategy) |
| "Marketing ideas," "brainstorm," "what else can I try" | **marketing-ideas** | |
| "Write an article," "research and write," "SEO article" | **content-production** | Not content-creator (production has the full pipeline) |
| "Sounds too robotic," "make it human," "AI watermarks" | **content-humanizer** | |
### SEO Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "SEO audit," "technical SEO," "on-page SEO" | **seo-audit** | Not aeo (that's for AI answer engines) |
| "AI search," "ChatGPT visibility," "Perplexity," "AEO" | **aeo** | Not seo-audit (that's traditional SEO) |
| "Schema markup," "structured data," "JSON-LD," "rich snippets" | **schema-markup** | |
| "Site structure," "URL structure," "navigation," "sitemap" | **site-architecture** | |
| "Programmatic SEO," "pages at scale," "template pages" | **programmatic-seo** | |
| "Local SEO," "Google Business Profile," "GBP," "NAP consistency," "Map Pack," "service area pages" | **local-seo-manager** | Not seo-audit (that's national/technical) |
### CRO Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "Optimize this page," "conversion rate," "CRO audit" | **page-cro** | Not form-cro (that's for forms specifically) |
| "Form optimization," "lead form," "contact form" | **form-cro** | Not signup-flow-cro (that's for registration) |
| "Signup flow," "registration," "account creation" | **signup-flow-cro** | Not onboarding-cro (that's post-signup) |
| "Onboarding," "activation," "first-run experience" | **onboarding-cro** | Not signup-flow-cro (that's pre-signup) |
| "Popup," "modal," "overlay," "exit intent" | **popup-cro** | |
| "Paywall," "upgrade screen," "upsell modal" | **paywall-upgrade-cro** | |
### Channels Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "Email sequence," "drip campaign," "welcome sequence" | **email-sequence** | Not cold-email (that's for outbound) |
| "Cold email," "outreach," "prospecting email" | **cold-email** | Not email-sequence (that's for lifecycle) |
| "Paid ads," "Google Ads," "Meta ads," "ad campaign" | **paid-ads** | Not ad-creative (that's for copy generation) |
| "Ad copy," "ad headlines," "ad variations," "RSA" | **ad-creative** | Not paid-ads (that's for strategy) |
| "Social media strategy," "social calendar," "community" | **social-media-manager** | Not social-content (that's for individual posts) |
| "X growth," "Twitter growth," "grow my X account" | **x-twitter-growth** | Not social-content (that's cross-platform posts) |
| "YouTube," "video SEO," "channel strategy," "thumbnails" | **youtube-full** | Not video-content-strategist (that's platform-agnostic strategy) |
| "Video strategy," "short-form video," "video content plan" | **video-content-strategist** (sibling folder `video-content-strategist/`) | Not youtube-full (that's YouTube-specific data: transcripts, search, channels) |
| "Webinar," "webinar funnel," "registration rate," "show-up rate" | **webinar-marketing** | |
| "App Store," "Play Store," "ASO," "app keywords" | **app-store-optimization** | Not seo-audit (that's web search) |
### Growth Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "A/B test," "experiment," "split test" | **ab-test-setup** | |
| "Referral program," "affiliate," "word of mouth" | **referral-program** | |
| "Free tool," "calculator," "marketing tool" | **free-tool-strategy** | |
| "Churn," "cancel flow," "dunning," "retention" | **churn-prevention** | |
### Intelligence Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "Campaign analytics," "channel performance," "attribution" | **campaign-analytics** | Not analytics-tracking (that's for setup) |
| "Set up tracking," "GA4," "GTM," "event tracking" | **analytics-tracking** | Not campaign-analytics (that's for analysis) |
| "Competitor page," "vs page," "alternative page" | **competitor-alternatives** | |
| "Psychology," "persuasion," "behavioral science" | **marketing-psychology** | |
| "Analyze my social accounts," "engagement rate," "social audit" | **social-media-analyzer** | Not social-media-manager (that's planning, not analysis) |
| "Marketing prompts," "prompt templates," "LLM governance for marketing" | **prompt-engineer-toolkit** | |
### Sales & GTM Pod
| Trigger | Route to | NOT this |
|---------|----------|----------|
| "Product launch," "feature announcement," "Product Hunt" | **launch-strategy** | |
| "Pricing," "how much to charge," "pricing tiers" | **pricing-strategy** | |
| "Positioning," "ICP," "product marketing," "messaging framework" | **marketing-strategy-pmm** | Not copywriting (that's execution) |
| "Demand gen," "lead gen program," "MQL/SQL funnel," "CRM campaigns" | **marketing-demand-acquisition** | Not paid-ads (that's one channel) |
| "Brand guidelines," "brand consistency," "style guide audit" | **brand-guidelines** | Not marketing-context (that's the foundation doc) |
### Cross-Domain (route outside marketing-skill/)
| Trigger | Route to | Domain |
|---------|----------|--------|
| "Revenue operations," "pipeline," "lead scoring" | **revenue-operations** | business-growth/ |
| "Sales deck," "pitch deck," "objection handling" | **sales-engineer** | business-growth/ |
| "Customer health," "expansion," "NPS" | **customer-success-manager** | business-growth/ |
| "Landing page code," "React component" | **landing-page-generator** | product-team/ |
| "Competitive teardown," "feature matrix" | **competitive-teardown** | product-team/ |
| "Email template code," "transactional email" | **email-template-builder** | engineering-team/ |
| "Brand strategy," "growth model," "marketing budget" | **cmo-advisor** | c-level-advisor/ |
---
## Tools
| Tool | Invocation | Output |
|---|---|---|
| Campaign tracker | `python3 scripts/campaign_tracker.py campaign.json` (no arg = embedded sample; add `--json` for machine-readable) | Per-task status, owners, deadlines, overdue flags across the skills involved in a campaign |
Use it during orchestration: after laying out a campaign sequence (below), capture each step as a task in a campaign JSON and run the tracker at every check-in — the overdue/ownerless flags feed the Quality Gate ("actions have owners and deadlines").
## Campaign Orchestration
For multi-skill campaigns, follow this sequence:
### New Product/Feature Launch
```
1. marketing-context (ensure foundation exists)
2. launch-strategy (plan the launch)
3. content-strategy (plan content around launch)
4. copywriting (write landing page)
5. email-sequence (write launch emails)
6. social-content (write social posts)
7. paid-ads + ad-creative (paid promotion)
8. analytics-tracking (set up tracking)
9. campaign-analytics (measure results)
```
### Content Campaign
```
1. content-strategy (plan topics + calendar)
2. seo-audit (identify SEO opportunities)
3. content-production (research → write → optimize)
4. content-humanizer (polish for natural voice)
5. schema-markup (add structured data)
6. social-content (promote on social)
7. email-sequence (distribute via email)
```
### Conversion Optimization Sprint
```
1. page-cro (audit current pages)
2. copywriting (rewrite underperforming copy)
3. form-cro or signup-flow-cro (optimize forms)
4. ab-test-setup (design tests)
5. analytics-tracking (ensure tracking is right)
6. campaign-analytics (measure impact)
```
---
## Quality Gate
Before any marketing output reaches the user:
- [ ] Marketing context was checked (not generic advice)
- [ ] Output follows communication standard (bottom line first)
- [ ] Actions have owners and deadlines
- [ ] Related skills referenced for next steps
- [ ] Cross-domain skills flagged when relevant
---
## Proactive Triggers
- **No marketing context exists** → "Run marketing-context first — every skill works 3x better with context."
- **Multiple skills needed** → Route to campaign orchestration mode, not just one skill.
- **Cross-domain question disguised as marketing** → Route to correct domain (e.g., "help with pricing" → pricing-strategy, not CRO).
- **Analytics not set up** → "Before optimizing, make sure tracking is in place — route to analytics-tracking first."
- **Content without SEO** → "This content should be SEO-optimized. Run seo-audit or content-production, not just copywriting."
## Output Artifacts
| When you ask for... | You get... |
|---------------------|------------|
| "What marketing skill should I use?" | Routing recommendation with skill name + why + what to expect |
| "Plan a campaign" | Campaign orchestration plan with skill sequence + timeline |
| "Marketing audit" | Cross-functional audit touching all pods with prioritized recommendations |
| "What's missing in my marketing?" | Gap analysis against full skill ecosystem |
## Communication
All output passes quality verification:
- Self-verify: routing recommendation checked against full matrix
- Output format: Bottom Line → What (with confidence) → Why → How to Act
- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
## Related Skills
- **chief-of-staff** (C-Suite): The C-level router. Marketing-ops is the domain-specific equivalent.
- **marketing-context**: Foundation — run this first if it doesn't exist.
- **cmo-advisor** (C-Suite): Strategic marketing decisions. Marketing-ops handles execution routing.
- **campaign-analytics**: For measuring outcomes of orchestrated campaigns.
Starter prompts for the main use cases—copy and use them directly.
Choose the right Skill for an SEO or copy request Use for: Choose the right Skill for an SEO or copy request. Prepare: Marketing context, campaign goal, channel plan, owners, dates, and the relevant specialist Skills.
Use the installed marketing-ops Skill. Task: Choose the right Skill for an SEO or copy request. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.[INPUT][CONSTRAINTS]Plan handoffs across a multi-channel campaign Use for: Plan handoffs across a multi-channel campaign. Prepare: Marketing context, campaign goal, channel plan, owners, dates, and the relevant specialist Skills.
Use the installed marketing-ops Skill. Task: Plan handoffs across a multi-channel campaign. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.[INPUT][CONSTRAINTS]Review campaign milestones from a local status file Use for: Review campaign milestones from a local status file. Prepare: Marketing context, campaign goal, channel plan, owners, dates, and the relevant specialist Skills.
Use the installed marketing-ops Skill. Task: Review campaign milestones from a local status file. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.[INPUT][CONSTRAINTS]The merchant needs a product page for existing email visitors, including finished copy, headline alternatives, edit rationale and review scheduling. Inputs include product context, tasks and initial wording.
Case input files: business-inputs.zip
Use the marketing-ops Skill.
Coordinate the product-page campaign in the supplied brief from drafting through editorial review and measurement handoff. Deliver the revised page, headline options, a concise editorial review and an actionable schedule with owners, dependencies and status. Keep price, care and shipping clear around the purchase CTA.
The attached business materials are:
- inputs/brief.json
- inputs/headlines.txt
- inputs/merchant.md
- inputs/requests.json
- inputs/weekly.json
Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.The primary file produced by this prompt is shown below in its original language.
Verified against the supplied fictional brief: the page now puts price, care, size and shipping beside the purchase decision. The writing and editorial deliverables are complete; tracking verification and merchant publication approval remain open. No campaign has been published.
HarborMug brings a blue insulated stainless steel mug to your daily desk setup. Check its size and care requirements before choosing your next cup.
$24 USD · One mug is $29 with US shipping, before applicable tax.
Add to cart
Hand-wash only. Not microwave safe. Dimensions: 9 × 9 × 19 cm. Weight: 0.35 kg. SKU: HM-BLUE-001.
Compare the 500 ml capacity with your usual serving and the dimensions with the space beside your keyboard or notebook. No measured heat-retention duration has been supplied, so this page makes no hours-of-warmth promise.
US orders dispatch in 2 business days. Delivery takes another 3–5 business days after dispatch. Shipping costs $5 below $50 and is free at $50 or more. International delivery is not available.
Unused items can be returned within 30 days of delivery. Final refunds require merchant approval. Contact support for return instructions before sending an item back.
Add to cart — $24 USD
Review the size, hand-wash care and $29 one-mug delivered subtotal before applicable tax.
Recommended: “A 500 ml stainless steel mug for your desk.” It identifies the product and use context without exaggeration. Alternatives: “Meet HarborMug: 500 ml, $24” for price-led email visitors; “Your 500 ml mug, with clear care and shipping details” for readers comparing purchase conditions. The supplied “Love your desk break” direction is warmer but less specific; keep it out of the main factual heading.
Seven-sweep review: clarified the product; kept a friendly direct voice; connected dimensions to a fit decision; removed unsupported proof; retained exact specifications; used the recognizable desk context; answered cost, care and return objections near the CTA. No synthetic interview sentence appears as a customer testimonial. No discount, review score, health benefit or environmental guarantee was added.
| Task | Proposed role owner | Deadline | Deliverable status | Dependency / acceptance |
|---|---|---|---|---|
| Product-page draft | Content owner | Nov 3 | Supplied draft complete; revised proposal delivered | Product facts and intended add-to-cart goal |
| Editorial review | Review owner | Nov 4 | Seven-pass proposal complete | Verify $24 + $5 = $29, care, size and policy parity |
| Measurement check | Analyst/developer | Nov 5 | Not started | Editorial freeze; validate view_item, add_to_cart and transaction deduplication |
| Merchant publication approval | Campaign owner | After measurement check | Pending | Approved copy and tracking evidence; no implementation in this exercise |
The original campaign tracker was actually run on the provided schedule and on the revised deliverable-status file. Recorded task completion moved from 1/3 (33%) to 2/3 (67%); this reflects generated deliverables, not a claim that the named merchant staff performed approvals. The tracker infers blockers from earlier deadlines, so explicit dependencies above are the business source of truth. Missing marketing pods in its generic output are not mandatory work for this narrow campaign.
The weekly order-to-session ratio is 100/4,000 = 2.5% and 120/4,800 = 2.5%. Higher sales do not prove page improvement. Preserve email source tags, validate one add-to-cart event per actual action and deduplicate purchases by transaction ID. Inspect tracking before comparing performance. Use customer questions about size, care and delivery as qualitative follow-up; no measured conversion lift is asserted.
Route the implementation handoff to analytics-tracking, then campaign-analytics once a comparable observation window exists. The completed editorial outputs are linked in the package; the remaining work has owners and observable acceptance checks.
Merchant business data is synthetic. Website observations, when present, come from the public URLs listed in the report.
The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.
Source and package files reviewed: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.
Route marketing requests and coordinate specialist workflows for campaigns and audits. A routing matrix and local campaign tracker make specialist handoffs and campaign status explicit.
Choose the method for your agent and install the complete package, not just the displayed SKILL.md. Marketing context, campaign goal, channel plan, owners, dates, and the relevant specialist Skills. Start a new agent session and explicitly ask to use marketing-ops. Try one use case below with a small sample and review the output.
Choose the right Skill for an SEO or copy request; Plan handoffs across a multi-channel campaign; Review campaign milestones from a local status file
The router depends on other marketing Skills; installing its folder alone does not provide every routed workflow or channel integration.
Source and package files reviewed: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Source and package files reviewed: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
Source and package files reviewed: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.
No reviews yet.