跳到主要内容

social-media-content-calendar 精选

Plan multi-platform social campaigns: briefs to posting.

在 GitHub 打开

安装方式

cp -r optional-skills/creative/social-media-content-calendar ~/.claude/skills/social-media-content-calendar

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/NousResearch/hermes-agent.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 无外部命令依赖
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。

SKILL.md 正文

来源 NousResearch/hermes-agent@0b89435 · 许可 MIT · 内容未修改

Social Media Content Calendar

Plan a concrete calendar across selected social platforms. This skill owns campaign structure, post briefs, channel adaptation, approvals, and publishing verification; platform skills such as xurl own API commands. For platforms without a connector, the verified handoff ends at approved drafts for the user's scheduler — say so rather than claiming publication.

When to Use

  • "Build next month's social calendar."
  • "Turn this launch into posts for X, LinkedIn, Instagram, and TikTok."
  • "Draft and schedule a campaign."
  • "Repurpose these articles/videos into social content."

Don't use for: single one-off posts (use the platform skill directly).

Procedure

1. Define campaign constraints

Record objective, audience, offer/message, platforms, date range, cadence, voice, mandatory/prohibited claims, links, tracking convention, localization, and approval/publishing authority. Done when each proposed post has a clear business purpose.

2. Inventory source material

Collect verified product facts, launches, articles, media, testimonials with permission, brand assets, and key dates using read_file and web_extract. Mark claim owners and expiration. Done when unsupported claims and missing assets are visible.

3. Build themes and calendar slots

Create a balanced mix such as education, proof, product, community, event, behind-the-scenes, and conversation. Account for platform cadence and campaign milestones. Done when dates, platforms, themes, and objectives form a coherent calendar rather than duplicate cross-posts.

4. Write platform-specific briefs

For each post specify hook, core message, format, copy length, CTA, link, asset dimensions/content, accessibility text, tags/mentions, and success metric. Adapt rather than copy-paste between platforms. Done when a creator can produce the asset without hidden context.

5. Draft copy and assets

Load humanizer for voice; generate visuals with the image_generate tool where assets are needed. Preserve factual claims and shared campaign identity while respecting platform norms. Done when every calendar slot has draft copy and asset status.

6. Run editorial and risk review

Check factual accuracy, tone, repetition, rights/permissions, accessibility, disclosures, link destination, date relevance, and crisis sensitivity. Mark draft, needs review, or approved; do not publish from draft. Done when every post has a disposition and owner.

7. Schedule or hand off

Present the approval batch. Publish/schedule only approved posts using available platform skills (xurl for X); for platforms without a connector, deliver the approved package (copy, assets, timing) for the user's scheduling tool and mark those slots handed-off, not published. Read back scheduled time, account, content preview, and provider post/job ID for anything actually published. Done when the calendar reflects verified publishing or handoff status per slot.

Pitfalls

  • Identical copy on every platform.
  • Filling cadence with low-value repetitive posts.
  • Publishing unverified metrics, testimonials, or future claims.
  • Confusing generated asset completion with scheduled publication.
  • Claiming "scheduled" for platforms where the handoff ended at drafts.

Verification

  • [ ] Every post traces to a campaign objective and a verified claim inventory.
  • [ ] No post was published from draft or needs review state.
  • [ ] Published slots have provider-confirmed IDs; handed-off slots are marked as such.
  • [ ] Rights, permissions, and disclosures checked before any publish.

质量与来源

所属仓库
NousResearch/hermes-agent
仓库星标
25 万
最近更新
今天
采集时间
今天
commit
0b89435e7e4f
内容指纹
sha256:f12b235ea3eedf6
文件路径
optional-skills/creative/social-media-content-calendar/SKILL.md

相似 Skill

更多「编码」
access
Manage Discord channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Discord channel.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端
configure
Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do I set this up" or "who can reach me," or wants to check channel status.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端
access
Manage iMessage channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the iMessage channel.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端
configure
Check iMessage channel setup and review access policy. Use when the user asks to configure iMessage, asks "how do I set this up" or "who can reach me," or wants to know why texts aren't reaching the assistant.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端
access
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端
configure
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
精选 anthropics/claude-plugins-official 3.8 万 原文
Claude CodeMCP 客户端