Expand description
vs skill install — install vibesurfer into every detected agent.
Each agent is targeted on two surfaces (when supported):
- Skill — SKILL.md (or GEMINI.md for Gemini) at the agent’s
conventional skills location, plus any sibling manifest the
agent expects (Gemini’s
gemini-extension.json). - MCP — an
mcpServers.vibesurfer = {command: "vs", args: ["mcp"]}entry in the agent’s MCP config file. Most agents share a JSON shape; Codex stores[mcp_servers.<name>]as TOML, hand-rolled here so we don’t pull a TOML crate.
Detection: an agent is considered installed when its config dir
exists or its CLI is on PATH. The canonical ~/.agents/ target
is always written. Per-agent failures don’t abort — the run
reports each result and exits non-zero only if no agent at all
could be reached.
Mirror of the agented::internal::agents shape. Keep this file
the single source of truth for vibesurfer agent integrations:
adding a new agent is one entry in agents(), not three patches
across the binary.