agentleFS
Sign inStart free
dynos-fitdynos-fit/dynos-work/skills/global/SKILL.md

global

Skill2 starsChanged 8 months agoMITView on GitHub

Internal dynos-work skill. Manage the global cross-project sweeper daemon. Runs only when the user explicitly types /dynos-work:global; never auto-triggered from conversation.

2 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 daemon health from stale assumptions.

    line 12
  2. Distinctive:

    If the subcommand fails, surface the failure directly instead of printing a polite summary.

    line 14
  3. Distinctive:

    If no subcommand is given, show the status.

    line 59

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

Manage the global daemon that sweeps all registered projects.

Ruthlessness Standard

  • Do not fake daemon health from stale assumptions.
  • Report the exact status returned by the command.
  • If the subcommand fails, surface the failure directly instead of printing a polite summary.

Usage

/dynos-work:global start             # start sweeper
/dynos-work:global stop              # stop sweeper
/dynos-work:global status            # show health
/dynos-work:global run-once          # single sweep
/dynos-work:global logs              # sweep history

What you do

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

start

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

stop

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

status

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

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

run-once

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

logs

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

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.

Check your setup, free