Claude (Enterprise)

Use this guide to install the private Gomboc Enterprise skills plugin for Claude Code.

This plugin is distributed only as a private zip package shared via Google Drive during Gomboc Enterprise onboarding. It is not published on any public marketplace.

What you will set up

By the end of this guide, you will have:

• The Gomboc Enterprise plugin package extracted locally on your machine

• The Gomboc Enterprise marketplace added to Claude Code

• The gomboc plugin installed in Claude Code

• A valid GOMBOC_API_TOKEN configured

• Docker available so the ORL container runtime can run

• A working Claude Code flow for Gomboc enterprise remediation and rule workflows

For background on ORL, see ORL (Open Remediation Language). For Gomboc rule concepts, see Rules

Who this is for

This guide is for Gomboc Enterprise customers who:

• use Claude Code as their coding agent

• have a valid Gomboc Enterprise subscription

• need enterprise remediation, rule authoring, or rule publishing workflows

If you are using the public community plugin instead, see Gomboc Community Skills

---

Prerequisites

Before you start, make sure you have the following.

Claude Code

• Claude Code must be installed and authenticated on your machine.

• Open Claude Code and confirm the plugin manager is available: /plugin

Enterprise Skills Plugin Package

• The plugin is distributed as a zip package via a Google Drive link shared by your Gomboc contact during onboarding.

• Download the zip and extract it to a stable location on your machine (for example ~/gomboc/gomboc-enterprise-skills/). The same extracted folder works for all four supported agent runtimes; you only need to do this once.

• To upgrade later, download the new zip your Gomboc contact provides and replace the extracted folder (or extract alongside and re-point the install commands to the new path).

The zip contains the full plugin — every per-agent manifest (plugin.json, gemini-extension.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json) plus all skills, commands, and reference files.

Gomboc API token

• You need a valid GOMBOC_API_TOKEN. See Generate A Personal Access Token.

Docker (for the ORL runtime)

• The Gomboc Enterprise plugin runs ORL through the public gombocai/orl:latest container image, managed automatically by the agent.

• Install Docker Desktop or Docker Engine for your operating system and confirm the daemon is running: docker info

For advanced ORL usage, see Custom Rules Quickstart (Advanced)

---

Step 1: Download and extract the plugin package

Download the zip file from the Google Drive link your Gomboc contact provided and extract it:

# Example — adjust the zip filename and destination to match your setup
unzip ~/Downloads/gomboc-enterprise-skills.zip -d ~/gomboc/

For the rest of this guide, the path ~/gomboc/gomboc-enterprise-skills/ refers to the extracted folder. Adjust it to wherever you extracted the zip.

Step 2: Add the Gomboc marketplace and install the plugin

Claude Code reads the marketplace manifest from .claude-plugin/marketplace.json at the root of the extracted folder. Add the marketplace from the local path:

1. Start Claude Code and open the plugin manager: /plugin

2. Select Add Marketplace.

3. When prompted for the marketplace source, enter the absolute path to the extracted folder, for example:

   /Users/you/gomboc/gomboc-enterprise-skills

4. Open the /plugin browser → select the Gomboc Enterprise marketplace → install the gomboc plugin.

5. Reload plugins if Claude Code prompts you to do so.

Step 3: Configure your Gomboc token

The gomboc plugin reads GOMBOC_API_TOKEN from the environment Claude Code is launched from. This is the most reliable way to configure it across Claude Code versions.

Set the variable in the shell that launches Claude Code:

export GOMBOC_API_TOKEN="<your-token>"
claude

To make this persistent, add the export line to your shell profile (~/.zshrc on macOS, ~/.bashrc on Linux, or equivalent). On macOS, if you usually launch Claude Code from Finder or Spotlight, launch it once from a terminal after updating your profile so the new value is inherited.

Keep this token private. Do not commit it to source control.

Alternative: in-app userConfig prompt

The plugin manifest also declares GOMBOC_API_TOKEN as a userConfig field. In Claude Code versions where the userConfig prompt is wired up correctly, Claude Code asks for the value at plugin enable time and stores it in your system keychain (or ~/.claude/.credentials.json as a fallback).

If you want to use this path, open /plugins → Installed → gomboc and run Disable plugin, then re-enable it. If a prompt appears asking for Gomboc API Token, paste your token there.

