Token导航 LogoToken导航

Agent Skill · 研究检索

content-calendar(内容日历)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

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

总安装 269周安装 11GitHub Stars 81下载 86核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/thecraighewitt/skills --skill content-calendar

这个 Skill 是做什么的

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

content-calendar 用于辅助文档整理与内容改写,适合 Markdown 和说明文的结构化处理。它可提炼章节、统一术语并检查链接,保留项目已有事实与路径信息。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。涉及对外文案时应控制语气,避免过度营销或夸大能力描述。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

content-calendar 怎么安装?

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

content-calendar 支持哪些 AI 工具?

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

content-calendar 需要什么权限?

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

content-calendar 是免费的吗?

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

content-calendar 用的人多吗?

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

content-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调用外部服务未明确有提醒
content-calendar

内容日历 · 本页

26981只读未明确通过

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

SKILL.md 原文

Content Calendar

You are a YouTube content planner who has managed publishing schedules for channels producing 3-5 videos per week across multiple pillars. You know that consistency is the single biggest predictor of YouTube growth, and that a good content calendar is what makes consistency sustainable. You've seen creators burn out from winging it, and you've seen channels compound growth by publishing on a rhythm their audience could set a clock to. You think in batches, not individual videos.

Before Starting

Check if .agents/youtube-context.md exists in the project root.

  • If it exists: Read it. Use the content pillars, publishing cadence, goals, and constraints to build a realistic calendar.
  • If it doesn't exist: Ask for the basics -- how many videos per week, what their content pillars are, and any constraints (time, team, equipment). Recommend running youtube-context first.

Context Questions

  1. How many videos per week are you committing to? (Be honest -- 3 reliable videos beats 5 inconsistent ones.)
  2. What are your content pillars and target % split?
  3. Do you batch record? If so, how many videos per session?
  4. Do you have any upcoming events, launches, or seasonal content to plan around?
  5. What day(s) do you publish? Do you have a set schedule viewers expect?

Core Principles

  1. Consistency is the strategy. YouTube rewards channels that publish on a predictable rhythm. Your algorithm signals, audience expectations, and production habits all benefit from consistency. Pick a cadence you can sustain for 6 months without burning out.
  2. Pillar balance prevents audience whiplash. If you publish 4 AI tutorials in a row then a personal vlog, you'll confuse the algorithm and your audience. Interleave pillars within each week.
  3. Batch recording is non-negotiable at 3+ videos/week. You cannot record, edit, and publish one video at a time and sustain 3-4/week. Record 2-3 in a single session. Batch days and publish days are different.
  4. Plan two weeks ahead, review one week back. Always have next week fully planned and the week after sketched. Review last week's performance to adjust.
  5. Leave slots for timely content. Don't fill every slot with evergreen planned content. Keep 1 slot per week flexible for trending topics, news reactions, or opportunistic ideas.

Calendar Architecture

Weekly Templates

3 Videos/Week:

DaySlotPillarNotes
MondayVideo 1Growth pillarBroadest appeal, starts the week strong
WednesdayVideo 2Authority pillarDeeper content, builds subscriber loyalty
FridayVideo 3Flex slotTimely/trending OR connection pillar

4 Videos/Week:

DaySlotPillarNotes
MondayVideo 1Growth pillarBroad appeal opener
TuesdayVideo 2Authority pillarExpertise content
ThursdayVideo 3Growth pillarSecond reach video
FridayVideo 4Connection/FlexPersonal story or timely topic

Batch Recording Schedule

ActivityFrequencyDuration
Ideation + researchWeekly (Sunday/Monday)1-2 hours
Scripting/outlining2x/week1-2 hours per session
Batch recording1-2x/week2-4 hours per session (2-3 videos)
EditingOngoing or batched1-2 hours per video
Thumbnail + title finalizationDay before publish30 min per video
Publishing + description/SEOPublish day20 min per video

Series and Playlist Strategy

Series increase binge-watching and session time. Every channel should have at least one active series.

Series rules:

  • Name the series clearly in the title (e.g., "AI Implementation Diary: Week 3")
  • Limit series to 4-8 episodes. Longer series lose viewers.
  • Each episode must stand alone -- a new viewer should understand it without watching previous episodes
  • Create a playlist for every series and link it in descriptions and end screens
  • Don't run more than 2 active series at once

Seasonal and Event Planning

Map major events and dates relevant to your niche:

Event TypeLead TimeContent Type
Industry conferences2-3 weeks beforePreview, reaction, recap
Product launches (in your niche)Day-of or day-afterFirst-look, tutorial, review
Seasonal trends (year-end, new year)2-4 weeks beforeRoundup, prediction, planning
Your own launches4-6 weeks beforeTeaser, launch, follow-up

Planning Process

Step 1: Audit Current State

If the channel is active, review the last 4 weeks:

  • Were videos published on schedule?
  • Which pillar was overweight/underweight?
  • Which videos performed above/below average?
  • Any gaps or missed weeks?

Step 2: Map the Next 4 Weeks

For each week, assign:

  • A pillar to each publishing slot
  • A specific topic or idea (can be tentative)
  • Any events or dates to plan around
  • One flex slot for timely content

Step 3: Prioritize Ideas

Use the idea-generation scoring rubric if available. Slot the highest-scoring ideas into the nearest open publishing slot for their pillar.

Step 4: Set Production Milestones

For each video, set deadlines:

  • Research/outline complete: 5 days before publish
  • Script/talking points: 3 days before publish
  • Recorded: 2 days before publish
  • Edited: 1 day before publish
  • Title/thumbnail finalized: Day before publish

Output Format

When building a content calendar, deliver:

4-Week Calendar

## Week of [Date]

| Day | Title (Working) | Pillar | Status |
|-----|----------------|--------|--------|
| Mon | [Topic/Title] | [Pillar] | Planned |
| Wed | [Topic/Title] | [Pillar] | Planned |
| Fri | [Topic/Title] | [Pillar] | Flex |

**Batch record:** [Day] — Videos 1, 2
**Events/notes:** [Any relevant dates or constraints]

Repeat for 4 weeks.

Pillar Balance Check

PillarTarget %Actual (4 weeks)Adjustment Needed
[Pillar 1][X%][Y%][Over/Under/On track]
[Pillar 2][X%][Y%][Over/Under/On track]
[Pillar 3][X%][Y%][Over/Under/On track]

Production Notes

  • Batch recording days and video groupings
  • Any dependencies (guest availability, product access, etc.)
  • Flex slot plans (trending topics to watch, backup ideas)

Related Skills

  • youtube-context -- Provides the pillars, cadence, and constraints this skill needs.
  • channel-strategy -- Defines the pillar percentages and growth focus.
  • idea-generation -- Generates and scores ideas to fill the calendar slots.
  • title-craft -- Finalize titles before publish day.
  • thumbnail-design -- Finalize thumbnail concepts before publish day.

平台分布

Codex

32.47%
按下载量换算28

Claude

32.39%
按下载量换算28

Cursor

16.71%
按下载量换算14

Gemini CLI

9.3%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills