What problem does it solve? Setting up a new capability in an agent harness normally means hand-copying files, inventing names that may collide, and losing track of what was written where. This Skill turns capability installation into a repeatable, recorded procedure: it validates the package, checks for name collisions, personalizes the render against your MOD.md, and materializes everything behind a diff gate. ## Core Features & Use Cases - Validated installation pipeline: Resolves the capability directory, runs aos-cap manifest validation, checks installed versions, and installs missing dependencies first. - Name collision gating: Runs aos-cap skills --check and agents --check before writing anything, stopping on exit 17 so skill and agent names never clash across sources. - Personalized rendering: Runs the capability's onboarding interview, writes answers to MOD.md, and renders skills with {{mod}} slots filled per the overlay doctrine. - Diff-gated materialization: Stages symlinks, schedules, context blocks, and config keys, shows the full plan for approval, executes, records every artifact, and verifies with aos-cap verify. - Use Case: You tell your agent "install the work-tracker capability" — it resolves the package, installs the missing kb dependency first, interviews you, renders the skills, shows you the exact plan, and only then touches your harness. ## Quick Start Ask your agent to install a capability by name or path, for example: "Install the work-tracker capability from upstream into my harness."
