agentleFS
Sign inStart free
ayleeaylee/agent-os/.agents/skills/open/SKILL.md

open

Skill0 starsChanged 4 months agoMITView on GitHub

Open and orient to a project when the user names a binder, asks to resume work, or needs the current state of a known project. Load the binder and its linked workstream without rewriting “last session” history.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    Read the binder, relevant area context, and the linked active state/workstreams/*/WORKSTREAM.md.

    line 9
  2. Distinctive:

    Read only the artifacts needed to understand the current objective, open decisions, verification, and next action.

    line 10

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

Open project

  1. Find the matching desk/*/BINDER.md, preferring an exact name or stable ID. Exclude closed examples unless explicitly requested.
  2. Read the binder, relevant area context, and the linked active state/workstreams/*/WORKSTREAM.md.
  3. Read only the artifacts needed to understand the current objective, open decisions, verification, and next action. Do not preload receipts or history.
  4. Present: project purpose, current truth, status, open decisions, important artifacts, verification state, and exactly one next action. For a closed workstream, report the terminal sentinel instead of inventing work.
  5. Flag missing links, divergent revisions, stale handoffs, or duplicated current status. Suggest $doctor for structural problems.

Opening is read-only. Do not update a binder merely because it was viewed, and do not require Git.

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