Output format·Sales & CRM

Content Calendar

Generate a structured content calendar for any brand, product, or creator.

You say
Install this skill Read the source first Free Written by mohitagw15856 · unverified publisher
Context cost
825 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 3.3 kBtext throughout, nothing executable
Licence
MITfree to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Output format

Produces one artefact, exactly shaped.

social media
Filed under

Sales & CRM

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md3.3 kB · 67 lines
--- name: content-calendar description: "Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks." ---
6# Content Calendar Skill
7
8This skill generates a structured content calendar from brand inputs. It produces ready-to-use calendar entries with topics, formats, channels, and opening hooks — usable for social media, blogs, newsletters, or multi-channel campaigns.
9
10## Required Inputs
11
12Ask the user for these if not provided:
13- **Brand or product name**
14- **Target audience** (who are you trying to reach?)
15- **Primary content goal** (awareness / lead gen / retention / thought leadership)
16- **Channels** (e.g. LinkedIn, Instagram, newsletter, blog, X/Twitter)
17- **Cadence** (daily / 3x per week / weekly / monthly)
18- **Timeframe** (e.g. 4 weeks, Q2)
19- **Brand pillars or themes** (optional — if not provided, derive 3 from the product description)
20
21## Output Structure
22
23### 1. Content Pillars (if not provided)
24
25Derive 3–4 content pillars from the brand/product description. Each pillar = a recurring theme that anchors multiple posts. Label each one clearly (e.g. "Pillar 1: Industry Education", "Pillar 2: Product Stories").
26
27### 2. Calendar Table
28
29Produce a weekly table for each week requested. Format:
30
31| Date | Pillar | Topic | Format | Channel | Opening Hook |
32|---|---|---|---|---|---|
33| Mon 7 Apr | Education | [Topic title] | Carousel / Article / Short video / Thread | LinkedIn | [First sentence or headline of the post] |
34
35Rules:
36- Rotate through all pillars across the week — don't stack the same pillar on consecutive days
37- Match format to channel norms (e.g. carousels for Instagram, long-form for LinkedIn, threads for X)
38- Opening hooks must be specific and scroll-stopping — no generic openers like "Did you know..."
39- Flag 1–2 posts per week as "High Priority" — these are the cornerstone pieces worth boosting or repurposing
40
41### 3. Repurposing Map
42
43For each "High Priority" post, add one repurposing suggestion — e.g. "Turn this LinkedIn article into a newsletter section" or "Clip this video for an Instagram Reel."
44
45## Quality Checks
46
47- [ ] Every week has balanced pillar distribution
48- [ ] No two consecutive posts have the same format on the same channel
49- [ ] Opening hooks are specific (no generic openers)
50- [ ] Formats match platform norms
51- [ ] Repurposing map covers all High Priority posts
52
53## Anti-Patterns
54
55- [ ] Do not fill the calendar with generic topic placeholders — every entry must have a specific, usable topic and hook
56- [ ] Do not stack the same pillar or format on consecutive days — variety is required
57- [ ] Do not produce opening hooks that start with "Did you know" or other cliché openers
58- [ ] Do not ignore channel norms — formats must match the platform (no long-form threads for Instagram)
59- [ ] Do not skip the repurposing map for High Priority posts
60
61## Example Trigger Phrases
62
63- "Build me a 4-week content calendar for [brand]"
64- "Create a social media plan for [product launch]"
65- "Give me a monthly editorial calendar for my newsletter"
66- "Plan my LinkedIn content for the next month"
67
In the file
SKILL.md543 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
745
on trigger
The instruction body, read only when the skill fires.
0.41%
of a 200k window
Ten skills this size would take about 4% of the window before you open a file.
050k100k150k200k context window

825 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 3.3 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md3.3 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Content Calendar · 825 tokens when loaded npx mcprush@latest skill add mohitagw15856/content-calendar

Writes to .claude/skills/content-calendar/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencemohitagw15856/content-calendar

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

MO
mohitagw15856

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill