playbooks

home / skills / gtmagents / gtm-agents / calendar-governance

calendar-governance skill

/plugins/social-scheduler-orchestration/skills/calendar-governance

This skill enforces social calendar cadence, timezone coverage, and approvals to prevent clashes and ensure global coverage.

npx playbooks add skill gtmagents/gtm-agents --skill calendar-governance

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.4 KB
---
name: calendar-governance
description: Use to enforce cadence rules, timezone coverage, and operational controls
  on social calendars.
---

# 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.

---

Overview

This skill enforces cadence rules, timezone coverage, and operational controls on social calendars. It helps teams prevent conflicts, ensure global representation, and maintain audit-ready change control for publishing schedules. Use it to standardize governance across channels and regions.

How this skill works

The skill inspects calendar entries, channel-level cadence settings, and regional timezones to identify gaps and conflicts. It applies configurable rules for minimum/maximum posts, quiet hours, dependencies with launches or PR, and approval milestones. It also produces governance artifacts like coverage heatmaps and change logs for audits and stakeholder communication.

When to use it

  • Building or auditing cross-network publishing schedules
  • Coordinating regional calendars, blackout dates, or compliance windows
  • Validating calendar alignment with product launches, events, or paid campaigns
  • Running retros after missed posts or conflicting campaigns
  • Preparing weekly stakeholder calendar health reports

Best practices

  • Define clear cadence rules per channel: min/max posts, pacing, and quiet hours
  • Map approval deadlines backward from publish times and include contingency buffers
  • Maintain timezone coverage matrices to ensure regional representation across dayparts
  • Automate checks for double-bookings and empty slots and flag them to owners
  • Keep governance docs and change logs stored next to calendars for auditability

Example use cases

  • Run a pre-week validation that flags channels exceeding daily post limits or missing minimums
  • Generate a timezone coverage heatmap to confirm global language and partner representation
  • Block publishing during blackout dates for outages or compliance windows
  • Enforce dependency checks to prevent social posts from conflicting with product launch or PR events
  • Capture late edits and cancellations in a structured change-log for post-mortem reviews

FAQ

Can this skill detect conflicts across different social platforms?

Yes. It checks calendar entries and channel rules to surface double-bookings, overlapping campaigns, and pacing issues across platforms.

How does it handle global timezone coverage?

It produces a timezone coverage heatmap and can validate that each region and daypart has assigned content or flag gaps for follow-up.