agentleFS
namddpnamddp/social-media-agent-skills/skills/social-content-calendar/SKILL.md

social-content-calendar

Skill0 starsChanged 3 months agoMITView on GitHub

Build a sustainable seven-day social plan from verified source material and realistic production capacity.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a small, executable calendar that balances teaching, proof, conversation, and promotion.

    line 10
  2. Distinctive:

    Add draft, review, and approval deadlines separately from publish targets.

    line 25
  3. Distinctive:

    Every item has a source and a distinct content role.

    line 40
  4. Distinctive:

    Do not schedule content or access account calendars.

    line 47
  5. Distinctive:

    Never treat a tentative date as approved publication.

    line 48
  6. Distinctive:

    Keep private launch dates and campaign details out of public examples.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Content Calendar

Purpose

Create a small, executable calendar that balances teaching, proof, conversation, and promotion.

Inputs

  • Approved source briefs and repurposing maps
  • Voice card, selected platforms, and campaign objective
  • Publishing capacity, approval owner, and blackout dates

Workflow

  1. Set one weekly objective and one measurable leading signal.
  2. Inventory approved facts and reusable assets.
  3. Assign content roles: teach, show, explain, invite, or promote.
  4. Limit the calendar to the team's real production capacity.
  5. Sequence reused ideas with enough distance and a different reader value.
  6. Add draft, review, and approval deadlines separately from publish targets.
  7. Mark dependencies and missing evidence.

Output

# Seven-day content calendar
| Day | Platform | Content role | Angle | Format | Source | Owner | Status |
## Reuse map
## Production checklist
## Measurement note

Quality gate

  • Every item has a source and a distinct content role.
  • The week is achievable with the stated people and assets.
  • Promotional items do not overwhelm useful content.
  • Approval is a visible state, not an assumption.

Safety

  • Do not schedule content or access account calendars.
  • Never treat a tentative date as approved publication.
  • Keep private launch dates and campaign details out of public examples.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.