Skip to main content

content-calendar

Build a multi-channel content calendar for a planning period

Zur Installation springen

Quellinformationen

Repository
redhat-et/claw-collections
Letzte Quellaktivität
18. Juni 2026 um 18:55
Erkannte Sprache von SKILL.md
Englisch
Sterne
0
Forks
4

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
content-calendar
description
Build a multi-channel content calendar for a planning period
# Content Calendar Builder Build a structured content calendar to coordinate publishing across channels. ## Required inputs Ask the user for: - **Planning period** (e.g., July 2026, Q3 2026) - **Channels**: which platforms to include (blog, email, LinkedIn, X/Twitter, etc.) - **Themes or campaigns** to align content around - **Publishing cadence** per channel (e.g., blog 2x/week, email 1x/week) - **Team members** responsible for content (for the Owner column) ## Calendar structure ### Overview Summarize the period's content strategy in 2-3 sentences: themes, goals, and any key dates (product launches, events, holidays) that anchor the calendar. ### Content calendar table | Week | Date | Channel | Content Type | Topic | CTA | Owner | Status | |------|------|---------|-------------|-------|-----|-------|--------| Pre-fill Status as "Planned" for all items. ### Content types to consider - Blog posts (thought leadership, how-to, product updates) - Email newsletters and nurture sequences - Social media posts (organic and paid) - Webinars or live events - Case studies and customer stories - Infographics and visual assets ### Coordination notes - Flag content that depends on other teams (product, sales, design) and note the dependency - Mark repurposing opportunities (e.g., blog post becomes email becomes social thread) - Note any approval gates (legal review, exec sign-off) ## Output format Use a markdown table. For periods longer than one month, break into monthly sections. Include a summary row at the bottom with total pieces per channel.
Auf GitHub ansehen