Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

content-calendar内容日历

Agent Skill

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

总安装

23,354

周安装

954

GitHub Stars

公开资料未说明

下载量

7,556
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install content-calendar

简介

内容日历技能管理从创意到发布的完整内容管道,涵盖博客、邮件与社交帖子排期。

  • 支持发布节奏规划与素材复用提醒,提高团队协作效率。
  • 自动跟踪各渠道表现数据,动态调整后续内容策略方向。
  • 安装命令:openclaw skills install content-calendar,注意日历同步权限设置。
  • 使用前应核实是否允许导出日程至外部协作工具或共享团队视图。

SKILL.md

name
content-calendar
version
1.0.0
description
Plan, schedule, and track content across channels — newsletters, social media, blog posts, and videos. Manages pipeline stages, publishing cadence, and repurposing opportunities. For solopreneurs and creators who want a system, not a spreadsheet.
tags
[content, calendar, newsletter, social-media, blog, publishing, scheduling, content-strategy, creator, solopreneur, pipeline, repurposing]
platforms
[openclaw, cursor, windsurf, generic]
category
productivity
author
The Agent Ledger
license
CC-BY-NC-4.0
url
https://github.com/theagentledger/agent-skills

Content Calendar

By The Agent Ledgertheagentledger.com

Plan, schedule, and track your content pipeline across every channel — without the spreadsheet chaos. This skill gives your agent a structured system for managing content from idea to published, and flagging what's falling behind.


What This Skill Does

Your agent will:

  • Maintain a content pipeline organized by stage (Idea → Draft → Review → Scheduled → Published)
  • Track publishing cadence per channel (newsletter, blog, LinkedIn, X, etc.)
  • Surface what needs attention — overdue pieces, gaps in the schedule, idle ideas
  • Flag repurposing opportunities — where existing content can be adapted for new channels
  • Provide a weekly content brief summarizing the next 7 days

Setup (5 Steps)

Step 1: Create your content workspace

Create a file called content/CALENDAR.md in your agent workspace. Paste this starter template:

# Content Calendar

_Last updated: [date]_

## Active Pipeline

| ID | Title | Type | Channel | Stage | Due Date | Notes |
|----|-------|------|---------|-------|----------|-------|
| C001 | | | | Idea | | |

## Publishing Cadence

| Channel | Frequency | Day/Time | Status |
|---------|-----------|----------|--------|
| Newsletter | Weekly | Thursday | Active |
| Blog | Bi-weekly | Monday | Active |
| LinkedIn | 3x/week | Mon/Wed/Fri | Active |
| X/Twitter | Daily | 9am | Active |

## Content Backlog (Unscheduled Ideas)

- [ ] [idea title] — [brief description]

## Published Archive

_Completed pieces move here after publishing._

Step 2: Define your channels

Edit the Publishing Cadence table above to match your actual channels. Remove what you don't use. Add what's missing. Be honest about cadence — if you realistically post once a week, put that.

Step 3: Tell your agent about content types

Add a note at the top of CALENDAR.md listing your content types and typical word counts or formats:

## Content Types
- **Newsletter** — ~800 words, personal tone, one main idea + links
- **Blog Post** — 1,200–2,000 words, SEO-focused, structured headers
- **LinkedIn Post** — 150–300 words, story format, one insight
- **X Thread** — 5–10 tweets, hook + value + CTA
- **YouTube Script** — 800–1,500 words, conversational

Step 4: Create the content folder structure

content/
├── CALENDAR.md          ← pipeline overview (this file)
├── ideas/               ← rough idea notes
├── drafts/              ← in-progress pieces
├── published/           ← archive of completed work
└── repurpose/           ← repurposing queue

Your agent will reference this structure when looking for content to work on.

Step 5: Activate the skill

Tell your agent:

"Read the content-calendar skill and set up my content system. Use the files in content/."

Or trigger it via heartbeat by adding to HEARTBEAT.md:

## Content Calendar (every Monday)
- Review content/CALENDAR.md
- Flag anything due this week
- Surface 2-3 backlog ideas worth developing
- Check for pieces stuck in Draft >7 days

Pipeline Stages

Each piece of content moves through these stages:

StageDescriptionTypical Duration
IdeaJust a title/concept, not startedIndefinite
OutlineStructure exists, no full draft1–3 days
DraftFull draft exists, not reviewed1–5 days
ReviewReady for final edits/approval1–2 days
ScheduledWritten, set to publish on a dateDone
PublishedLive — move to archiveArchive

Stall flag: Any piece in Draft or Review for >7 days gets flagged in status reports.


Weekly Content Brief Format

When asked for a content brief, your agent will produce:

CONTENT BRIEF — Week of [date]

PUBLISHING THIS WEEK
━━━━━━━━━━━━━━━━━━━
• [Day] — [Channel]: [Title] (Stage: Scheduled ✅)
• [Day] — [Channel]: [Title] (Stage: Draft — needs ~2h to finish ⚠️)

