SOS: Make Vibe Coding More Lively

English | 中文

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, causing the agent to execute wrong scripts.
• Fragile Manual Backups: Renaming or moving folders manually leads to config drift or lost work.
• Rigid Rule-Based Recommendations: Standard heuristics fail to adapt to a developer’s unique high-frequency tool chains.

SOS gives that sprawl a small, auditable shape:

• scan local SKILL.md folders;
• propose focused packs such as docs, browser, data, deploy, or tool-specific groups;
• write a dry-run plan before managed writes;
• copy selected skills into a managed vault;
• generate short active skills such as sos-haruhi and sos-;
• keep manifests, registry state, fingerprints, backups, and restore paths;
• recommend workspace-level packs through sos-nagato when one workspace needs a different setup from another.

---

🌟 Core Features

1. Skill Packs & Vault Isolation