EpistatesEpistates/sparX/.claude/skills/schedule/SKILL.md

schedule

Skill3 starsChanged 7 months agoMITView on GitHub

Get optimal posting times and schedule content for X. Use when the user asks when to post, wants scheduling advice, or wants to queue up content at optimal times.

We split this skill into the rules it gives an agent

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

0
Common
Most of the 31 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read ../../../reference/timing.md for the complete timing reference.
line 22
Distinctive:
Consider the day of week
line 38
Distinctive:
If OpenTweet MCP is available:
line 66
Very specific:
Use opentweet_batch_schedule for weekly plans
line 68
Distinctive:
Avoid weekends unless the audience is consumer/hobby
line 82
Distinctive:
Never schedule without a reply plan — posting and disappearing wastes the first-hour window
line 83
Distinctive:
If user can't be available to reply, schedule for the next available window where they can be present
line 84

“Common” is measured: kept by at least 6 in 10 of the 31 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

Intelligent Posting Schedule

Provide data-driven posting time recommendations and help schedule content for maximum first-hour engagement velocity.

Input

The user may ask:

"When should I post this?"
"Build me a weekly posting schedule"
"What's the best time for [content type] aimed at [audience]?"
Or provide content ready to schedule

Process

Step 1 — Load Timing Data

Read ../../../reference/timing.md for the complete timing reference.

Step 2 — Gather Context

Determine:

Content type: Post, thread, poll, announcement, etc.
Target audience: Developers, general tech, consumers, specific niche
Author's timezone: For converting recommendations
Posting history: Any known patterns or constraints
Urgency: Time-sensitive content vs. evergreen

Step 3 — Generate Recommendation

For a single post:

Recommend the top 3 posting windows with rationale
Account for content type × timing matrix
Consider the day of week
Note: "Be available to reply for 30-60 min after posting" for every recommendation

For a weekly schedule: Build a 5-day plan:

Monday:    [Content type] at [time] — [rationale]
Tuesday:   [Content type] at [time] — [rationale]
Wednesday: [Content type] at [time] — [rationale] ← peak day
Thursday:  [Content type] at [time] — [rationale]
Friday:    [Content type] at [time] — [rationale] (lighter content)

3-5 posts per week for quality-focused accounts
Space posts minimum 2 hours apart on multi-post days
Threads on Tuesday-Thursday mornings (highest dwell time)
Lighter content (polls, questions) on Monday/Friday

For a content calendar: Build a 2-4 week plan mixing:

1-2 threads per week (highest engagement format)
2-3 single posts per week (insights, tips, observations)
1 poll per week (engagement boost)
Daily reply/engagement time (15-30 min)

Step 4 — MCP Integration

If OpenTweet MCP is available:

Offer to schedule content directly
Use opentweet_batch_schedule for weekly plans
Suggest adding high-performers to the evergreen queue

Step 5 — Output

Present:

Recommendation with specific times (converted to user's timezone)
Rationale for each slot
Engagement reminders (reply windows, availability needed)
Content type suggestions for each slot if doing a weekly plan

Key Rules

Always specify timezone
Wednesday is the peak day — schedule best content here
Avoid weekends unless the audience is consumer/hobby
Never schedule without a reply plan — posting and disappearing wastes the first-hour window
If user can't be available to reply, schedule for the next available window where they can be present

Download now (ZIP)

Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
jlia0/tinyclaw★ 3.6ksame name
TinyAGI/tinyagi★ 3.6ksame name
TinyAGI/tinyclaw★ 3.6ksame name
SethGammon/Citadel★ 927same name
boldsoftware/shelley★ 704same name
first-fluke/fullstack-starter★ 223same name
svy04/ballast★ 73same name
invergent-ai/surogates★ 28same name
Hassaan146/claude-skills★ 18same name
thtskaran/claude-skills★ 18same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use send-user-message, tinyagi-admin and 10 more.
Other files people use alongside this one.
- Maliot100XSkill
  send-user-message
  Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.
  Also in 4 projects that use this
- jlia0Skill
  tinyagi-admin
  Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.
  Also in 3 projects that use this
- gildasfremontSkill
  setup-cowork
  Guided Cowork setup — install a matching plugin, try a skill, connect tools.
  Also in 4 projects that use this
- thtskaranSkill
  consolidate-memory
  Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.
  Also in 6 projects that use this
- anyprotoSkill
  skills-manager
  Context-aware routing to skills and hooks management. Use when troubleshooting skill activation, fine-tuning keywords, or managing the automated documentation system.
  Also in 3 projects that use this
- OpenAISkill
  imagegen
  Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.
  Also in 4 projects that use this
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- composeSkill
- engageSkill
- hooksSkill
- mediaSkill
- optimizeSkill
- postSkill
- repurposeSkill
- researchSkill
- reviewSkill
- setupSkill
- strategySkill
- testSkill
- threadSkill

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free

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

Intelligent Posting Schedule

Input

Process

Step 1 — Load Timing Data

Step 2 — Gather Context

Step 3 — Generate Recommendation

Step 4 — MCP Integration

Step 5 — Output

Key Rules

Word for word · 0

Edited · 0

Wrote their own version · 35

send-user-message

tinyagi-admin

setup-cowork

consolidate-memory

skills-manager

imagegen

Does it work?

Your trail

Now do this for your own.