Back to Details

content-calendar

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Content Calendar Skill

内容日历Skill

Operator Context

操作上下文

This skill operates as an operator for editorial content pipeline management, configuring Claude's behavior for tracking blog posts through ideation, drafting, editing, and publication stages. It implements the State Machine architectural pattern -- content moves through defined stages with recorded transitions -- with Pipeline Intelligence embedded in the stage enforcement.
本Skill作为编辑内容管道管理的操作器，配置Claude的行为以跟踪博客文章从构思、撰写、编辑到发布的全流程。它采用**State Machine（状态机）架构模式——内容在预定义阶段间流转，且所有流转操作都会被记录——同时在阶段管控中嵌入了Pipeline Intelligence（管道智能）**机制。

Hardcoded Behaviors (Always Apply)

硬编码行为（始终生效）

  • CLAUDE.md Compliance: Read and follow repository CLAUDE.md before any pipeline operation
  • Over-Engineering Prevention: Only perform the requested pipeline operation. No speculative reorganization, no "while I'm here" reformatting of unrelated sections
  • Single Source of Truth: All pipeline state lives in a single 
    content-calendar.md
    file -- never store state elsewhere
  • Stage Integrity: Content moves forward through defined stages only; no skipping stages
  • Date Tracking: Every stage transition records a timestamp in YYYY-MM-DD format
  • File Preservation: Read the full calendar file before writing; never truncate or lose existing entries
  • CLAUDE.md合规性：在执行任何管道操作前，需先阅读并遵循仓库中的CLAUDE.md文件
  • 防止过度设计：仅执行用户请求的管道操作，不得进行推测性重组，不得顺带修改无关内容
  • 单一事实源：所有管道状态均存储在单个
    content-calendar.md
    文件中——不得在其他位置存储状态
  • 阶段完整性：内容仅能按预定义阶段顺序向前流转；不得跳过任何阶段
  • 日期跟踪：每次阶段流转都需记录YYYY-MM-DD格式的时间戳
  • 文件完整性：写入前需读取完整的日历文件；不得截断或丢失现有条目

Default Behaviors (ON unless disabled)

默认行为（默认开启，可关闭）

  • Visual Dashboard: Show pipeline overview with progress indicators on view
  • Upcoming Awareness: Highlight scheduled content in next 14 days
  • In-Progress Focus: Emphasize content actively being worked on (Outlined, Drafted, Editing)
  • Recent History: Show publications from last 30 days
  • Duplicate Warning: Warn when adding topics with titles matching existing entries
  • 可视化仪表盘：查看管道状态时，展示带进度指示器的管道概览
  • 近期内容提醒：高亮显示未来14天内的排期内容
  • 在办内容聚焦：重点展示当前正在处理的内容（大纲拟定、草稿撰写、内容编辑阶段）
  • 历史记录展示：显示过去30天内发布的内容
  • 重复项警告：添加与现有条目标题重复的主题时发出警告

Optional Behaviors (OFF unless enabled)

可选行为（默认关闭，可开启）

  • Stale Detection: Flag content stuck in a stage for 14+ days
  • Velocity Metrics: Show publishing rate and stage throughput statistics
  • Auto-Archive: Move published content older than current month to Historical section
  • ** stale内容检测**：标记在某一阶段停留14天以上的内容
  • 速度指标统计：展示发布频率和阶段处理效率统计数据
  • 自动归档：将早于当前月份的已发布内容移至历史记录板块

What This Skill CAN Do

本Skill可执行的操作

  • View current pipeline state across all stages with dashboard formatting
  • Add new ideas to the pipeline with duplicate detection
  • Move content between adjacent stages with timestamp recording
  • Schedule ready content for publication dates
  • Archive published content to monthly historical sections
  • Parse and update the content-calendar.md file structure
  • 以仪表盘格式查看所有阶段的当前管道状态
  • 添加新创意至管道，并检测重复项
  • 在相邻阶段间移动内容，并记录时间戳
  • 为待发布内容安排发布日期
  • 将已发布内容归档至月度历史记录板块
  • 解析并更新
    content-calendar.md
    文件结构

What This Skill CANNOT Do

本Skill不可执行的操作

  • Create or modify actual Hugo content files (use content creation skills)
  • Publish or deploy posts (use deploy skill)
  • Skip stages when moving content forward
  • Send notifications or reminders about scheduled content
  • 创建或修改实际的Hugo内容文件（请使用内容创作类Skill）
  • 发布或部署帖子（请使用部署类Skill）
  • 流转内容时跳过阶段
  • 发送排期内容的通知或提醒

Instructions

操作说明

Phase 1: READ PIPELINE

阶段1：读取管道状态

Goal: Load and validate the current calendar state before any mutation.
Step 1: Read the content calendar file from the project root
Step 2: Parse pipeline sections -- extract entries from Ideas, Outlined, Drafted, Editing, Ready, Published, and Historical sections.
Step 3: Validate file structure -- all required sections exist, counts match actual entries.
Gate: Calendar file loaded and parsed successfully. All sections accounted for. Proceed only when gate passes.
目标：在进行任何修改前，加载并验证当前日历状态。
步骤1：从项目根目录读取内容日历文件
步骤2：解析管道板块——提取创意构思、大纲拟定、草稿撰写、内容编辑、待发布、已发布和历史记录板块中的所有条目。
步骤3：验证文件结构——确保所有必填板块存在，条目数量与实际一致。
闸门：日历文件已成功加载并解析，所有板块均已识别。仅当闸门通过时才可继续。

Phase 2: EXECUTE OPERATION

阶段2：执行操作

Goal: Perform the requested pipeline operation with proper validation.
目标：在完成所有验证后执行请求的管道操作。

Operation: View Pipeline

操作：查看管道状态

  1. Count entries in each stage
  2. Identify upcoming scheduled content (next 14 days)
  3. Identify in-progress content (Outlined, Drafted, Editing)
  4. Gather recent publications (last 30 days)
  5. Display dashboard with progress indicators
  1. 统计每个阶段的条目数量
  2. 识别未来14天内的排期内容
  3. 识别当前正在处理的内容（大纲拟定、草稿撰写、内容编辑阶段）
  4. 收集过去30天内发布的内容
  5. 展示带进度指示器的仪表盘

Operation: Add Idea

操作：添加创意

  1. Validate topic name is non-empty
  2. Search all sections for duplicate titles; warn if found
  3. Append 
    - [ ] [Topic name]
    to Ideas section
  4. Update pipeline count in overview table
  1. 验证主题名称非空
  2. 搜索所有板块查找重复标题；若找到则发出警告
  3. 将
    - [ ] [主题名称]
    追加至创意构思板块
  4. 更新概览表格中的管道统计数量

Operation: Move Content

操作：移动内容

  1. Find topic in its current section (search all sections)
  2. Validate target stage is the next sequential stage:
    • Ideas -> Outlined -> Drafted -> Editing -> Ready -> Published
  3. Remove entry from current section
  4. Add to target section with timestamp metadata:
    • outlined: 
      (outline: YYYY-MM-DD)
    • drafted: 
      (draft: YYYY-MM-DD)
    • editing: 
      (editing: YYYY-MM-DD)
    • ready: 
      (ready: YYYY-MM-DD)
      -- requires scheduled publication date
    • published: 
      (published: YYYY-MM-DD)
  5. Update pipeline counts
  1. 在其当前板块中查找主题（需搜索所有板块）
  2. 验证目标阶段为当前阶段的下一个顺序阶段：
    • 创意构思 → 大纲拟定 → 草稿撰写 → 内容编辑 → 待发布 → 已发布
  3. 从当前板块移除条目
  4. 将条目添加至目标板块，并添加时间戳元数据：
    • 大纲拟定：
      (outline: YYYY-MM-DD)
    • 草稿撰写：
      (draft: YYYY-MM-DD)
    • 内容编辑：
      (editing: YYYY-MM-DD)
    • 待发布：
      (ready: YYYY-MM-DD)
      ——需附带排期发布日期
    • 已发布：
      (published: YYYY-MM-DD)
  5. 更新管道统计数量

Operation: Schedule Content

操作：排期内容

  1. Find topic (must be in Ready section)
  2. Validate date is today or future
  3. Update or add 
    Scheduled: YYYY-MM-DD
    to entry
  4. Update file
  1. 查找主题（必须处于待发布板块）
  2. 验证日期为今日或未来日期
  3. 更新或添加
    Scheduled: YYYY-MM-DD
    至条目
  4. 更新文件

Operation: Archive Published

操作：归档已发布内容

  1. Find Published entries older than current month
  2. Move to appropriate 
    ### YYYY-MM
    section in Historical
  3. Update pipeline counts
Gate: Operation executed with all validations passing. Proceed only when gate passes.
  1. 查找早于当前月份的已发布条目
  2. 将其移至历史记录板块中对应的
    ### YYYY-MM
    子板块
  3. 更新管道统计数量
闸门：操作已完成所有验证。仅当闸门通过时才可继续。

Phase 3: WRITE AND CONFIRM

阶段3：写入并确认

Goal: Persist changes and verify the write succeeded.
Step 1: Write the updated calendar file back to disk.
Step 2: Re-read the file and verify the change is present.
Step 3: Display confirmation with relevant dashboard section showing the change.
Gate: File written, re-read confirms changes persisted. Operation complete.
目标：保存修改并验证写入成功。
步骤1：将更新后的日历文件写回磁盘。
步骤2：重新读取文件并验证修改已生效。
步骤3：展示确认信息，并显示包含修改内容的相关仪表盘板块。
闸门：文件已写入，重新读取确认修改已保存。操作完成。

Error Handling

错误处理

Error: "Calendar file not found"

错误："未找到日历文件"

Cause: 
content-calendar.md
does not exist in the project Solution:
  1. Create initial calendar file with all empty sections and overview table
  2. Confirm file creation to user
  3. Proceed with requested operation
原因：项目中不存在
content-calendar.md
文件 解决方案：
  1. 创建初始日历文件，包含所有空板块和概览表格
  2. 向用户确认文件已创建
  3. 继续执行请求的操作

