agentleFS
Sign inStart free
indranilbanerjeeindranilbanerjee/digital-marketing-pro/skills/content-calendar/SKILL.md

content-calendar

Skill873 starsChanged 9 months agoMITView on GitHub

Build a content calendar: topics by platform and date, pillar and funnel tags. \"plan next month's content\"

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add SEO keyword targets to relevant content pieces

    line 33

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/digital-marketing-pro:content-calendar

Purpose

Generate a structured content calendar that maps topics to platforms, aligns with content pillars, and includes a repurposing workflow to maximize output from each core piece.

Input Required

The user must provide (or will be prompted for):

  • Time period: Month, quarter, or custom date range
  • Platforms: Which channels to plan for (blog, social, email, video, podcast)
  • Content pillars: Core themes or topics (or let the system recommend based on brand profile)
  • Publishing cadence: How often per platform (e.g., 3 blogs/month, daily social)
  • Key dates: Product launches, holidays, industry events, promotions
  • Team capacity: Who creates content and how much bandwidth exists

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Define or validate content pillars based on brand expertise and audience needs
  3. Map key dates, seasonal trends, and industry events to the calendar
  4. Generate topic ideas for each pillar, distributed across the time period
  5. Assign each topic to a primary platform and content format
  6. Build repurposing chains: blog to social snippets, video to short clips, email to blog, etc.
  7. Balance content types: educational, promotional, engagement, thought leadership
  8. Add SEO keyword targets to relevant content pieces
  9. Output the calendar in a structured, sortable format

Output

A structured content calendar containing:

  • Monthly/weekly view with publish dates and platforms
  • Topic and title for each content piece
  • Content pillar and funnel stage tags
  • Primary format and repurposing derivatives
  • Keyword targets for SEO-driven content
  • Owner/assignee column (if team info provided)
  • Repurposing workflow diagram showing content atomization paths

Agents Used

  • content-creator — Topic ideation, pillar strategy, repurposing workflows, editorial planning
  • seo-specialist — Keyword alignment, search trend timing, topic gap identification
  • social-media-manager — Platform-specific posting cadence, content format recommendations, hashtag strategy, calendar validation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free