Skill Orchestration System — Development skill for Claude Code

SOS: Make Vibe Coding More Lively

[English](README.md) | [中文](README_CN.md)

Good grief. Your agent skills should feel like a capable, tidy club room, not a storage closet where every discarded experiment has somehow earned permanent residency. Why does almost every AI Agent framework assume the solution to a complex task is to dump dozens of tools into the prompt context at once? You start vibe-coding, and within three days, your active skills folder looks exactly like the SOS Brigade clubroom—cluttered with strange, useless gadgets a certain chaotic "Brigade Chief" dragged in from who-knows-where. If you leave them all active, the Agent gets cross-eyed and response times crawl. If you move directories by hand, you are bound to miss a config file, a backup, or a rollback path. Since we've already been dragged into this bizarre club's workflow, we might as well handle it the rational way. Let's establish some basic paperwork rules to keep the chief's chaotic tool cabinet looking semi-professional.

---

🔍 What is SOS?

**Skill Orchestration System (SOS)** is a lightweight local Agent Skill manager and dynamic routing registry designed for **Codex** and **Claude Code**.

By utilizing a **Skill Pack (Vault Isolation) mechanism**, **Workspace-level recommendations**, and **local adaptive learning**, SOS helps developers automatically catalog and isolate large directories of `SKILL.md` folders. Without altering the agent's default lookup logic, SOS reduces active-layer skills by over 90%, preventing **Prompt Pollution**, **Context Dilution**, and **Function Hallucination**.

---

⚡ Pain Points & Solutions (Why You Need SOS)

As your local AI Agent skill library grows, directories degrade rapidly. Here is how SOS resolves these challenges:

• Prompt Bloat & Context Dilution: All SKILL.md folders are active, forcing the agent to process irrelevant instructions.
• Global vs. Project Tool Conflict: Tools for one project contaminate another, cau