agentleFS
dynos-fitdynos-fit/dynos-work/skills/local/SKILL.md

local

Skill2 starsChanged 8 months agoMITView on GitHub

Internal dynos-work skill. Manage the project daemon: start, stop, status, logs, run-once, dashboard. Runs only when the user explicitly types /dynos-work:local; never auto-triggered from conversation.

3 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Do not fake local daemon status from prior runs.

    line 12
  2. Distinctive:

    If the command fails, surface the failure directly and do not imply the daemon changed state.

    line 14
  3. Distinctive:

    If no subcommand is given, show the status.

    line 67

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

dynos-work: Local

Manage the local project daemon.

Ruthlessness Standard

  • Do not fake local daemon status from prior runs.
  • Report the exact command result for the requested subcommand.
  • If the command fails, surface the failure directly and do not imply the daemon changed state.

Usage

/dynos-work:local start              # start daemon
/dynos-work:local stop               # stop daemon
/dynos-work:local status             # show daemon status
/dynos-work:local logs               # show cycle history
/dynos-work:local run-once           # run single maintenance cycle
/dynos-work:local dashboard          # generate per-project HTML dashboard

What you do

Parse the user's arguments to determine the subcommand. Run the corresponding Python command:

start

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/daemon.py" start --root .

stop

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/daemon.py" stop --root .

status

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/daemon.py" status --root .

Print the JSON result in a human-readable format: running/stopped, last cycle time, cycle count.

logs

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/daemon.py" logs --root .

run-once

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/daemon.py" run-once --root .

dashboard

PYTHONPATH="${PLUGIN_HOOKS}:${PYTHONPATH:-}" python3 "${PLUGIN_HOOKS}/dashboard.py" generate --root .

Print the path to the generated HTML file. This is generate-only (no server). The global dashboard (/dynos-work:dashboard) is the web server for all projects.

Default

If no subcommand is given, show the status.

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.