Waiting for engine...
Skip to main content

Installing Boomi Companion on GitHub Copilot and other non-Claude tools

Boomi Companion is built as a Claude plugin, a Claude-specific packaging format that lets you install a curated set of tools, skills, commands, and agents through Claude's plugin system in a single step.

The full Boomi Companion plugin experience (including its plugin marketplace and installation flow) is available only in Claude Code and Claude Cowork. However, the skills inside Boomi Companion follow the Agent Skills open standard, an open, cross-platform format developed by Anthropic and adopted by a wide range of AI coding tools.

warning

The Agent Skills open standard does not support commands. As a result, commands included in Boomi Companion will not be available.

You can install and use each individual Boomi skill independently in any tool that supports the standard without needing Claude Code or Claude Cowork, including:

  • GitHub Copilot (not Microsoft Copilot)
  • Cursor
  • OpenAI Codex
  • Gemini CLI

Installing on GitHub Copilot​

GitHub Copilot loads Agent Skills from a fixed set of directories and, as of GitHub CLI 2.90.0, offers a gh skill command for discovering and installing them. Copilot skills work in Copilot's cloud agent, Copilot code review, the GitHub Copilot CLI, the GitHub Copilot app, and agent mode in Visual Studio Code and JetBrains IDEs.

Option A: Install with the GitHub CLI​

  1. Confirm you have GitHub CLI 2.90.0 or later installed (gh --version). The gh skill command is in public preview and subject to change.

  2. Inspect the skill before installing it:

    gh skill preview OfficialBoomi/boomi-integration

    Always preview a skill before installing it. GitHub does not verify third-party skills, and a skill's SKILL.md and any bundled scripts run with your permission once installed.

  3. Install it:

    gh skill install OfficialBoomi/boomi-integration

    By default, this installs at project scope. Add --scope user to install once for every repository instead, or --agent github-copilot if you use gh skill with multiple agent hosts and want to target Copilot explicitly.

  4. Run gh skill update any time you want to pull in upstream changes to the skill.

Option B: Install manually​

  1. Clone or download the skill:

    git clone https://github.com/OfficialBoomi/boomi-integration.git

  2. Move the resulting folder into one of Copilot's skill directories:

    ScopeDirectory
    Project (this repository only).github/skills/, .claude/skills/, or .agents/skills/
    Personal (every repository)~/.copilot/skills/ or ~/.agents/skills/

    For example, to install boomi-integration for the current repository only:

    mkdir -p .github/skills
    cp -r boomi-integration .github/skills/

After installing​

Copilot decides when to use a skill based on your prompt and the skill's description field; you do not need to invoke it explicitly. If Copilot prompts you to run a bundled script, such as one of boomi-integration's CLI helpers for pushing components to the Boomi Platform API, review the script before approving it.

Installing on Cursor​

Cursor discovers Agent Skills automatically from a set of skill directories, and also reads Claude's and Codex's skill directories for compatibility. There is no separate "install" command for a standalone skill; you add the folder to a skill directory and Cursor picks it up.

  1. Clone the skill:

    git clone https://github.com/OfficialBoomi/boomi-integration.git

  2. Copy or symlink it into one of Cursor's skill directories:

    ScopeDirectory
    Project (this repository only).cursor/skills/ or .agents/skills/
    Personal (every repository on this machine)~/.cursor/skills/ or ~/.agents/skills/

    For example, to register it as a project-scoped skill:

    mkdir -p .cursor/skills
    ln -s "$(pwd)/boomi-integration" .cursor/skills/boomi-integration

  3. Restart Cursor, or open Customize → Skills to confirm boomi-integration was discovered.

Cursor's Agent decides when to use the skill automatically. You can also invoke it explicitly by typing /boomi-integration in Agent chat, or keep it active for the whole session by loading it as a Custom Mode.

note

Cursor's Customize → Skills → From GitHub Repository import is for skills packaged as a Cursor plugin (a repository with a .cursor-plugin/marketplace.json file). Boomi ships standalone Agent Skills, not Cursor plugins, so use the clone-and-copy steps above instead of that import flow.

If you plan to sync this skill to Cursor's Cloud Agents, it must live under ~/.cursor/skills/ and you must turn on Sync Skills for Cloud Agents in Settings → Agents; skills under ~/.agents/skills/ or project directories are not copied to Cloud Agents automatically.

Installing on OpenAI Codex​

Codex reads Agent Skills from .agents/skills directories at the repository level and from your home directory at the user level. Skills work the same way across the Codex CLI, the Codex IDE extension, and the Codex app.

  1. Clone the skill:

    git clone https://github.com/OfficialBoomi/boomi-integration.git

  2. Copy it into the directory for the scope you want:

    ScopeDirectory
    Repository (checked in for your team).agents/skills/ at your repository root
    Personal (every repository on this machine)~/.agents/skills/

    For example, to make it available to everyone who works in a given repository:

    mkdir -p .agents/skills
    cp -r boomi-integration .agents/skills/

  3. Codex detects new skills automatically. If boomi-integration doesn't appear, restart Codex.

Codex can pick the skill automatically based on your prompt, or you can invoke it explicitly by typing $boomi-integration in the CLI or IDE extension.

note

Codex also has a built-in $skill-installer for pulling curated skills into your local setup. Boomi's skills aren't in that curated catalog today, so use the manual steps above.

Installing on Gemini CLI​

Gemini CLI can install a skill directly from a Git repository, or read it from a local skills directory.

Using the gemini CLI:

gemini skills install https://github.com/OfficialBoomi/boomi-integration.git --consent

--consent skips the interactive security confirmation. Add --scope workspace to install the skill for the current project only; the default scope is user (available in every project).

Installing manually, clone the repository into one of Gemini CLI's skill directories instead:

ScopeDirectory
Workspace (this project, shareable via version control).gemini/skills/ or .agents/skills/
User (every project on this machine)~/.gemini/skills/ or ~/.agents/skills/
git clone https://github.com/OfficialBoomi/boomi-integration.git ~/.gemini/skills/boomi-integration

Verify the install with gemini skills list --all, or from an interactive session run /skills list. Use /skills disable boomi-integration or /skills enable boomi-integration to toggle it, and /skills reload after pulling updates to the skill's files.

Slash commands and the skills-only experience​

Claude Code and Claude Cowork add plugin packaging on top of the same skills: slash commands such as /freshies, bundled sub-agents, and one-step install and auto-update through the plugin marketplace. None of that packaging exists in GitHub Copilot, Cursor, OpenAI Codex, or Gemini CLI.

This is a packaging difference, not a capability gap. The skill itself, not the slash command, carries the instructions Boomi Companion follows. Anywhere Boomi's documentation references a slash command, ask your agent to do the same thing in plain language instead. For example, instead of /freshies order-sync, say "Set up a new Boomi project called order-sync from my template." If a tool has its own shortcut for repeating that kind of request (a custom mode, an alias, a saved prompt), you can use that too.

On this Page