Use it when your goal in communication and scheduling is clear and you can limit it to the data and actions it actually needs.
Directory → SKILL
SKILLoptionalHermes Optional Skills
Social Media Content Calendar
Plan multi-platform social campaigns: briefs to posting
Last registry verification2026-08-18v0.1.0Ben Barclay (benbarclay), Hermes Agent
What does it add to Hermes?
Plan multi-platform social campaigns: briefs to posting
Social Media Content Calendar is a skill related to communication and scheduling. It connects the agent to a communication channel or calendar. The important distinction is whether it only reads or can also send and modify.
This plain-language explanation is based on the publisher description. The original text remains visible for verification.
Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.
Best for users who want a repeatable way of working inside Hermes.
Use a test account or draft-only workflow and confirm actual sending requires explicit approval.
Original publisher description
Plan multi-platform social campaigns: briefs to posting
Data source
This entry was indexed from Hermes Optional Skills. Our explanation interprets the type and domain without inventing a capability not present upstream.
Security review
The source is official or editorially reviewed, but you still need to review permissions and version compatibility.
Inspect, install, then test.
- 01Open the source
Match the publisher, license, and description to your need. Check the real update history.
- 02Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
- 03Copy setup only after review
The controls below copy text. They do not execute commands on your device.
- 04Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.
Review the command, then copy it.
hermes skills install social-media-content-calendarHermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.
Exactly what Hermes loads when this skill runs.
Reproduced from the official documentation. Read it before enabling the skill: this text becomes the agent's instructions.
Plan multi-platform social campaigns: briefs to posting.
Skill metadata
A lookup table. Do not read it all; find the row that applies to you.
| Source | Optional — install with hermes skills install official/creative/social-media-content-calendar |
| Path | optional-skills/creative/social-media-content-calendar |
| Version | 0.1.0 |
| Author | Ben Barclay (benbarclay), Hermes Agent |
| License | MIT |
| Platforms | linux, macos, windows |
| Tags | Social-Media, Content-Calendar, Campaigns, Publishing |
| Related skills | xurl, humanizer |
Reference: full SKILL.md
Explains the idea itself. Read it slowly; the later sections build on it.
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
Explains the idea itself. Read it slowly; the later sections build on it.
- "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
Explains the idea itself. Read it slowly; the later sections build on it.
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
Explains the idea itself. Read it slowly; the later sections build on it.
- 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
Explains the idea itself. Read it slowly; the later sections build on it.
- [ ] Every post traces to a campaign objective and a verified claim inventory.
- [ ] No post was published from
draftorneeds reviewstate. - [ ] Published slots have provider-confirmed IDs; handed-off slots are marked as such.
- [ ] Rights, permissions, and disclosures checked before any publish.