Skip to content

iamwaqargulzar/Marketing-Agent-OS / overlays/marketing-os

marketing-os

Verified

Route complex marketing work across strategy, narrative, SEO/GEO, CRO, lifecycle, paid, social, influencer, launch, sales and measurement. Use for broad marketing plans, multi-channel work, or when the right specialist skill is unclear.

Marketing OS

Route the request to the smallest set of specialist skills, then return one integrated answer. Do the specialist's work through that skill's own instructions rather than from general knowledge.

How to route

  1. Read .agents/product-marketing.md when present. If it is materially incomplete and the work depends on it, start with product-marketing.
  2. Classify the request by objective, funnel stage, channel, artifact, and decision horizon.
  3. Find the narrowest match in references/skill-guide.md. Use references/skill-index.json for the complete machine-readable inventory.
  4. Load the chosen skill and follow it. If it is not installed, say which skill is missing and how to add it, then continue only with what is available.
  5. For cross-channel work, settle narrative and claims before producing publish-ready assets.
  6. Run specialists in parallel only when their inputs are independent. Otherwise sequence them by dependency.
  7. Apply references/skill-contract.md throughout. For cross-skill or side-effecting work, apply references/control-artifacts.md and keep proposal, approval, execution, receipt, and measurement separate.
  8. For high-impact deliverables, run the relevant quality gate and return one recommendation rather than disconnected expert notes.

Choosing between overlapping skills

Several families cover similar ground from different angles. Choose by the job, not the keyword.

RequestStart withNot
Full-site SEO score and prioritized reportseo-audit and its full-site workflowa single-topic specialist
One page reviewedseo-page or on-page-seo-checkerseo-audit
Crawl, indexing, rendering, or Core Web Vitalsseo-technical or technical-seo-checkerseo
Visibility in AI answers, as a strategyai-seogeo unless a full GEO audit is wanted
Full GEO audit or a client reportgeo-audit, then geo-reportai-seo
One GEO questiongeo-citability, geo-crawlers, geo-llmstxt, geo-schema, geo-brand-mentions, or geo-platform-optimizergeo-audit
Write or refresh SEO contentcontent-writercopywriting
Page copy that must convertcopywritingcontent-writer
Edit an existing draftcopy-editingcopywriting
Is a draft ready to publishcontent-quality-auditora writing skill
Conversion events not arriving or not matchingconversion-trackingattribution or ads
Which channel gets creditattribution or attribution-reconcilerconversion-tracking
Earn new linkslink-buildingoffsite-signal-analyzer
Diagnose an existing backlink profileoffsite-signal-analyzer or seo-backlinkslink-building
Plan paid campaigns or audit an accountads or ad-account-auditorad-creative
Lifecycle email programemails or email-sequence-designercold-email
Outbound to people with no prior relationshipcold-email or prospectingemails
Study how a competitor marketsreverse-engineer-marketingcompetitors for comparison pages

Routing does not authorize external actions. Stop and ask when authority is missing, a material strategic fork needs the user, evidence is insufficient, or the next step has a real-world side effect.

Output

Return the smallest useful artifact. For analysis, use Observation → Evidence → Interpretation → Recommendation → Validation. For plans, include owner or next action, metric, dependency, and risk where relevant.

Handoff

When another skill should continue the work, provide:

  • status: DONE, DONE_WITH_CONCERNS, BLOCKED, or NEEDS_INPUT
  • objective
  • findings with evidence labels
  • assumptions and open_loops
  • recommended_next_skill (maximum three)

References

  • references/skill-guide.md: every skill by domain
  • references/skill-index.json: complete catalog
  • references/skill-contract.md: evidence, permissions, and handoffs
  • references/control-artifacts.md: action lifecycle and receipts
  • references/routing-policy.md: precedence and conflict resolution
  • references/product-context-schema.md: shared marketing context
  • references/connectors.md and references/connector-catalog.md: optional data and tool integrations

The complete source library contains all four original workflows and their tooling. Use the source root specified by the specialist when a step needs its original runtime.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall