mcpField
C
channel-integration

channel-integration

github.com/gtmagentsMarketing & growth42865 installsUpdated 30w ago
Repository

About channel-integration

A marketing skill for coordinating campaigns across channels such as email, social, paid media, events, web, and PR. It provides shared planning, tracking, and escalation templates to reduce message conflicts and inconsistent measurement.

Key features

  1. 01Channel messaging matrix
  2. 02Campaign cadence planning
  3. 03Approved asset repository
  4. 04Consistent UTM and naming rules
  5. 05Channel status dashboard
  6. 06Conflict escalation path

Use cases

  1. 01Coordinating a multi-channel campaign launch
  2. 02Preventing overlapping messages or conflicting offers
  3. 03Standardizing campaign tracking across teams
  4. 04Sharing channel status and risks during launch

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill channel-integration

After installing, type/channel-integrationin Claude Code to confirm it loaded.

Details

From the project README

Channel Integration Skill

When to Use

  • Running campaigns that span email, social, paid media, events, web, PR.
  • Need to prevent message fatigue or conflicting offers.
  • Ensuring consistent tracking/UTM taxonomy across channels.

Framework

  1. Messaging Matrix – align offer, CTA, creative angle per channel/persona.
  2. Cadence Alignment – stagger sends/posts to avoid overlap; define quiet periods.
  3. Asset Repository – maintain single source of truth for approved copy/creative.
  4. Tracking Consistency – standardize UTMs, naming conventions, analytics tags.
  5. Feedback Loop – daily standup with channel owners to share insights/risks.
  6. Escalation Path – define who can approve changes when conflicts arise.

Templates

  • Channel calendar template (email, paid, social, events, partner).
  • UTM builder/validation sheet.
  • Real-time channel status dashboard (Ready, QA, Live, Blocked).
  • Message/source-of-truth sheet mapping audience × channel × CTA.

Tips

  • Use a common taxonomy for statuses (Draft, QA, Scheduled, Live) so every team reads the board the same way.
  • Hold 15-minute syncs during peak launch weeks, async updates otherwise.
  • Automate delivery of performance snapshots back to planners so adjustments happen fast.
  • Designate a single owner for conflict resolution to avoid channel tug-of-war.

Comments

Markdown supported