How detection works
An agent counts as installed when its config directory exists (for example~/.claude for Claude Code, ~/.codex for Codex). No per-agent integrations, no plugins: supporting an agent means knowing which user-level skills folder it reads.
Two families:
- Own-directory agents — Claude Code (
~/.claude/skills), Windsurf (~/.codeium/windsurf/skills), and others each get their own link into the central store. - Universal-directory agents — Cline, Warp, Zed, Kimi, and others read the shared
~/.agents/skillsconvention. That directory is linked exactly once and serves them all. Theuniversalpseudo-agent covers any future tool that adopts the convention — it activates whenever~/.agentsexists.
masterskills link (or any subsequent install) away.
Talking to MasterSkills through an agent
Installing skills works for all registry agents. Driving MasterSkills conversationally — “publish this”, “any updates?” — additionally requires the agent to run shell commands, since the MasterSkills skill drives themasterskills CLI. Claude Code is the reference experience; any agent that loads skills and executes commands works the same way.
Environment overrides
masterskills agents --json shows each agent’s id, detection state, and resolved skillsDir — useful when scripting or debugging link locations.