If no prompt appears, the in-app configuration flow is affected by a known Claude Code bug (anthropics/claude-code#39827). Use the shell environment variable approach above instead.

Verify the token is in use

Inside Claude Code, run a workflow that needs the token, for example asking the agent to Pull rules from the default channel using the orl skill. If the token is correctly configured, the call succeeds; if it is missing or invalid, you will see a Missing GOMBOC_API_TOKEN or 401 Unauthorized error from the Rules Service.

Step 4: Confirm the ORL runtime

The gomboc plugin's orl skill resolves the runtime for you. It uses a local orl binary when one is on your PATH, and otherwise runs ORL through the gombocai/orl:latest Docker container (pulled automatically on first use). You do not invoke the runtime directly.

Verify the integration end-to-end by asking the agent to run the orl skill with the version subcommand. The skill prints the resolved ORL version and reports the execution method (local binary or container image).

In the Claude Code chat, type: /orl version

If the call fails (no version returned, or an error referencing the runtime), see ORL runtime not available under Troubleshooting below.

Step 5: Run your first Gomboc workflow

Once the plugin, token, and ORL runtime are configured, use the Claude Code commands provided by the plugin.

Fix a concrete issue in code

Use: /fix

• This workflow helps apply or build a fix for a concrete violation in code.

Create a reusable rule

Use: /new-rule

• This workflow helps create a reusable ORL rule from a policy, classification, or requirement.

Release or publish a rule

Use: /release

• This workflow supports enterprise rule release and publishing flows.

• For details about publishing ORL rules, see Publish and Rule Service API

---

Troubleshooting

Use this section to diagnose the most common setup issues.

Plugin package download or extraction issues

If the zip file provided by your Gomboc contact cannot be downloaded or extracted:

• Confirm the Google Drive link is still valid and has not expired. Ask your Gomboc contact to re-share if needed.

• Confirm the download completed fully before extracting — a partial download will fail silently or produce an empty folder.

• On macOS, if unzipping via Finder produces an incomplete result, prefer the terminal: unzip ~/Downloads/gomboc-enterprise-skills.zip -d ~/gomboc/

• Confirm you have write access to the destination folder.

If you are still unable to obtain the package, contact your Gomboc representative.

Marketplace does not appear in Claude Code

If the marketplace was added but does not appear in the plugin browser:

• Refresh or update the marketplace from the Claude Code plugin manager.

• Restart Claude Code.

• Reopen /plugin and check the marketplace list again.

If the problem persists, remove the marketplace from the Claude Code plugin manager and re-add it using the absolute path to the extracted folder.

Plugin does not appear after adding the marketplace

If the marketplace appears but the gomboc plugin is missing:

• Confirm that the marketplace source is the absolute path to the extracted folder (the folder that contains .claude-plugin/marketplace.json at its root).

• Confirm that the extracted folder is still present at that path and has not been moved or deleted.

• Refresh the marketplace from the Claude Code plugin manager.

• Restart Claude Code and open /plugin again.

Token configuration errors

If the plugin reports authentication or token errors:

• Confirm that GOMBOC_API_TOKEN is set.

• Confirm that the token is valid and has not expired.

• Generate or rotate your token — see Generate A Personal Access Token

• Reconfigure the installed gomboc plugin with the new token.

ORL runtime not available

If Claude Code or the plugin reports that ORL cannot be executed:

• Run docker info to confirm Docker is installed and the daemon is running.

• Pull the image manually to confirm registry access: docker pull gombocai/orl:latest

• If you maintain a local orl binary, confirm it is on PATH with command -v orl.

• Restart your terminal and Claude Code after fixing Docker or PATH.

ORL command runs but remediation fails

If ORL is available but remediation does not complete:

• Confirm that you are running the command from the correct project or workspace.

• Confirm that the target files are supported by the workflow you are running.

• Confirm that your GOMBOC_API_TOKEN is valid.

• Review the command output for rule, language, or workspace errors.

For ORL concepts and supported rule workflows, see ORL (Open Remediation Language) and Workspace

Plugin updates do not appear

If a new version of the plugin is available but Claude Code still shows an older version:

• Confirm you have downloaded the latest zip from the Google Drive link your Gomboc contact provided.

• Replace the contents of the extracted folder (or extract the new zip to the same path).

• Update the marketplace from the Claude Code plugin manager so Claude Code re-parses the manifest.

• Restart Claude Code.

Still need help?

If you are still blocked, contact the Gomboc team with:

• the step where the setup failed

• the error message you received

• the absolute path to your extracted plugin folder

• the output of docker info (or orl --help, if you use a local binary)

See Support for support channels.