agentleFS
omnipresence-osomnipresence-os/claude-skills/load-worker/SKILL.md

load-worker

Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub

Warms up the current chat session as a project-scoped worker by reading the worker spec file from custom/projects/<active>/workers/<slug>.md and loading every methodology / process / skill / project file listed in its auto-load block before doing any task work. Trigger when the user says any of "load worker X", "load the X worker", "be the X worker", "act as the content writer", "warm up worker X", "I want to use the X worker", "as the X worker, do Y", "X worker please do Y", "use worker X for this". This is the ONE canonical way to invoke a saved worker — replaces the manual "read project info, read methodology A, read methodology B, read skill C..." prompt sequence with a single command. Reads the spec, fans out reads in parallel, surfaces a compact "loaded as <worker> for <project>: ready" confirmation before doing anything else, then routes the user's actual ask through the worker's propose-then-execute process plan. Idempotent — calling it twice in the same chat just re-confirms the active worker. Pairs with create-worker (which writes the spec).

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 10 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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.