agentleFS
Sign inStart free
fmindfmind/dot/skills/scheduled-jobs/SKILL.md

scheduled-jobs

Skill13 starsChanged 3 days agoMITView on GitHub

Schedule and debug local jobs with systemd timers or macOS launchd.

6 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

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    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
  1. Distinctive:

    Run an existing bounded command through the native user scheduler and prove its outcome.

    line 15
  2. Distinctive:

    Keep definitions in the owning repository: call an existing bounded command by absolute path with locked dependencies and one writer lock.

    line 20
  3. Very specific:

    Workstation units live in fmind/dot: put them in dot_config/systemd/user/, enable timers through a managed timers.target.wants symlink, and …

    line 25
  4. Distinctive:

    Stay in user space: do not enable system services or lingering merely to keep a laptop job alive.

    line 30

“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

Scheduled Jobs

Run an existing bounded command through the native user scheduler and prove its outcome. python-script owns program code, and mise owns task commands.

Workflow

  1. Choose the native owner: Linux user timers or macOS LaunchAgents; keep an existing project scheduler unless migration is requested, and leave harness-native agent schedules to the host skill.
  2. Keep definitions in the owning repository: call an existing bounded command by absolute path with locked dependencies and one writer lock; enable it only after the user approves its recurring effects and schedule.
  3. Prove a scheduler-triggered run: a manual run, valid unit, or enabled timer is partial evidence; check the real triggered run and its application result.

Owner conventions

  • Workstation units live in fmind/dot: put them in dot_config/systemd/user/, enable timers through a managed timers.target.wants symlink, and add each unit's hash to run_onchange_after_systemd-user-reload.sh.tmpl, which runs systemctl --user daemon-reload on apply.
  • Never restart the agy daemon from apply: it may host this remote-control session; the reload hook only prints the restart command.

Gotchas

  • Stay in user space: do not enable system services or lingering merely to keep a laptop job alive; explain when the requested availability exceeds a user session.
  • Never blindly replay a timed-out mutation: decide whether a missed run is skipped or coalesced, and resume only from current state.

Documentation

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