Token导航 LogoToken导航

Agent Skill · 研究检索

content-calendar(内容日历)

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

content-calendar 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 6,082。

总安装 23,354周安装 954GitHub Stars 公开资料未说明下载 7,556核验 2026-05-01

安装说明

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

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

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

内容日历技能管理从创意到发布的完整内容管道,涵盖博客、邮件与社交帖子排期。支持发布节奏规划与素材复用提醒,提高团队协作效率。自动跟踪各渠道表现数据,动态调整后续内容策略方向。安装命令:openclaw skills install content-calendar,注意日历同步权限设置。

使用前应核实是否允许导出日程至外部协作工具或共享团队视图。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install content-calendar;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

content-calendar 怎么安装?

在终端执行 openclaw skills install content-calendar。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

content-calendar 支持哪些 AI 工具?

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

content-calendar 需要什么权限?

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

content-calendar 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

content-calendar 用的人多吗?

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

content-calendar 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 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

内容日历 · 本页

23,354—需要联网MIT-0通过

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

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 Ledger — theagentledger.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.*

平台分布

OpenClaw

96.22%
按下载量换算7,270

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills