mcpField
C
calendar-governance

calendar-governance

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

About calendar-governance

A governance framework for creating or auditing cross-network social publishing calendars, intended for content and marketing teams. It addresses cadence, regional coverage, dependencies, approvals, and change records.

Key features

  1. 01Set channel cadence and quiet hours
  2. 02Check timezone, language, and regional coverage
  3. 03Coordinate posts with launches and PR
  4. 04Schedule approval milestones with buffers
  5. 05Track calendar versions and change rationale

Use cases

  1. 01Build or audit cross-network publishing schedules
  2. 02Coordinate regional calendars and blackout dates
  3. 03Review missed posts or campaign conflicts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill calendar-governance

After installing, type/calendar-governancein Claude Code to confirm it loaded.

Details

From the project README

Social Calendar Governance Skill

When to Use

  • Building or auditing cross-network publishing schedules.
  • Coordinating regional calendars or blackout dates (events, outages, compliance windows).
  • Running retros after missed posts or conflicting campaigns.

Framework

  1. Cadence Rules – define min/max posts per channel/day, quiet hours, and pacing relative to paid media.
  2. Coverage & Localization – ensure global timezones, languages, and partner regions have representation.
  3. Dependency Checks – align with product launches, events, newsletters, or PR activity to avoid clashes.
  4. Approval Milestones – map review deadlines backwards from publish times; include contingency buffers.
  5. Audit & Change Control – maintain version history, note last-minute overrides, and capture rationale.

Templates

  • Calendar governance checklist (cadence, blackout, approvals, localization, dependencies).
  • Timezone coverage heatmap (channel × region × daypart).
  • Change-log template for late edits or cancellations.

Tips

  • Publish a weekly "calendar health" snapshot for stakeholders.
  • Pair with automation scripts that flag double-bookings or empty slots.
  • Store governance docs alongside calendars for auditability.

Comments

Markdown supported