---
name: meta-marketing-router
description: "Route Meta marketing tasks to their existing pack owner. Use for exact brand scope, prerequisites, accepted inputs and action-review handoffs."
license: AGPL-3.0-or-later
compatibility: "Claude Code, Cursor, Codex and Cowork with qualified host tools"
metadata:
  hive-tier: orchestrator
  paired-drone: none
  version: "1.0.0"
  owner: meta-foundation
---

# Meta Marketing Router

## Purpose

Route the user's concrete marketing outcome to one existing source owner, carrying exact brand identity, prerequisites, accepted inputs and the actual action boundary. This orchestrator does not create another provider executor, calculator, scheduler or credential store.

## When to use

- Route an everyday suite task to its existing specialist or standalone skill.
- Resolve missing pack, host, contract or provider prerequisites.
- Coordinate optimization recommendations with their existing execution owners.

## When not to use

- Forge or install an unavailable capability automatically.
- Choose a default profile or first platform match for a brand-sensitive task.
- Treat a proposal, broad API key, health status or local result as action approval.

## Procedure

1. Load `pest-controller-suit` first. Resolve the current source catalog, selected Core/pack prerequisites and actual available owner.
2. Read [the guide map](README.md) and [owner map](references/owner-map.md). Match the requested output rather than a superficial keyword.
3. Follow [task routing](guides/route-task.md). Arm each selected specialist with its paired skill; preserve standalone and orchestrator classifications.
4. Carry [the exact handoff terms](references/handoff-fields.md), including selected profile/account IDs, contract version/revision and evidence references. Use the shared `1.0.0`, revision `1` artifacts where applicable.
5. Follow [prerequisite resolution](guides/resolve-prerequisite.md) for unavailable owners, host features or qualified provider routes. Source/package presence does not prove installed dispatch.
6. Follow [the action boundary](guides/preserve-action-boundary.md). The Foundation provider adapter qualifies exact operations but performs no execution; missing bindings stay unverified. Preserve existing approval within its exact scope and return changed effects for review.
7. Return the artifact, actual evidence, limitations and unresolved prerequisite. Keep worker ownership exclusive; the lead coordinates parallel work and specialists do not nest additional agents.

## References map

- [Source provenance](references/source-provenance.md): current official pages and capture hashes.
- [Social Media Doctor](../social-media-doctor-stinger/SKILL.md): exact brand selection, access and per-feature readiness.
- `plugin-catalog.json` at the source/package root: canonical owner and prerequisite inventory; resolve it from the actual selected artifact.

## Critical Directive

- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
  - [social-media-doctor-stinger](../social-media-doctor-stinger/SKILL.md) - Selected identity and evidence-based capability diagnosis.

## Ship Gate

Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.