smithery.ai

calendar-governance

Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.

First seen Apr 8, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,413 B
  • docs SUMMARY.md 121 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.