Skip to main content

Social Media Content Calendar

Plan multi-platform social campaigns: briefs to posting.

Skill metadata​

SourceOptional — install with hermes skills install official/creative/social-media-content-calendar
Pathoptional-skills/creative/social-media-content-calendar
Version0.1.0
AuthorBen Barclay (benbarclay), Hermes Agent
LicenseMIT
Platformslinux, macos, windows
TagsSocial-Media, Content-Calendar, Campaigns, Publishing
Related skillsxurl, humanizer

Reference: full SKILL.md​

info

The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

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.