Error: "Topic not found in pipeline"

错误："管道中未找到该主题"

Cause: User referenced a topic name that does not match any entry Solution:
  1. Search all sections for partial matches (case-insensitive)
  2. Suggest closest matches if available
  3. Show current pipeline state so user can identify the correct title
原因：用户引用的主题名称与任何条目都不匹配 解决方案：
  1. 搜索所有板块查找部分匹配项（不区分大小写）
  2. 若存在相似匹配项则提供建议
  3. 展示当前管道状态，以便用户确认正确的标题

Error: "Invalid stage transition"

错误："无效的阶段流转"

Cause: User attempted to skip a stage (e.g., Ideas directly to Ready) Solution:
  1. Explain the required stage sequence
  2. Show the topic's current stage and the next valid stage
  3. Ask user to confirm sequential move or move to adjacent stage
原因：用户尝试跳过阶段（例如从创意构思直接移至待发布） 解决方案：
  1. 解释要求的阶段顺序
  2. 展示主题的当前阶段和下一个有效阶段
  3. 请用户确认按顺序移动或移至相邻阶段

Anti-Patterns

反模式

Anti-Pattern 1: Skipping Stages

反模式1：跳过阶段

What it looks like: Moving content directly from Ideas to Ready or Drafted to Published Why wrong: Skips essential phases of work; stage transitions represent real editorial progress Do instead: Move through each stage sequentially; each transition records that actual work occurred
表现：将内容从创意构思直接移至待发布，或从草稿撰写直接移至已发布 问题：跳过了必要的工作环节；阶段流转应反映实际的编辑进度 正确做法：按顺序逐个阶段移动内容；每次流转都记录实际完成的工作

Anti-Pattern 2: No Scheduled Dates on Ready Content

反模式2：待发布内容无排期日期

What it looks like: Content sits in Ready indefinitely without a publication date Why wrong: Pipeline clogs with "ready" items that never publish; content goes stale Do instead: Always prompt for a scheduled date when moving to Ready
表现：内容长期停留在待发布板块，未设置发布日期 问题：管道会被"已就绪"但从未发布的内容堵塞；内容会过时 正确做法：将内容移至待发布板块时，始终提示用户设置排期日期

Anti-Pattern 3: Ignoring Historical Archive

反模式3：忽略历史归档

What it looks like: Published section grows unbounded month after month Why wrong: Makes pipeline overview cluttered and dashboard counts misleading Do instead: Archive published content monthly to Historical section
表现：已发布板块随时间推移无限膨胀 问题：导致管道概览杂乱，仪表盘统计数据失真 正确做法：每月将已发布内容归档至历史记录板块

Anti-Pattern 4: Mutating Without Reading First

反模式4：未读取状态直接修改

What it looks like: Writing calendar file based on assumed state rather than reading first Why wrong: Overwrites changes made by other processes or manual edits Do instead: Always read the full file before any write operation (Phase 1 is mandatory)
表现：基于假设的状态写入日历文件，而非先读取实际状态 问题：会覆盖其他流程或手动编辑所做的修改 正确做法：执行任何写入操作前必须先读取完整文件（阶段1为强制步骤）

References

参考资料

This skill uses these shared patterns:
  • Anti-Rationalization - Prevents shortcut rationalizations
  • Verification Checklist - Pre-completion checks
本Skill使用以下共享模式：
  • 反合理化 - 防止寻找捷径的合理化借口
  • 验证清单 - 完成前的检查步骤

Domain-Specific Anti-Rationalization

领域特定反合理化

RationalizationWhy It's WrongRequired Action
"I know the current state"Memory of state ≠ actual file stateRead the calendar file first
"Skipping one stage is fine"Stage transitions track real workEnforce sequential movement
"The file format looks right"Looking ≠ verifyingRe-read after write to confirm
"No one will notice stale entries"Stale content degrades pipeline trustFlag or archive old entries
合理化借口问题所在要求的操作
"我知道当前状态"记忆中的状态 ≠ 文件实际状态先读取日历文件
"跳过一个阶段没关系"阶段流转应反映实际工作进度强制按顺序流转
"文件格式看起来没问题"视觉检查 ≠ 实际验证写入后重新读取确认
"没人会注意到过时内容"过时内容会降低管道的可信度标记或归档旧内容

Reference Files

参考文件

  • ${CLAUDE_SKILL_DIR}/references/pipeline-stages.md
    : Detailed stage definitions and transition criteria
  • ${CLAUDE_SKILL_DIR}/references/calendar-format.md
    : Complete file format specification with examples
  • ${CLAUDE_SKILL_DIR}/references/operations.md
    : Detailed command reference with edge cases
  • ${CLAUDE_SKILL_DIR}/references/pipeline-stages.md
    ：详细的阶段定义和流转标准
  • ${CLAUDE_SKILL_DIR}/references/calendar-format.md
    ：完整的文件格式规范及示例
  • ${CLAUDE_SKILL_DIR}/references/operations.md
    ：包含边缘情况的详细命令参考