OVERDUE / AT RISK
━━━━━━━━━━━━━━━━
• [Title] — [Channel] — was due [date], stuck in [Stage] for [X] days
  → Recommended action: [complete / reschedule / cut]

SCHEDULE GAPS
━━━━━━━━━━━━
• [Channel] has no content scheduled for [date range]
  → Backlog options: [list 2-3 relevant ideas]

REPURPOSE OPPORTUNITIES
━━━━━━━━━━━━━━━━━━━━━━
• "[Title]" (published [date]) → could become [format] for [channel]

NEXT WEEK PREVIEW
━━━━━━━━━━━━━━━━
• [Channel]: [Title] (Stage: Outline — on track)
• [Channel]: [TBD — needs idea]

RECOMMENDED ACTION TODAY
━━━━━━━━━━━━━━━━━━━━━━━
1. [Most urgent thing]
2. [Second thing]
3. [Third thing]

Repurposing Tracker

Good content does more than one job. Tell your agent to check for repurposing opportunities by looking at anything published in the last 60 days:

Common repurposing patterns:

  • Newsletter issue → LinkedIn post (pull the main insight)
  • Blog post → X thread (break into 5-8 key points)
  • Long blog → Short blog (split into 2 pieces)
  • Video script → Blog post (light reformatting)
  • Newsletter → Blog post (add SEO metadata and headers)

To flag a piece for repurposing, add a row in content/repurpose/queue.md:

| Original | Original Channel | Repurpose As | Target Channel | Status |
|----------|-----------------|--------------|----------------|--------|
| [Title] | Newsletter | Thread | X/Twitter | Todo |

Content Idea Capture

Drop rough ideas into content/ideas/ as simple text files. Naming convention:

[topic-slug].md

Minimum viable idea note:

# [Idea Title]

**Angle:** [One sentence on the specific take]
**Channel:** [Best fit channel]
**Why now:** [Why this is relevant/timely]
**Hook:** [Draft hook if you have one]
**Related:** [Links to existing content it connects to]

Your agent can help expand ideas into outlines on request.


Customization Options

Change the stall threshold

Default is 7 days. To adjust, add to CALENDAR.md:

## Settings
- Stall threshold: 5 days
- Overdue warning: 2 days before due date

Topic clusters

Group your content by theme to ensure balanced coverage:

## Topic Clusters
- Business Systems (40%)
- AI / Automation (30%)
- Personal Productivity (20%)
- Industry News (10%)

Your agent will flag if any cluster is underrepresented over a rolling 4-week period.

Seasonal content flags

Mark pieces as time-sensitive:

| ID | Title | ... | Notes |
|----|-------|-----|-------|
| C012 | Year-end recap | ... | ⏰ SEASONAL: must publish Dec 28-30 |

Minimum viable cadence mode

If you're overwhelmed, tell your agent:

"Switch content calendar to minimum viable cadence."

It will prioritize your single highest-traffic channel and flag everything else as optional.


Integration with Other Agent Ledger Skills

SkillIntegration
Daily BriefingInclude "Content due today" in morning briefing
Project TrackerContent launches tracked as projects (e.g., "Issue #5")
Solopreneur AssistantContent calendar reviewed in weekly business review
Research AssistantResearch briefs feed directly into content ideas
Inbox TriageReader replies/feedback captured for content improvement

Troubleshooting

"My calendar is getting out of date" Add a heartbeat check. Weekly is usually right for most creators. Daily if you publish daily.

"Too many ideas, can't prioritize" Use the scoring rubric in references/advanced-patterns.md to rank ideas by effort vs. impact.

"I keep missing my publishing schedule" Run a cadence audit: count how many pieces you actually published in the last 30 days vs. how many you planned. Adjust your cadence table to match reality, not aspirations. A realistic cadence beats an optimistic one every time.

"Agent keeps forgetting what I've published" Move published pieces to content/published/ and update the archive section of CALENDAR.md. Periodically tell your agent: "Update the content archive from the published folder."

"I want to track performance metrics" This skill tracks pipeline, not analytics. For performance data, track metrics manually in a content/published/[slug]-metrics.md file and reference them in repurposing decisions.


Triggers

This skill activates when you say things like:

  • "What content do I have due this week?"
  • "Give me a content brief"
  • "What's in my content pipeline?"
  • "I have a new content idea: [idea]"
  • "What content is overdue?"
  • "What can I repurpose from last month?"
  • "Review my content calendar"

*Content Calendar — by The Agent Ledger* *Subscribe at theagentledger.com for new skills and the weekly newsletter on building AI-powered systems.* *License: CC-BY-NC-4.0*

*DISCLAIMER: This skill was created by an AI agent. It is provided "as is" for informational and educational purposes only. It does not constitute professional, financial, legal, or technical advice. Review all generated files before use. The Agent Ledger assumes no liability for outcomes resulting from use. Use at your own risk.*

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

96.22%
按下载量换算7,270

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills