Skills

Wayland Content Calendar Build

Build a 30/60/90-day content calendar mapped to funnel stages, with inferred pillar...

Install

npx skills add FerroxLabs/wayland --skill wayland-content-calendar-build -g -a claude-code -y
Repository
FerroxLabs/wayland616
Category
Engineering
Updated
4d ago
License
Apache-2.0
Context cost
Lightabout 882 tokens
Runs scripts
No, instructions only

What it does

Build a 30/60/90-day content calendar mapped to funnel stages, with inferred pillar topics, a per-channel cadence, and repurpose chains for each anchor. Use when the user wants a structured multi-step process to plan a quarter of content tied to funnel stages and topic clusters. Do NOT use for a single post or a one-off idea; use this only when the user wants a full multi-week publishing plan.

30/60/90-Day Content Calendar Builder

Estimated time: 30-45 minutes

This workflow builds a quarter of content mapped to funnel stages. It captures the brief, infers pillar topics and a per-channel cadence, lays out a 30-day plan, extends it to 60 and 90 days, and maps repurpose chains so each long-form anchor has its derivative shapes planned. Review gates sit at the 30-day plan and the final assembly.

By the end you will have: confirmed pillar topics and cadence, a 30-day plan, a 60/90-day plan, and repurpose chains for the anchors.

When to Use

  • User wants a 30/60/90-day content plan tied to funnel stages
  • User wants pillar topics and a per-channel cadence
  • User wants repurpose chains mapped to each anchor

Workflow Steps

Step 1: Capture the Brief (uses: content-calendar)

Ask the user for the offer at the top of mind, who the audience is, and which channels they publish to. Capture this brief as the basis for the calendar.

  • Input: offer, audience, channels
  • Output: confirmed calendar brief
  • Key focus: offer, audience, and channel mix

Step 2: Infer Pillar Topics (uses: content-audit)

From the brief, infer three to five pillar topics: the recurring themes the content should orbit. State the pillars and your reasoning, then let the user adjust.

  • Input: calendar brief
  • Output: three to five pillar topics with reasoning
  • Key focus: a small set of durable, recurring themes

Step 3: Recommend a Cadence (uses: content-calendar)

From the brief and the pillars, recommend a publishing cadence per channel. State the cadence and your reasoning, and ask the user to adjust for any known capacity constraints.

  • Input: brief, pillar topics
  • Output: per-channel publishing cadence
  • Key focus: a realistic cadence the user can sustain

Step 4: Build the 30-Day Plan (uses: content-calendar)

Read the whole SKILL.md on GitHub

More in Engineering