video-content-calendar
Plan recurring video publishing schedule with themes, formats, dependencies, and review cadence.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- video-content-calendar
- tags
- [ "video", "calendar", "planning", "operations" ]
- version
- 0.1.0
- description
- Plan recurring video publishing schedule with themes, formats, dependencies, and review cadence.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md436 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Purpose
Plan recurring video publishing schedule with themes, formats, dependencies, and review cadence.
Use when
- A team needs repeatable video production cadence across weeks/months.
- You are planning schedule/ops, not producing a single script or edit plan.
Required inputs
- Publishing goals, channels, and cadence targets [client-provided].
- Brand/client context from context/BRAND-CONTEXT.template.md and context/CLIENT-CONTEXT.template.md.
- Resource capacity, campaign windows, and approval SLAs.
Safety/authority
- No fabricated forecast metrics or guaranteed growth outcomes.
- No direct scheduling/publishing actions; provide planning draft only.
- Flag capacity gaps and unknown dependencies clearly.
Workflow
- Map content pillars and format mix by channel.
- Build calendar with production lead times and approval checkpoints.
- Link each slot to required script/edit/storyboard inputs.
- Add contingency plan for delays or asset shortages.
Output format
- Video calendar summary
- Publishing grid (date | format | objective | owner | dependencies)
- Production lead-time map
- Contingency and risk notes
Quality checks
- Calendar aligns with available capacity and approval timelines.
- Each scheduled item has clear objective and prerequisite dependencies.
Related skills
video-edit-plan, short-form-video-script, social-content-ops-plan
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.