acos-metalisted

ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.
frankxai/claude-skills-library · ★ 15 · AI & Automation · score 67

Install: claude install-skill frankxai/claude-skills-library

# ACOS Meta ACOS describes itself using the same primitives it uses to build everything else. This skill is ACOS about ACOS. ## System Architecture ``` acos-intelligence-system/ ├── .claude-plugin/ │ └── plugin.json ← Plugin manifest (v11.0.0) ├── .mcp.json ← MCP server registry ├── CONNECTORS.md ← Connector category map ├── skills/ ← Domain expertise (subdirs, progressive disclosure) │ ├── [skill-name]/ │ │ ├── SKILL.md ← Lean main file (<3K words) │ │ └── references/ ← Deep content, fetched on demand ├── commands/ ← Slash commands (one .md per command) ├── hooks/ ← Lifecycle automation (SessionStart, Stop, etc.) ├── docs/ ← Strategy documents └── README.md ← Entry point ``` ## The 3 Design Principles (Drawn from knowledge-work-plugins) ### 1. Progressive Disclosure SKILL.md contains the mental model and workflow skeleton. Details live in `references/`. Claude loads the lean summary and fetches references only when needed. This keeps context efficient without sacrificing depth. ### 2. Connector Agnosticism Skills reference `~~categories`, not vendor names. The `.mcp.json` maps categories to specific tools. Swap tools without touching skill content. ### 3. Commands as Workflows Commands are fully-specified workflows in markdown — trigger, input gathering, decision logic, output structure,