Token导航 LogoToken导航

Agent Skill · 研究检索

blog-calendar(博客日历)

blog-calendar 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

blog-calendar 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 33,694。

总安装 2,324周安装 94GitHub Stars 619下载 729核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:blog-calendar(博客日历)
来源仓库:https://github.com/agricidaniel/claude-blog
仓库路径:skills/blog-calendar
安装命令:
npx skills add https://github.com/agricidaniel/claude-blog --skill blog-calendar
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/agricidaniel/claude-blog --skill blog-calendar

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于制定周期性发布日历与话题集群规划,强化主题权威与内容新鲜度。适合媒体机构或品牌方统筹全年内容节奏与季节性热点响应。自动检测内容衰减周期,推荐重写时间与渠道适配方案。安装方式:GitHub 仓库,使用 npx skills add 命令添加;需设定发布频率及时段范围。

注意:日历建议应结合团队产能灵活调整,避免机械执行导致质量下降。

来源仓库内路径:skills/blog-calendar

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-calendar;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

blog-calendar 怎么安装?

在终端执行 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-calendar。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

blog-calendar 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

blog-calendar 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

blog-calendar 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

blog-calendar 用的人多吗?

公开数据是累计安装 2,324 次,近一周安装 94 次,下载 729 次,GitHub 619 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

blog-calendar 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
blog-calendar

博客日历 · 本页

2,324619只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Blog Calendar -- Editorial Planning

Generates editorial calendars with topic clusters, publishing cadence, freshness update schedules, content decay detection, template recommendations, distribution planning, and seasonal hooks. Optimized for building topical authority (Google) and maintaining citation freshness (AI platforms).

Workflow

Step 1: Understand the Blog

Gather context:

  1. Niche/industry -- What is the blog about?
  2. Existing content -- Scan for existing blog posts (Glob for *.md, *.mdx, *.html)
  3. Publishing cadence -- How often can they publish? (default: 2x/week)
  4. Timeframe -- Monthly or quarterly calendar?
  5. Business goals -- What should the blog drive? (traffic, leads, authority)

Step 2: Topic Cluster Design

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:

  • Target a primary keyword theme
  • Cover the topic comprehensively for topical authority
  • Include varied content types (guides, comparisons, how-tos, listicles)
  • Support internal linking between cluster pages

Step 2.5: Content Decay Detection

Scan existing blog posts for lastUpdated or date fields in frontmatter. Classify each post by staleness using these thresholds:

Traffic LevelStale ThresholdAt-Risk Threshold
High-traffic posts>30 days since update>90 days
Medium-traffic posts>90 days since update>180 days
Low-traffic posts>180 days since update>365 days

Reference: 76% of top AI citations are from content updated within 30 days.

Output a decay report:

## Content Decay Report
| Post | Last Updated | Days Stale | Priority | Action |
|------|-------------|-----------|----------|--------|
| [slug] | [date] | [N] | Critical | Refresh immediately |
| [slug] | [date] | [N] | High | Schedule this month |
| [slug] | [date] | [N] | Medium | Schedule this quarter |

Priority levels:

  • Critical: High-traffic post stale >30 days -- refresh immediately
  • High: Any post stale beyond its threshold -- schedule this month
  • Medium: Posts approaching their threshold -- schedule this quarter
  • Low: Posts within threshold -- no action needed

Step 3: Freshness Update Schedule

AI platforms heavily favor fresh content (76% of top citations updated within 30 days).

Plan update cycles:

  • High-priority posts (traffic drivers): Update every 30 days
  • Medium-priority posts: Update every 90 days
  • Low-priority posts: Update annually
  • Evergreen posts: Update when data changes

Step 4: Seasonal & Trending Hooks

Research seasonal opportunities:

  1. Industry events -- Conferences, product launches, algorithm updates
  2. Seasonal trends -- Use WebSearch to check Google Trends for the niche
  3. Annual reports -- When do major studies release new data?
  4. Algorithm updates -- Google core updates (typically 3-4 per year)
Seasonal Trends Integration
  • Map seasonal peaks to content production schedule
  • Plan content 4-6 weeks before seasonal peaks for indexing lead time
  • Create "evergreen with seasonal hook" content (e.g., "X Guide [Year]" updated annually)
  • Track industry report release cycles:

- Ahrefs Annual State of SEO (typically Q1) - Google Year in Search (December) - HubSpot State of Marketing (Q1) - Gartner Hype Cycle (August) - Major conference dates in the niche

  • Use WebSearch to validate timing of trends before scheduling

Step 5: Generate the Calendar

Content Mix Formula

Apply the recommended content mix ratio: 60% new content / 30% freshness updates / 10% repurposed content

CadenceMonthly PostsNewRefreshesRepurposed
2 posts/week8521
3 posts/week12741
4 posts/week161051
1 post/week42-310-1

Within new posts, aim for content type diversity:

  • Guides/How-tos: 30-40% of new content
  • Comparisons/Alternatives: 15-20%
  • Listicles/Roundups: 15-20%
  • Case studies/Data research: 10-15%
  • Thought leadership/News analysis: 10-15%
Template Integration

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: references/content-templates.md for full template details.

Monthly Calendar Format
# 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 Calendar Format
# 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]

Step 5.5: Topic Cluster Progress Tracking

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:

  • Clusters at 50%+ coverage: highest priority to complete
  • Clusters with published pillar but few spokes: second priority
  • New clusters: only start when existing clusters reach 75%+ coverage
  • Never have more than 3 clusters in active build-out simultaneously

Step 5.6: Distribution Scheduling

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:

  • LinkedIn: Same day as publish (share key insight + link)
  • Reddit: 2-3 days after publish (share genuine insight, not a link drop)
  • Email newsletter: Batch weekly (include 2-3 posts per newsletter)
  • YouTube: Plan companion video for pillar posts only (resource-intensive)
  • Twitter/X: Same day as publish (thread key takeaways)

Reference: references/distribution-playbook.md for detailed channel tactics.

Step 5.7: Freshness Automation

Set up a system for ongoing freshness maintenance:

## Freshness Schedule: Next 30 Days
| Post | Last Updated | Next Refresh Date | Priority | Owner |
|------|-------------|-------------------|----------|-------|
| [slug] | [date] | [date + 30] | High | [name] |
| [slug] | [date] | [date + 90] | Medium | [name] |

Automation recommendations:

  • Set calendar reminders for 30-day refresh cycles on high-traffic posts
  • List posts by "next refresh date" in ascending order (most urgent first)
  • Prioritize refresh order by traffic/importance
  • After each refresh, update the lastUpdated frontmatter field
  • Track refresh history to measure freshness impact on rankings/citations
  • Suggest running /blog rewrite for each scheduled refresh

Step 6: Save & Next Steps

Save the calendar and suggest:

  1. Start with /blog brief <first-topic> to create the first content brief
  2. Use /blog write to generate articles from briefs
  3. Use /blog rewrite for freshness updates on existing content
  4. Re-run /blog calendar next month/quarter for the next plan
  5. Review the Content Decay Report weekly and address Critical items first
  6. Track Topic Cluster Progress monthly to ensure clusters reach completion

平台分布

Codex

34.59%
按下载量换算252

Claude

31.65%
按下载量换算231

Cursor

18.53%
按下载量换算135

Gemini CLI

9.78%
按下载量换算71

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills