agentleFS
Sign inStart free
last9last9/mithai/skills/scheduling/SKILL.md

scheduling

Skill20 starsChanged 5 months agoApache-2.0View on GitHub

You can schedule recurring tasks that trigger yourself via cron + Slack. When you create a schedule, a cron job posts a message mentioning you in the specified Slack channel. When that message arrives, you process it like any other @mention — no special scheduler needed. - Use list_schedules to see what's already scheduled before creating duplicates - Use descriptive labels so you can find and remove schedules later - Cron expressions are in the system timezone — confirm with…

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. halide/Halide★ 6.6ksame name
    2. mariagorskikh/open-instinct★ 428same name
    3. poolside-ventures/meetbot-mcp★ 1same name

    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.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you create a schedule, a cron job posts a message mentioning you in the specified Slack channel.

    line 5
  2. Very specific:

    Use list_schedules to see what's already scheduled before creating duplicates

    line 23
  3. Distinctive:

    Use descriptive labels so you can find and remove schedules later

    line 24
  4. Very specific:

    When backend: agent_cloud_platform is set in config, schedules are stored centrally and survive restarts.

    line 28

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

You can schedule recurring tasks that trigger yourself via cron + Slack.

How it works

When you create a schedule, a cron job posts a message mentioning you in the specified Slack channel. When that message arrives, you process it like any other @mention — no special scheduler needed.

When to use scheduling

  • Recurring tasks: EOD summaries, morning health checks, weekly digests
  • Periodic monitoring: check a service every N hours and report
  • Reminders: nudge the team about standups, deployments, reviews

When NOT to use scheduling

  • One-time tasks — just do them now
  • Tasks that need sub-minute precision — cron's minimum is 1 minute
  • Tasks that don't need your reasoning — use a plain cron + script instead

Tips

  • Use list_schedules to see what's already scheduled before creating duplicates
  • Use descriptive labels so you can find and remove schedules later
  • Cron expressions are in the system timezone — confirm with the user if needed
  • Channel ID is required (not channel name). Ask the user or check the current channel
  • Labels must be alphanumeric with hyphens/underscores (e.g. eod-summary)
  • When backend: agent_cloud_platform is set in config, schedules are stored centrally and survive restarts; otherwise they fall back to the local crontab

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