agentleFS
saksham10arora-dotcomsaksham10arora-dotcom/everything-claude-codex/skills/boot/SKILL.md

boot

Skill74 starsChanged 9 days agoMITView on GitHub

Use when the user says "/boot", "start session", "boot up", "what's the situation", or starts a session wanting a full briefing

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, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read in parallel, then stop reading once you have what you need:

    line 8
  2. Very specific:

    Only open a tracker (*_tracker.md) if hot.md lacks the detail.

    line 12
  3. Distinctive:

    Never invent a status or deadline.

    line 34
  4. Distinctive:

    If hot.md was last updated more than 2 days ago, say so.

    line 35

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

/boot: the 30-second session briefing

Read in parallel, then stop reading once you have what you need:

  1. .remember/hot.md: deadlines, active projects, tracks, hard rules
  2. daily/<today>.md if it exists

Only open a tracker (*_tracker.md) if hot.md lacks the detail. Never read big trackers by default.

Output (exactly this, no intro)

BOOT: <date>

Kill list (hard deadlines in the next 7 days)

Date | What | Status. If none: "None this week".

Active projects

One line each: name, status, what's left.

Tracks

One line per track from hot.md: where you are, what's next.

Today

Daily note headline, or "No daily note. Create one?"

What are we doing?

Rules

  • Load the "Hard rules" section of hot.md into working memory and never break them.
  • Never invent a status or deadline. If it isn't in the files, say "unknown, check <file>".
  • If hot.md was last updated more than 2 days ago, say so.
  • At the end of the session, remind the user to run /tldr.

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.