mycoadd-symbiontlisted

Use this skill when adding a new symbiont (agent integration) to Myco's SymbiontInstaller — the component that manages agent lifecycle operations (init, update, remove, doctor) for all registered agents. Activates whenever you need to onboard a new AI agent (Claude Code, Cursor, Windsurf, a custom agent, etc.) so that `myco init`, `myco update`, and `myco doctor` manage its installation. Apply this skill even if the user doesn't explicitly mention SymbiontInstaller — any time you're adding a new agent type, creating a symbiont manifest, wiring new hook templates, or extending the supported agents list, this skill applies. Also relevant when a new symbiont needs the cross-platform hook guard or environment variable injection.
goondocks-co/myco · ★ 13 · AI & Automation · score 79

Install: claude install-skill goondocks-co/myco

# Adding a New Symbiont to Myco's SymbiontInstaller ## Prerequisites - Understand the new agent's hook format and config file locations - Know the agent's config directory name (e.g., `.claude/`, `.cursor/`, `.gemini/`) - Determined whether the agent reads `AGENTS.md` natively or needs a thin instruction stub ## Integration Classes Not all agents can be wired via the same procedure. Before starting, identify which class applies: | Class | Description | Example agents | |-------|-------------|----------------| | **Class 1 — Config-File** | Agent is configured via JSON or TOML files in a project directory. Hooks, MCP entries, and instructions are written by `SymbiontInstaller` as file I/O. | Claude Code, Cursor, Windsurf, Codex, Gemini CLI, VS Code Copilot | | **Class 2 — Plugin-API** | Agent exposes a plugin registration API; it cannot be configured by writing files into a config directory. Requires a dedicated, agent-specific installation path in `SymbiontInstaller` — the standard Steps 1–8 below do NOT apply. | opencode | **If you are adding a Class 2 agent:** the steps below describe the Class 1 path only. Class 2 integration requires a separate SymbiontInstaller code path for plugin registration — consult the opencode implementation as the reference. Do not attempt to adapt the file-based manifest/hook steps for a plugin-API agent. ## Steps ### 1. Create the Symbiont Manifest Manifests live in `src/symbionts/manifests/`. Create `<agent-name>.yaml`: ```yaml name: