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.
Generate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and…
$ npx skills add AgriciDaniel/claude-blog --skill blog-calendar -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-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/AgriciDaniel/claude-blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blog-calendar .claude/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .claude/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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/AgriciDaniel/claude-blog/tree/main/skills/blog-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 AgriciDaniel/claude-blog --skill blog-calendar -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-calendar --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/blog-calendar .agents/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .agents/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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 AgriciDaniel/claude-blog --skill blog-calendar -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-calendar --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/blog-calendar .cursor/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .cursor/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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/AgriciDaniel/claude-blog.git --path skills/blog-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 AgriciDaniel/claude-blog --skill blog-calendar -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-calendar --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/blog-calendar .gemini/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .gemini/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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 AgriciDaniel/claude-blog blog-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 AgriciDaniel/claude-blog --skill blog-calendar -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/blog-calendar .github/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .github/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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 AgriciDaniel/claude-blog --skill blog-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 AgriciDaniel/claude-blog blog-calendar --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/blog-calendar .opencode/skills/blog-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 "blog-calendar" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-calendar into .opencode/skills/blog-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-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.
blog-calendarGenerate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and…
Blog Calendar is an agent skill from AgriciDaniel/claude-blog. Generate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars around reader needs, evidence changes, and sustainable publishing capacity. Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Content strategy. The repository describes itself as: Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at… The licence is MIT.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 2500d4c. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blog Calendar loads about 3k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 977 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.
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.
The full file from AgriciDaniel/claude-blog at commit 2500d4c, republished under its MIT licence (© AgriciDaniel). 977 words, ~2,974 tokens.
.claude/skills/blog-calendar/SKILL.md (or your agent's skills folder).Generates editorial calendars with topic clusters, publishing cadence, material-change reviews, content-decay investigation, template recommendations, distribution planning, and seasonal hooks. It does not treat publication or update frequency as a ranking or citation signal.
This skill operates at the FLOW Find stage. Before selecting topics, run
/blog flow find for keyword discovery, content prioritization, and audience
avatar prompts that should inform cluster selection and topic sequencing.
Gather context:
Design 3-5 topic clusters (pillar + supporting content):
Cluster: [Pillar Topic]
├── Pillar Page: [Comprehensive guide - 3,000+ words]
├── Supporting: [Subtopic 1 - 2,000 words]
├── Supporting: [Subtopic 2 - 2,000 words]
├── Supporting: [Subtopic 3 - 1,500 words]
├── Comparison: [X vs Y - 1,500 words]
└── FAQ: [Common questions - 1,500 words]Each cluster should:
Scan existing posts for material change signals. Dates are inventory metadata, not proof that content is stale or fresh.
| Signal | Review Question | Priority Effect |
|---|---|---|
| Query or fact volatility | Have prices, laws, products, events, or guidance changed? | Raise when the changed fact is material |
| Performance trend | Is there a sustained decline after controlling for seasonality and Search surface? | Investigate before rewriting |
| Source availability | Are important sources outdated, contradicted, or unavailable? | Raise when claims lose support |
| Reader intent | Does the page still solve the current task? | Raise when intent materially shifted |
Do not prioritize an update solely because a frontmatter date is old or a vendor sample observed recently updated citations.
Output a decay report:
## Content Decay Report
| Post | Material Change Evidence | Performance Context | Priority | Action |
|------|--------------------------|---------------------|----------|--------|
| [slug] | [changed fact/source/intent] | [surface and comparison] | Critical | Correct material error |
| [slug] | [documented change] | [sustained trend] | High | Schedule substantive review |
| [slug] | [no confirmed change] | [stable/unclear] | Low | Monitor |Priority levels:
Plan review triggers around the topic:
Change lastUpdated only after substantive content changes.
Research seasonal opportunities:
Start from this planning heuristic, then adjust for decay risk, authority gaps, team capacity, and available source material: 60% new content / 30% freshness updates / 10% repurposed content
| Cadence | Monthly Posts | New | Refreshes | Repurposed |
|---|---|---|---|---|
| 2 posts/week | 8 | 5 | 2 | 1 |
| 3 posts/week | 12 | 7 | 4 | 1 |
| 4 posts/week | 16 | 10 | 5 | 1 |
| 1 post/week | 4 | 2-3 | 1 | 0-1 |
Within new posts, aim for content type diversity:
For each new post entry, recommend a content template from these 12 available:
how-to-guide, listicle, case-study, comparison, pillar-page,
product-review, thought-leadership, roundup, tutorial,
news-analysis, data-research, faq-knowledge
Reference: skills/blog/references/content-templates.md for full template details.
# Editorial Calendar: [Month Year]
## Publishing Cadence: [N] posts/week
## Content Mix: [N] new / [N] refreshes / [N] repurposed
### Week 1: [Date Range]
| Day | Type | Title | Template | Cluster | Target Keyword | Status |
|-----|------|-------|----------|---------|---------------|--------|
| Mon | New | [Title] | how-to-guide | [Cluster] | [keyword] | Draft |
| Thu | Update | [Existing post] | - | [Cluster] | [keyword] | Refresh |
### Week 2: [Date Range]
| Day | Type | Title | Template | Cluster | Target Keyword | Status |
|-----|------|-------|----------|---------|---------------|--------|
| Mon | New | [Title] | comparison | [Cluster] | [keyword] | Brief |
| Thu | New | [Title] | listicle | [Cluster] | [keyword] | Brief |
### Week 3: [Date Range]
[...]
### Week 4: [Date Range]
[...]
## Content Mix This Month
- New posts: [N]
- Freshness updates: [N]
- Repurposed content: [N]
- Content types: [guides, comparisons, how-tos, listicles, ...]
## Freshness Update Queue
| Post | Last Updated | Priority | Scheduled |
|------|-------------|----------|-----------|
| [slug] | [date] | High | Week 2 |
| [slug] | [date] | Medium | Week 4 |
## Seasonal Hooks
- [Event/trend and how to leverage it]# Quarterly Editorial Plan: Q[N] [Year]
## Content Strategy
- Topic clusters: [N] active
- New posts planned: [N]
- Freshness updates planned: [N]
- Repurposed content: [N]
- Total content actions: [N]
## Month 1: [Month]
### Focus: [Primary cluster or theme]
| Week | Type | Title | Template | Cluster | Keyword |
|------|------|-------|----------|---------|---------|
| W1 | New | ... | how-to-guide | ... | ... |
| W1 | Update | ... | - | ... | ... |
| W2 | New | ... | comparison | ... | ... |
[...]
## Month 2: [Month]
### Focus: [Primary cluster or theme]
[...]
## Month 3: [Month]
### Focus: [Primary cluster or theme]
[...]
## Quarterly Goals
- [ ] Publish [N] new posts
- [ ] Update [N] existing posts for freshness
- [ ] Complete [Cluster] pillar + [N] supporting pages
- [ ] Achieve [metric target]Track the build-out state of each topic cluster. Prioritize completing partially-built clusters over starting new ones.
## Topic Cluster Progress
| Cluster | Pillar | Spokes Published | Spokes Planned | Coverage |
|---------|--------|-----------------|----------------|----------|
| [Topic] | Published | 5/10 | 5 this quarter | 50% |
| [Topic] | Draft | 2/8 | 3 this quarter | 25% |
| [Topic] | Not started | 0/6 | 1 this quarter | 0% |Rules for cluster prioritization:
For each new post, plan distribution across channels. Include distribution timing in the calendar output.
## Distribution Schedule
| Post | Publish Date | LinkedIn | Reddit | Email | YouTube |
|------|-------------|----------|--------|-------|---------|
| [Title] | [Date] | Same day | +2-3 days | Next batch | If pillar |Channel timing rules:
Reference: skills/blog/references/distribution-playbook.md for detailed channel tactics.
Set up a system for ongoing freshness maintenance:
## Material-Change Review Queue
| Post | Review Trigger | Evidence | Priority | Owner |
|------|----------------|----------|----------|-------|
| [slug] | [official source/product/fact changed] | [link or observation] | High | [name] |
| [slug] | [sustained performance or intent shift] | [surface-specific comparison] | Medium | [name] |Automation recommendations:
lastUpdated only after substantive content changes/blog rewrite only when a substantive review finds work to doSave to calendars/[yyyy-mm]-editorial-calendar.md unless the user specifies
another path. Create calendars/ if it does not exist.
Suggested workflow:
/blog strategy when positioning or pillars are unclear/blog cluster plan <seed-keyword> for cluster-heavy calendars/blog brief <first-topic> or /blog outline <first-topic> for the first scheduled item/blog write to generate articles from approved briefs or outlines/blog rewrite for freshness updates on existing content/blog calendar next month/quarter for the next plan© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/blog-calendar of AgriciDaniel/claude-blog.
Open the folder on GitHubat commit 2500d4c
Blog 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 |
|---|---|---|---|---|---|---|
| Blog Calendar this skillAgriciDaniel/claude-blog | 2.3k | — | ~3k | 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 |
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.
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
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.
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.
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.
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…
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
AgriciDaniel/claude-blog
Generate audio narration of blog posts using Google Gemini TTS.
AgriciDaniel/claude-blog
FLOW framework integration for bloggers. An agent skill from AgriciDaniel/claude-blog.
AgriciDaniel/claude-blog
Query Google NotebookLM notebooks for source-grounded, citation-backed answers from user-uploaded documents.
AgriciDaniel/claude-blog
AI image generation and editing for blog content powered by Gemini via MCP.
AgriciDaniel/claude-blog
Semantic topic cluster planning and automated execution engine for claude-blog.
Categories
Generate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and…. Blog Calendar is an agent skill from AgriciDaniel/claude-blog. Generate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling.
Blog Calendar fits situations like: user says editorial calendar; content calendar; publishing schedule; what should I write.
Run `npx skills add AgriciDaniel/claude-blog --skill blog-calendar -a claude-code`. Or copy the skill folder (skills/blog-calendar in AgriciDaniel/claude-blog) into .claude/skills/blog-calendar in your project. Claude Code loads it when a task matches its description.
Run `npx skills add AgriciDaniel/claude-blog --skill blog-calendar -a codex`. Or copy the skill folder (skills/blog-calendar in AgriciDaniel/claude-blog) into .agents/skills/blog-calendar in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-blog --skill blog-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/blog-calendar, .gemini/skills/blog-calendar, .github/skills/blog-calendar and .opencode/skills/blog-calendar in your project.
SKILL.md names no scripts, command-line tools or credentials: Blog Calendar is instructions for the agent only.
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.
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.
Blog Calendar is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blog 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.
AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-blog, which has 2,348 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 9, 2026.
Source: AgriciDaniel/claude-blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.