Skip to main content
Generalgtmagents

calendar-governance

Use to enforce cadence rules, timezone coverage, and operational controls

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--calendar-governance
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/social-scheduler-orchestration/skills/calendar-governance/SKILL.md -o .claude/skills/calendar-governance.md

Drops the SKILL.md into .claude/skills/calendar-governance.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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.