MCP.Market

social-media-content-calendar skill

by NousResearch·NousResearch/hermes-agent·263k stars·MIT

Plan multi-platform social campaigns: briefs to posting.

A100/100content scan

Is the social-media-content-calendar skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-25.

No findings.

Install the social-media-content-calendar skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/NousResearch/hermes-agent.git /tmp/hermes-agent
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-agent/optional-skills/creative/social-media-content-calendar ~/.claude/skills/social-media-content-calendar
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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 readfile and webextract. 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.

More skills from NousResearch/hermes-agent

  • A1passwordSet up op CLI, sign in, and read or inject secrets.
  • A3-statement-modelBuild integrated IS/BS/CF financial workbooks in Excel.
  • AaccelerateRun PyTorch training across GPUs with minimal changes.
  • Cactual-setupSet up Actual Computer (actual.inc) inference in Hermes.
  • Aadversarial-ux-testRoleplay a hostile user to find and triage UX pain points.
  • Aagent-merge-conflict-arbiterNeutral arbiter for merge conflicts between two agents.
  • AagentmailUse when an agent needs AgentMail CLI email inboxes.
  • Aai-presenter-videoMake a verified AI presenter video from script + image.
  • AairtableAirtable REST API via curl. Records CRUD, filters, upserts.
  • AanatomyExplain an idea as an interactive isometric machine figure.
  • Cantigravity-cliOperate the Antigravity CLI (agy): plugins, auth, sandbox.
  • Aapple-notesManage Apple Notes via memo CLI: create, search, edit.

All agent skills → · MCP servers