Install Bundled Vigilante Skills For All Runtimes

Most users assume vigilante setup auto-installs codex skills by default - but here’s the blind spot: Claude Code and Gemini CLI users often miss bundled skill assets during standard installation. While Codex assets ship reliably, Claude and Gemini runtimes lag behind unless triggered by their specific provider path. The current setup silos skill installation, creating broken expectations across supported runtimes.

What’s really happening? Setup routes through SetupWithProvider(...) and installs only the selected provider’s assets - Codex tricks work, but Claude Code and Gemini CLI rarely get their companion command files or runtime metadata unless manually guided. This isn’t just a minor gap; it’s a design flaw that undermines consistency for users relying on bundled skills for security, workflow, or AI-augmented productivity.

Here’s the core insight: internal/skill/skill.go already contains the runtime-specific logic that ensures all three runtimes - Codex, Claude Code, Gemini CLI - get their bundled assets. But setup skips this universal install, relying on provider-specific flags instead. That means every runtimescape is treated as a separate case, even though their skill layouts share structural DNA.

Here is the elephant in the room: Without automatic bundled install, users must remember to run provider-specific commands - or run setup from a repo checkout to unlock assets. This fragments the experience, especially for teams or solo contributors who value embedded, zero-friction skill access. The fix is simple: expand vigilante setup to iterate over all supported runtimes, installing bundled skills in their designated homes by default.

Safety first: The update preserves existing Codex behavior and respects provider-specific install patterns. No runtime data is overwritten unless intended. Tests must evolve too - adding coverage for Claude Code’s command files and Gemini’s .toml metadata to ensure idempotent, reliable results. When one runtime fails, the process should fail gracefully, not block all.

Should vigilante setup install bundled Vigilante skills for Codex, Claude Code, and Gemini CLI automatically? Yes. When should it stop? At ensuring no runtime is left behind - because security, consistency, and convenience demand it. Ready to close that gap once and for all?