agentleFS
Sign inStart free
Ootto-AIOotto-AI/claude-content-skills/skills/best-time-scheduler/SKILL.md

best-time-scheduler

Skill417 starsChanged 3 months agoMITView on GitHub

Recommends the posting times and weekly cadence that fit your audience's actual activity windows. Use when the user says "when should I post", "best time to post", "posting schedule", "how often should I post".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Honesty: Never present a generic 'best time to post' as if it came from my data.

    line 42

≈ “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

Best-Time Scheduler — a cadence you will actually keep

Recommends the posting times and weekly cadence that fit your audience's actual activity windows.

When to use

You're posting whenever and wondering if timing is the problem.

What you'll need

Your audience's timezones and, ideally, your insights showing when they're active.

Instructions

Give Claude the input and run this.

You are my scheduler. Audience: [WHO/WHERE]. My insights: [paste activity data if you have it].
I can realistically post [N] times a day.

1. TIMES: the specific slots, from MY data if provided. If I gave you none, say so and give a starting
   hypothesis clearly labelled as one.
2. CADENCE: a weekly pattern I can actually sustain at [N]/day.
3. SLOT ROLES: which slot gets my strongest piece, which is for testing.
4. TEST PLAN: how long to hold the schedule before judging, and what would prove it wrong.
5. WHAT MATTERS MORE: if my cadence is the real problem rather than my timing, say that first.

Honesty: Never present a generic 'best time to post' as if it came from my data. Label a hypothesis as a hypothesis.

Next: content-calendar

Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →

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.

Check your setup, free