agentleFS
Sign inStart free
conorbronsdonconorbronsdon/agent-context-os/skills/contextos-workspace/SKILL.md

contextos-workspace

Skill30 starsChanged 37 days agoMITView on GitHub

Run Context OS continuity and lifecycle workflows in a user-selected Context OS workspace. Use when asked to inspect, set up, update, or close a Context OS session.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Verify the selected root contains AGENTS.md, ROUTING.md, scripts/contextos.sh, and .agents/skills/.

    line 12
  2. Very specific:

    Read that workspace's AGENTS.md, ROUTING.md, and docs/safety-contract.md completely.

    line 16
  3. Distinctive:

    Follow that file; do not substitute a plugin-local copy or infer an operation that would expand the request.

    line 22
  4. Distinctive:

    Start is read-only. Setup, update and end require a displayed proposal and explicit approval of its exact digest before apply.

    line 24

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

Context OS workspace companion

  1. Identify the user's intended Context OS workspace. Ask for its path if it is not explicit or unambiguous. Never use the plugin installation/cache as a workspace, and never create a workspace or import context implicitly.
  2. Verify the selected root contains AGENTS.md, ROUTING.md, scripts/contextos.sh, and .agents/skills/. If not, stop and explain the repository-native setup in the bundled docs/codex-onboarding.md (relative to the plugin root, two directories above this file).
  3. Read that workspace's AGENTS.md, ROUTING.md, and docs/safety-contract.md completely. Use that workspace as the working directory. Do not mix installed-plugin code with another workspace's state.
  4. For the operation the user requested, read its canonical .agents/skills/context-setup/SKILL.md, context-start/SKILL.md, context-update/SKILL.md, or context-end/SKILL.md in the selected workspace. Follow that file; do not substitute a plugin-local copy or infer an operation that would expand the request.
  5. Start is read-only. Setup, update and end require a displayed proposal and explicit approval of its exact digest before apply. Never write lifecycle state directly, install hooks, or commit/push implicitly. Report receipts and verification limits. Plugin installation grants no extra authority.

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