agentleFS
gokulsvisiongokulsvision/Crewm8-Social-Media-Manager-Skill-Graph/skills/publishing/schedule-queue/SKILL.md

schedule-queue

Skill17 starsChanged 7 months agoMITView on GitHub

Queue approved posts to scheduling tools (Buffer, Hypefury, Typefully, native schedulers) with platform-specific formatting, optimized posting times, media attachments, and cross-platform coordination.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    Check for collisions (two posts same platform within 30 min — too close)

    line 65
  2. Distinctive:

    Write alt-text for accessibility

    line 76
  3. Distinctive:

    Verify captions/subtitles embedded

    line 78
  4. Distinctive:

    Every approved post has a time slot

    line 120
  5. Distinctive:

    No platform collisions exist

    line 121
  6. Distinctive:

    All media is attached and correctly formatted

    line 122
  7. Distinctive:

    Not updating bio link before "link in bio" post goes live

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Schedule Queue

Take approved content and queue it to the right scheduling tool for the right platform at the right time. This skill bridges "content is written" and "content is live."

Purpose

The gap between content creation and publishing is where most social strategies die. This skill eliminates that gap by handling formatting, media attachment, timing optimization, and queue management — so all that's left is clicking "schedule all."

When to Use

  • Weekly batch scheduling session
  • Posts drafted and approved (passed draft-review)
  • Content calendar is locked
  • Founder approved the queue
  • Rebalancing a queue mid-week

Inputs Required

  • Approved posts per platform (text, formatted)
  • Target posting times per platform (from cadence-timing)
  • Media assets per post (images, videos, GIFs)
  • Scheduling tool (Buffer, Hypefury, Typefully, native — or any equivalent)
  • Auto-plug rules for threads
  • Bio link update schedule

Quick Reference

Scheduling ToolBest ForPlatform Support
BufferMulti-platform queue, team collaborationX, LinkedIn, IG (limited), TikTok (limited)
HypefuryX-focused with auto-plug, threadsX, LinkedIn, IG
TypefullyX threads, analytics, auto-plugX, LinkedIn
Native schedulersPlatform-specific featuresX (Media Studio), LinkedIn (native), IG (Meta Business Suite), TikTok (native)
LaterIG-first with visual planningIG, TikTok, LinkedIn, X

Procedure

  1. Gather all approved posts for the scheduling window:
    • Post text per platform
    • Target platforms
    • Recommended posting times
    • Media assets (formatted per asset-format)
    • Special rules (thread structure, auto-plug settings)
  2. Assign each post to a time slot:
    • Match cadence-timing best times
    • Check for collisions (two posts same platform within 30 min — too close)
    • Space thread tweets 1-2 minutes apart
  3. Format content per platform before queuing:
    • X: character count verified, links only in final tweet or reply
    • LinkedIn: 3-5 hashtags at end
    • IG: first 2 lines optimized, hashtags in first comment or end of caption
    • TikTok: caption short, no links
  4. Attach media assets:
    • Confirm correct dimensions
    • Write alt-text for accessibility
    • Set thumbnail for video if custom needed
    • Verify captions/subtitles embedded
  5. Set auto-plug rules:
    • Threads: add link to tweet 1 after [X likes or Y minutes]
    • Link-in-bio posts: ensure bio link is updated BEFORE post goes live
  6. Set queue management:
    • Maximum posts per day per platform to avoid fatigue
    • Fallback times if a slot is empty

Output Format

# Publishing Queue: [Week of Date]

## Queue Summary
- **Total posts:** [N] across platforms
- **Scheduling tool:** [Tool name]
- **Window:** [Date range]
- **Flex slots reserved:** [N]

## Queue by Platform

### X
| Time | Content | Type | Media | Auto-plug | Status |
|------|---------|------|-------|-----------|--------|
| Mon 9:00 AM | [Hook truncated] | Thread (8 tweets) | Image tweet 3 | Link after 20 likes | Queued |
...

### LinkedIn / Instagram / TikTok
[Same structure per platform]

## Collision Check
[Any posts within 30 min of each other?]

## Bio Link Coordination
[Posts that require bio link updates — when to update]

Done Criteria

The skill is complete when:

  1. Every approved post has a time slot
  2. No platform collisions exist
  3. All media is attached and correctly formatted
  4. Auto-plug rules are configured
  5. Bio link coordination is documented
  6. Queue is ready for the "schedule all" action

Pitfalls

  • Scheduling threads with zero spacing (unfolds as one block)
  • Forgetting to check media dimensions (queue stalls when platform rejects it)
  • Scheduling a post linking to a URL that isn't live yet
  • Not updating bio link before "link in bio" post goes live

Verification

Preview the queue in the scheduling tool's calendar view. Does the week look balanced? Does every post have media if needed? Does every thread have correct tweet spacing?

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.