agentleFS
Sign inStart free
NashEQifyNashEQify/forge/skills/boot/SKILL.md

boot

Skill2 starsChanged 5 days agoMITView on GitHub

Start Buddy, Forge's orchestrator, in a session that loads Forge as a plugin. Use when the project's or the user's AGENTS.md asks for the forge:boot skill before the first answer.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and follow framework/work-principle.md before taking up work.

    line 17
  2. Very specific:

    If this session's context already holds the BUDDY-BOOT REQUIRED entry, the boot is running: do not start it again, follow that entry.

    line 27
  3. Very specific:

    Run, as its own call: python3 <root>/scripts/user_scope.py --framework-root <root> --boot-entry

    line 32
  4. Very specific:

    Follow the printed entry before the first answer: it names the soul, the user scope, the files to read and the boot sequence.

    line 34

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

Read and follow framework/work-principle.md before taking up work. Resolve this reference against the framework root; retain the consumer CWD.

Skill: boot

The project's or the user's AGENTS.md asks for this skill with the line "Forge: start Buddy. Before the first answer, run the forge:boot skill and follow the boot entry it returns."

  1. If this session's context already holds the BUDDY-BOOT REQUIRED entry, the boot is running: do not start it again, follow that entry.
  2. The framework root <root> is the directory that holds .claude-plugin/, two levels above this skill's folder (<root>/skills/boot). Take the absolute folder from the skill listing the host shows.
  3. Run, as its own call: python3 <root>/scripts/user_scope.py --framework-root <root> --boot-entry
  4. Follow the printed entry before the first answer: it names the soul, the user scope, the files to read and the boot sequence. If the command fails, say so first in your first answer and follow <root>/agents/buddy/boot.md.

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