**Source URL:** https://limited.veevavault.dev/vault-dx/plugins/guides/using-with-other-agents

# Using Claude Plugins with Other Coding Agents

Veeva Claude Plugins were designed for Claude Code, but can be used with other coding agents.

The Claude Plugin skills are plain files: each skill is a folder containing a `SKILL.md` with `name` and `description` in its frontmatter, plus reference files the skill links to. Any coding agent that can read files can follow a skill, no Claude marketplace required.

To use Veeva Claude Plugins with another agent, copy the plugin folder into your project and point your agent at the `SKILL.md` for the skill you want to use. The agent reads the file, understands what the skill does and when to apply it, and follows its instructions.

What varies by agent is where the folder goes and how the agent discovers it. The following sections describe the most common patterns.

<Aside type="note">
The unit you copy is a whole plugin folder, not an individual skill. Skills link to reference files at the plugin root, and some links use `${CLAUDE_PLUGIN_ROOT}` to mean the plugin folder itself. Copy the entire plugin folder and treat that folder as the root when following any internal link.
</Aside>

## Installation by Agent

### Codex

Copy the plugin folder into `.agents/skills/` in your project, or `$HOME/.agents/skills/` to make it available to every project.

Invoke a skill with `$` or `/skills` to pick one explicitly, or describe the Vault task and Codex matches it against the skill's `description`.

Learn more in the [Codex skills documentation](https://learn.chatgpt.com/docs/build-skills).

### GitHub Copilot

Copy the plugin folder into one of the following locations:

*   `.github/skills/`, `.claude/skills/`, or `.agents/skills/` in the project for project-scoped access
*   `~/.copilot/skills/` or `~/.agents/skills/` for a single user across projects

Copilot loads a skill when the task fits the skill's `description`. If you use the Copilot cloud coding agent, commit the skill folder to the repository rather than relying on a personal location, which the cloud agent may not reach.

Learn more in the [GitHub Copilot agent skills documentation](https://docs.github.com/en/copilot/concepts/customizations/agent-skills).

### Agents that read AGENTS.md

Cursor, Gemini CLI, Windsurf, Aider, Zed, goose, opencode, Codex, and the Copilot coding agent follow an `AGENTS.md` file at the repository root. Codex and the Copilot coding agent also support the folder-based approach described in their sections above. Use whichever fits your workflow. Copy the plugin folder anywhere in the project (for example, `vault-skills/`) and add the following to your `AGENTS.md`:

```
Vault skills are in vault-skills/.
Before any Vault task, read the matching plugin's SKILL.md in full.
Open the reference files it links to as needed.
```

The agent reads the file nearest to the code being edited, and explicit chat instructions take precedence over all files.

Learn more in the [AGENTS.md specification](https://agents.md).

### Other agents

Copy the plugin folder into the working project and name the file directly in chat:

```
Read plugins/vault/skills/query/SKILL.md and follow it.
```

## Vault CLI

The [Vault CLI](/vault-dx/cli/) rules in each skill apply in any agent. When the CLI is installed, skills route operations through it. When it is absent, skills call the Vault API directly.

## Vault Documentation MCP

The `vault` plugin registers the Vault Documentation MCP automatically in Claude Code. In other agents, the MCP is not registered by the plugin. Point the agent at `https://general.veevavault.dev/` for reference questions, or add the MCP server manually if your agent supports MCP.

---

**Previous:** [Managing Installed Plugins](/vault-dx/plugins/guides/managing-plugins)  
**Next:** [References](/vault-dx/plugins/reference)