AGENT SKILL

marketing-ops

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
最近更新
2026-06-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
marketing-ops
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
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.'

02 资源文件 1

03 SKILL.md 正文

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 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 ai-seo (that's for AI search engines)
"AI search," "ChatGPT visibility," "Perplexity," "AEO" ai-seo 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

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)

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

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

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/

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.

04 同仓库更多 Skills

AdmiralGallade
AdmiralGallade/harness-repository

verify-sign

Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

template-usage

Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

sign-artifact

Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build/push; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

sei-analytics

Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

security-report

Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says "security report", "vulnerabilities", "SBOM", "security scan", "compliance check", or asks about application security.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

scorecard-review

Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.

★ 0