Blogger Distiller
otter1101/blogger-distiller
A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.
A skill your agent uses to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from…
Install Content Calendar
$ npx skills add social-media-skills/skills --skill content-calendar -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install social-media-skills/skills content-calendar --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-calendar .claude/skills/content-calendar && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .claude/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/social-media-skills/skills/tree/main/skills/content-calendarType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add social-media-skills/skills --skill content-calendar -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install social-media-skills/skills content-calendar --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-calendar .agents/skills/content-calendar && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .agents/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill content-calendar -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install social-media-skills/skills content-calendar --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-calendar .cursor/skills/content-calendar && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .cursor/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/social-media-skills/skills.git --path skills/content-calendar--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add social-media-skills/skills --skill content-calendar -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install social-media-skills/skills content-calendar --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-calendar .gemini/skills/content-calendar && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .gemini/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install social-media-skills/skills content-calendarInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add social-media-skills/skills --skill content-calendar -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-calendar .github/skills/content-calendar && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .github/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill content-calendar -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install social-media-skills/skills content-calendar --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-calendar .opencode/skills/content-calendar && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-calendar" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/content-calendar into .opencode/skills/content-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-calendar", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-calendar- GitHub stars
- 134
- Token cost
- ~1.6k tokens
- SKILL.md length
- 677 words
- Files
- 6 (incl. references)
- Skills in repo
- 106
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from…
- Works in 7 steps: Read the foundation first → Size the cadence to real capacity → Build the recurring skeleton → …
- Build a content calendar — a sustainable
- SKILL.md covers Step 0 — Read the foundation…, Step 1 — Size the cadence to…, Step 2 — Build the recurring… and Step 3 — Design one or two…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Calendar is an agent skill from social-media-skills/skills. Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars. Run when the user says "content calendar," "editorial calendar," "social media calendar," "posting schedule," "content plan" (ongoing), "what should I post each week," "build me a posting routine/cadence," or wants a repeatable system rather than one period's posts. Reads social-strategy, content-pillars, and…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/cadence-and-capacity.md` and `references/calendar-structure.md`).
It sits in Writing & Content, covering Content strategy. The repository describes itself as: 106 social media skills for AI agents - strategy, writing, video, design, platform growth, publishing, and analytics. Works with Claude, Cursor, OpenClaw, Hermes & 40+ agents. The licence is MIT.
When your agent uses it
- Build a content calendar — a sustainable
- Repeatable posting rhythm and recurring structure (which pillars/formats post on which days
- On which platforms)
- Derived from strategy and pillars
Example prompts
- “content calendar,”
- “editorial calendar,”
- “social media calendar,”
- “/content-calendar”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6e30eeb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Calendar loads about 1.6k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 247 tokens; SKILL.md has 677 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from social-media-skills/skills at commit 6e30eeb, republished under its MIT licence (© social-media-skills). 677 words, ~1,623 tokens.
Download SKILL.mdSave it as
.claude/skills/content-calendar/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- content-calendar
- description
- Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars. Run when the user says "content calendar," "editorial calendar," "social media calendar," "posting schedule," "content plan" (ongoing), "what should I post each week," "build me a posting routine/cadence," or wants a repeatable system rather than one period's posts. Reads social-strategy, content-pillars, and brand-profile first; sizes cadence to real capacity; builds a recurring skeleton of buckets and named series with room reserved for reactive/trend content; sets the planning rhythm (batch, buffer, review). Hands a period's briefs to batch-content-plan, content to the writing skills, and scheduling to scheduling-and-queue. For filling one specific week/month with actual posts use batch-content-plan; for higher-level channel/goal choices use social-strategy.
- metadata.version
- 1.0.0
- license
- MIT
Content Calendar
A content calendar isn't a blank grid you fill by heroics — it's a sustainable operating rhythm: a recurring structure that generates posts so you're never staring at an empty page, at a cadence you can actually hold. Two ideas drive everything here:
- Cadence equals capacity. The number-one reason calendars fail is overcommitting. A sustainable floor you keep for a year beats an ambitious plan abandoned in February.
- A recurring skeleton beats a blank page. Define repeatable buckets (pillar × format × slot) and a couple of named series — then each cycle is fill-in-the-blanks, not invent-from-scratch.
This skill owns the recurring system. Filling a specific week/month with actual posts is
batch-content-plan; the higher-level channel/goal choices are social-strategy. This sits
between them: strategy + pillars → the repeatable rhythm → (per cycle) batch-content-plan →
content skills → scheduler.
Step 0 — Read the foundation first
Load social-strategy.md, content-pillars.md, and brand-profile.md. If pillars don't exist,
route to content-pillars or derive lightweight provisional ones — the calendar must map to themes,
not float free.
Step 1 — Size the cadence to real capacity
Estimate honest capacity (time, people, budget, the bad-week floor) and set a sustainable cadence
per platform — different per platform, not one number everywhere. Pick one or two primary
platforms to do well. Use repurposing to cover more without proportionally more work. See
references/cadence-and-capacity.md.
Step 2 — Build the recurring skeleton
Map buckets — pillar × format × slot/day/platform — so each slot is a standing instruction, not
a fixed post. Distribute across pillars (signature pillar gets prime slots) and vary formats by
design. See references/calendar-structure.md.
Step 3 — Design one or two recurring series
Add a named franchise in a fixed slot ("Teardown Tuesday," "Build Log") for anticipation, less decision fatigue, and recognition. One or two — not every slot.
Step 4 — Anchor dates + reserve reactive room
Layer time-bound anchors (launches, relevant events) onto the skeleton, and reserve ~20–30% for
reactive/timely content with one or two open slots a week (hand live trend research to
trend-jacking). Structure for consistency; reactive room for relevance.
Step 5 — Set the operating rhythm
Define the workflow that sustains it: a planning ritual (monthly shape, weekly fill, daily
engage), batch creation, and a buffer/queue so a bad week doesn't break the streak. Assign
roles if a team. See references/operating-rhythm.md.
Step 6 — Deliver + hand off
Output the cadence + recurring skeleton + series + planned/reactive split + anchors, plus a filled sample week to make it concrete. Then:
- Fill a specific period →
batch-content-plan. - Write each piece → the content skills; adapt across platforms →
cross-platform-repurposing. - Schedule →
scheduling-and-queue(into the buffer).
Show full SKILL.md (263 more words)Show less
Quality bar — self-check
- Is the cadence sized to capacity (the floor, not the ceiling), and per-platform?
- Is there a recurring skeleton of buckets (pillar × format × slot), not a one-off list?
- Are there one or two named series?
- Is reactive room reserved (~20–30%) alongside sensible anchors?
- Is there a planning rhythm + buffer, not just a grid?
- Are hand-offs to batch-content-plan / content skills / scheduler clear?
- Is multi-platform made feasible by repurposing, with no analytics claims?
Edge cases & pushback
- Overcommitting ("5×/day on 6 platforms solo") → right-size hard to a sustainable floor; explain why; use repurposing.
- Too rigid ("lock 90 days, no gaps") → reserve reactive slots; a fully-locked calendar can't ride trends.
- "Just give me 20 post ideas" → that's
batch-content-plan; offer the recurring skeleton here. - "Build it around our best times/top performers" → WoopSocial has no analytics; offer native data the user pulls or qualitative review; don't claim data-driven optimization.
- No pillars/strategy yet → route to
content-pillars/social-strategyor derive provisional pillars; don't float free. - Keeps abandoning schedules → fix the rhythm (sustainable floor + buffer + ritual), not just the grid.
Related skills
social-strategy— the channel/goal choices above this.content-pillars— the themes the skeleton maps to;brand-profile,voice-builder.batch-content-plan— fills a specific period with briefs (the per-cycle execution).cross-platform-repurposing— makes multi-platform sustainable.- content skills (
caption-writer,reels-script,tiktok-script,carousel-writer,thread-writer,linkedin-post-writer) — write each slot. trend-jacking— the reactive slots;scheduling-and-queue— ship into the buffer.
References
references/cadence-and-capacity.md— sizing cadence to capacity; per-platform norms; repurposing; buffer.references/calendar-structure.md— buckets, pillar × format × slot, series, planned/reactive, anchors.references/operating-rhythm.md— the planning ritual, batching, buffer, honest review, hand-offs.references/examples.md— worked calendars (solo + team) with sample weeks, vs an over-ambitious one.
© social-media-skills, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/content-calendar of social-media-skills/skills.
- SKILL.md
- evals/evals.json
- references/cadence-and-capacity.md
- references/calendar-structure.md
- references/examples.md
- references/operating-rhythm.md
Open the folder on GitHubat commit 6e30eeb
Compare with similar skills
Content Calendar next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Calendar this skillsocial-media-skills/skills | 134 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 701 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None | |
| Brand Voice Content Creatordavila7/claude-code-templates | 33k | 3 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
WeChat Hot Article Analysis
SpaceZephyr/creator-buddy
Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
Ralph Copywriter
muratcankoylan/ralph-wiggum-marketer
A skill your agent uses when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand…
More from social-media-skills/skills
All 106 skills in this repoAI Image Editing
social-media-skills/skills
The AI image-editing router — inpainting/object removal, background removal, upscaling, outpainting, old-photo restoration, and retouch, routed task-first to the right engine.
AI Music And Sound
social-media-skills/skills
The AI music + sound-design skill for social -- original/licensed audio beds and sound design for Reels/TikToks/Shorts/videos.
AI Search Optimization
social-media-skills/skills
A skill your agent uses to get a brand and its content CITED and RECOMMENDED by AI answer engines — the GEO (Generative Engine Optimization) / AI-search-visibility skill.
AI Video
social-media-skills/skills
The model-agnostic AI-video router and brief — the counterpart to image-prompt.
AI Voiceover
social-media-skills/skills
The AI narration / voiceover mini-skill (ElevenLabs-led). An agent skill from social-media-skills/skills.
Analytics And Reporting
social-media-skills/skills
Social media analytics and reporting — read native platform data honestly and turn it into next actions.
Related
Categories
Questions about Content Calendar
What does Content Calendar do?
A skill your agent uses to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from…. Content Calendar is an agent skill from social-media-skills/skills. Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars.
When should I use Content Calendar?
Content Calendar fits situations like: build a content calendar — a sustainable; repeatable posting rhythm and recurring structure (which pillars/formats post on which days; on which platforms); derived from strategy and pillars.
How do I install Content Calendar in Claude Code?
Run `npx skills add social-media-skills/skills --skill content-calendar -a claude-code`. Or copy the skill folder (skills/content-calendar in social-media-skills/skills) into .claude/skills/content-calendar in your project. Claude Code loads it when a task matches its description.
How do I install Content Calendar in Codex?
Run `npx skills add social-media-skills/skills --skill content-calendar -a codex`. Or copy the skill folder (skills/content-calendar in social-media-skills/skills) into .agents/skills/content-calendar in your project. Codex loads it when a task matches its description.
Can I use Content Calendar in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add social-media-skills/skills --skill content-calendar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-calendar, .gemini/skills/content-calendar, .github/skills/content-calendar and .opencode/skills/content-calendar in your project.
What does Content Calendar need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Calendar is instructions for the agent only.
Does Content Calendar access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Content Calendar safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Calendar use?
Content Calendar is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Calendar use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Content Calendar?
Skills that share tags, products or a category with Content Calendar: Blogger Distiller (otter1101/blogger-distiller, 701 stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars) and WeChat Hot Article Analysis (SpaceZephyr/creator-buddy, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Calendar?
social-media-skills (a GitHub organization) maintains it in social-media-skills/skills, which has 134 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on October 1, 2026.
Source: social-media-skills/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.