Content Calendar Planner logo

Content Calendar Planner

Organization
Amazon-Quick
content-calendar-planner

Plans and manages content calendars for small business marketing. Creates strategic content plans across blog, social media, email, and video channels aligned to business goals. Use when user says 'plan my content', 'create a content calendar', 'what should I post this month', 'content strategy', 'editorial calendar', 'plan my blog posts', 'social media schedule', 'content ideas for [topic/month]', or 'quarterly content plan'.

Overview

PublisherAmazon-Quick
RepositoryAmazon-Quick-official-catalog
Skill namecontent-calendar-planner
Stars
50
Forks
4
Bundled files
1
LicenseMIT-0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Amazon-Quick on GitHub. Read the source before you install it.

Installation

Install the Content Calendar Planner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/marketing/content-calendar-planner
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Amazon-Quick/Amazon-Quick-official-catalog.git /tmp/Amazon-Quick-official-catalog
mkdir -p .claude/skills
cp -r /tmp/Amazon-Quick-official-catalog/skills/marketing/content-calendar-planner .claude/skills/content-calendar-planner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Content Calendar Planner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Content Calendar Planner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Content Calendar Planner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Overview

Creates practical, executable content calendars that drive traffic, build authority, and generate leads, calibrated to the business owner's actual available time. Balances SEO-driven evergreen content with timely trend-responsive posts across all relevant channels. Delivers to Google Sheets (if connected) or as an Excel spreadsheet.

Workflow

<Definition - Capacity Guide>

Hours/WeekRecommended Output
2-3 hours2 social posts/week + 1 email/month
5-8 hours4-5 social posts/week + 1 blog/week + 2 emails/month
10-15 hoursDaily social + 2 blogs/week + weekly email + monthly video
15+ hoursFull multi-channel with repurposing pipeline
</Definition - Capacity Guide>

<Definition - Content Pillar Matrix>

PillarPurposeExample TopicsFunnel Stage
ExpertiseBuild authorityHow-tos, frameworks, deep divesAwareness
StoriesBuild trustCase studies, behind-the-scenesConsideration
ProofReduce riskTestimonials, results, comparisonsDecision
CultureBuild connectionValues, mission, communityLoyalty
TrendingRide momentumIndustry news, commentaryAwareness
</Definition - Content Pillar Matrix>

<Definition - Repurposing Waterfall>

  1. Long-form blog post → Pillar piece
  2. → Email newsletter teasing key takeaways
  3. → LinkedIn post with key framework
  4. → Twitter/X thread in bite-sized insights
  5. → Instagram carousel visualizing the framework
  6. → Short video (60s) covering #1 insight
  7. → Quote graphics from best lines </Definition - Repurposing Waterfall>

<Definition - Delivery Cascade> Auto-select delivery format (do not ask):

  1. Google Sheets connected (default) → Create a "Content Calendar for [Month/Quarter]" spreadsheet in the connected sheets tool with tabs: Monthly Calendar, Content Briefs, Ideas Backlog, Performance Tracker.
  2. Google Sheets not connected → Generate Excel via run_python + open_in_session_tab.
  3. Either way → Also display this week's priorities in chat. </Definition - Delivery Cascade>

<Definition - Content Brief Template>

## Content Brief: [Title]
- **Channel:** [Platform]
- **Format:** [Post type, word count, visual needs]
- **Target audience:** [Who specifically]
- **Key message:** [1 sentence]
- **Hook:** [Opening line/visual that stops the scroll]
- **CTA:** [Specific action]
- **SEO keywords:** [If blog/YouTube]
- **Assets needed:** [Images, graphics, video clips]
- **Success metric:** [Views, clicks, signups, comments]
- **Due date:** [Creation deadline]

</Definition - Content Brief Template>

<Definition - Time Period Defaults>

  • Week plan = 5-7 posts
  • Month plan = 20-30 posts (default if unspecified)
  • Quarter plan = High-level themes with monthly breakdown </Definition - Time Period Defaults>

<Workflow - Content Calendar Planning description="Full content calendar planning workflow from audit to delivery." tools=[web_search, run_python, file_write, open_in_session_tab] triggers=["plan my content", "create a content calendar", "what should I post this month", "content strategy", "editorial calendar", "quarterly content plan", "social media schedule"]

  1. [Decide] Is sufficient context available (business_type, active channels, hours_per_week)?

    • Yes: proceed to step 3.
    • No: proceed to step 2. Validate: At minimum, business type and channels are known. If fails: Proceed to step 2.
  2. [Ask user] Gather missing context: What is your business and what do you sell? Which channels are you active on (Blog, LinkedIn, Instagram, TikTok, YouTube, Email, etc.)? How many hours per week do you have for content creation? What has worked well before? Any existing content that can be repurposed? Validate: User provides business type, active channels, and hours/week. If fails: Default to conservative plan (2-3 hours/week capacity) and note assumption.

  3. [Agent] Audit current state. Map hours_per_week to <Definition - Capacity Guide> to determine realistic output volume. Determine time_period scope per <Definition - Time Period Defaults>. Assess what the user can realistically produce. Validate: Recommended output matches available hours. Volume matches time period. If fails: Default to conservative capacity tier (2-3 hours/week).

  4. [Agent] Define 3-5 content pillars using <Definition - Content Pillar Matrix>. Use web_search to find topic ideas by searching "[target audience] questions about [topic]", customer FAQs, competitor content, and seasonal/industry events. Generate 10-20 topic ideas per pillar. Validate: Pillars cover full funnel (awareness + consideration + decision). At least 3 pillars defined. If fails: Use default pillar framework (Expertise, Stories, Proof, Culture, Trending).

  5. [Agent] Build the calendar. Create complete schedule with columns: Week, Date, Channel, Content Type, Topic/Title, Pillar, CTA, Status. Apply planning rules: alternate between pillars, front-load evergreen content, include reactive slots, match content types to platform strengths. Validate: Calendar matches capacity. Pillars alternate. Reactive slots included. Entry count matches time period. If fails: Reduce volume to match capacity. Display as markdown table.

  6. [Agent] Generate content briefs using <Definition - Content Brief Template> for each planned piece. Each brief must have enough detail to execute without additional research. Validate: Each brief has audience, key message, hook, CTA, and assets needed. If fails: Provide abbreviated briefs (title + key message + CTA only).

  7. [Agent] Build repurposing plan using <Definition - Repurposing Waterfall>. For each long-form piece (blog/pillar content), map derivative content across platforms. Validate: Each long-form piece generates 5+ derivative pieces. Each derivative is adapted to its platform (not copy-pasted). If fails: Provide repurposing suggestions for top 3 pieces only.

  8. [Agent] Deliver calendar per <Definition - Delivery Cascade>. If Google Sheets connected: create spreadsheet with tabs (Monthly Calendar, Content Briefs, Ideas Backlog, Performance Tracker). If not connected: generate Excel via run_python + open_in_session_tab. Display this week's priorities in chat regardless. Validate: All tabs/sections populated correctly. Delivery format auto-selected without asking. If fails: Deliver as markdown in chat.

</Workflow - Content Calendar Planning>

<Workflow - Content Repurposing description="Generate derivative content plan from an existing piece." tools=[web_search, run_python, file_write, open_in_session_tab] triggers=["repurpose this post", "derivative content from", "what else can I make from this"]

  1. [Decide] Did the user provide a specific existing content piece to repurpose?

    • Yes: proceed to step 2.
    • No: ask user which piece they want to repurpose. Validate: A specific content piece is identified. If fails: Ask user to share the content or link.
  2. [Agent] Apply <Definition - Repurposing Waterfall> to the provided content. Generate specific, platform-adapted derivative pieces with concrete suggestions (not generic "make a carousel"). Validate: At least 5 derivative pieces generated. Each adapted to its platform format. If fails: Generate at least 3 derivatives with specific content suggestions.

  3. [Agent] Deliver repurposing plan with timeline and brief for each derivative piece. Validate: Each derivative has a brief with format, key message, and platform-specific hook. If fails: Deliver as bullet list with title + platform + key angle.

</Workflow - Content Repurposing>

Note: For individual post creation, use social-post-creator. For blog writing, use seo-content-writer. This skill handles STRATEGY; those handle EXECUTION.

<Template - Calendar Output>

Content Calendar: [Month/Quarter] for [Business Name]

Capacity: [X] hours/week → [output level from capacity guide] Channels: [list] Pillars: [list with emoji markers]

WeekDateChannelContent TypeTopic/TitlePillarCTAStatus
.....................Planned

This Week's Priorities

  1. [Most important piece to create first]
  2. [Second priority]
  3. [Third priority] </Template - Calendar Output>

<Template - Repurposing Plan>

Repurposing Waterfall: [Original Title]

Source: [Original piece type and platform]

#DerivativePlatformKey AngleFormatDue
1Email newsletterEmailKey takeaways teaser200 words + linkDay 2
2Framework postLinkedInCore framework visualText + imageDay 3
3ThreadTwitter/XBite-sized insights5-7 tweetsDay 4
4CarouselInstagramVisual framework8-10 slidesDay 5
5Short videoTikTok/Reels#1 insight explained60 secondsDay 7
6Quote graphicsAll socialBest lines highlighted3-4 imagesDay 8
</Template - Repurposing Plan>

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Content Calendar Planner AI skill do?

Plans and manages content calendars for small business marketing. Creates strategic content plans across blog, social media, email, and video channels aligned to business goals. Use when user says 'plan my content', 'create a content calendar', 'what should I post this month', 'content strategy', 'editorial calendar', 'plan my blog posts', 'social media schedule', 'content ideas for [topic/month]', or 'quarterly content plan'.

Why use Content Calendar Planner on TypingMind?

Because you install it once and use it with any model. Content Calendar Planner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Content Calendar Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/marketing/content-calendar-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Content Calendar Planner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Content Calendar Planner?

As many as you like. As long as a model supports skills, you can use Content Calendar Planner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Content Calendar Planner AI skill free?

Yes. It is published on GitHub by Amazon-Quick under the MIT-0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