Agent skill
calendar-governance
Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/calendar-governance
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
- Cadence Rules – define min/max posts per channel/day, quiet hours, and pacing relative to paid media.
- Coverage & Localization – ensure global timezones, languages, and partner regions have representation.
- Dependency Checks – align with product launches, events, newsletters, or PR activity to avoid clashes.
- Approval Milestones – map review deadlines backwards from publish times; include contingency buffers.
- 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?