Sos
Skill Rainnystone/skill-orchestration-system/.agents/skills/sos
Skill-first CLI for turning agent skills into reviewable, routing-friendly packs.
npx -y skills add Rainnystone/skill-orchestration-system --skill sosAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.6 KB, as published. Nobody here has run it
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.pyto detect whether SOS can run and which hosts are visible. - Resolve the host (
--host codexor--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:
- Read
references/execution-modes.mdwhen local capability is uncertain. - Read
references/workflows.mdfor the specific operation the user requested. - Read
references/safety-model.mdbefore any write, restore, cleanup, sync apply, or source deletion. - Read
references/codex.mdfor Codex-specific config or skill-root behavior. - Read
references/claude-code.mdfor 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.