agentleFS
RainnystoneRainnystone/skill-orchestration-system/.agents/skills/sos/SKILL.md

sos

Skill10 starsChanged 6 months agoMITView on GitHub

Use when helping a user inspect, organize, plan, apply, activate, back up, or restore SOS-managed agent skill packs on Codex or Claude Code without assuming global installation.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. MetalLegBob/solana-vibes-kit★ 19same name
    2. parkkarl/claude-skill-sos★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for workflows around Skill Orchestration System (SOS) on Codex or Claude Code: inspecting active skills, proposing packs, …

    line 7
  2. Distinctive:

    Start in no-global-install mode.

    line 10
  3. Very specific:

    Use scripts/sos_doctor.py to detect whether SOS can run and which hosts are visible.

    line 11
  4. Distinctive:

    Prefer read-only or dry-run commands before any write.

    line 13
  5. Distinctive:

    Keep deterministic writes in the SOS CLI.

    line 14
  6. Very specific:

    Do not edit Codex config, Claude .sos-archive/, SOS vaults, manifests, registry files, backups, or generated pointer skills by hand.

    line 15
  7. Very specific:

    Read references/execution-modes.md when local capability is uncertain.

    line 18
  8. Very specific:

    Read references/workflows.md for the specific operation the user requested.

    line 19
  9. Very specific:

    Read references/safety-model.md before any write, restore, cleanup, sync apply, or source deletion.

    line 20
  10. Very specific:

    Read references/codex.md for Codex-specific config or skill-root behavior.

    line 21
  11. Very specific:

    Read references/claude-code.md for Claude-specific archive and skill-root behavior.

    line 22
  12. Distinctive:

    Do not load every reference up front.

    line 24
  13. Very specific:

    Keep README.md and README_CN.md aligned when user-facing install, usage, or workflow entry points change.

    line 26

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SOS Skill Orchestration

Use this skill for workflows around Skill Orchestration System (SOS) on Codex or Claude Code: inspecting active skills, proposing packs, creating reviewable plans, applying approved plans, activating packs, checking status, and restoring backups.

Default stance:

  • Start in no-global-install mode.
  • Use scripts/sos_doctor.py to detect whether SOS can run and which hosts are visible.
  • Resolve the host (--host codex or --host claude) before any write command.
  • Prefer read-only or dry-run commands before any write.
  • Keep deterministic writes in the SOS CLI.
  • Do not edit Codex config, Claude .sos-archive/, SOS vaults, manifests, registry files, backups, or generated pointer skills by hand.

Progressive disclosure:

  1. Read references/execution-modes.md when local capability is uncertain.
  2. Read references/workflows.md for the specific operation the user requested.
  3. Read references/safety-model.md before any write, restore, cleanup, sync apply, or source deletion.
  4. Read references/codex.md for Codex-specific config or skill-root behavior.
  5. Read references/claude-code.md for Claude-specific archive and skill-root behavior.

Do not load every reference up front. Do not paste the full CLI reference unless the user asks for command details or the selected workflow needs exact commands.

Keep README.md and README_CN.md aligned when user-facing install, usage, or workflow entry points change.

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.