Generalv2.0.0

split-io

Manage Split.io feature flags - get status, check targeting, add/remove companies, create, and archive flags across environments

by Ashley DeaneView on GitHub ↗
splitfeature-flagsfeature-flagsplit-iotargetingrolloutflagsarchive

Split.io Feature Flag Management

Manage Split.io feature flags directly from Claude Code. Check flag status across environments, inspect targeting rules, find which companies are in a flag, and create or archive flags with safety guardrails.

Installation

claude plugin install split-io@personio-claude-code-marketplace

What you need

  • SPLIT_API_KEY environment variable set to your Split.io Admin API key
  • python3, curl, and jq available on your system

Getting a Split API key

API keys must be requested through a Foundations/TPF service desk request: https://personio.atlassian.net/servicedesk/customer/portal/30

Important: Do not create API keys tied to individual user accounts. Split has a seat limitation, so individual accounts are periodically rotated and their API keys are deleted when this happens. Instead, request a service account for your team or area. This ensures the key remains stable regardless of seat rotation.

What does this plugin do?

This plugin provides a single skill (split) that covers all feature flag operations through the Split.io Admin API:

  • Get flag status across dev and prod (targeting rules, treatments, kill status)
  • Check if a company is targeted by a flag (whitelist + segment membership)
  • Search for all flags targeting a specific company
  • List all companies in a flag's targeting rules
  • Create new feature flags
  • Archive feature flags (with double confirmation safety) — flags are archived, not deleted, to preserve their audit history

Get Flag Status

Check a feature flag's full status across both dev and prod environments.

Quick Start:

Check the status of the feature flag enable-new-dashboard

Example:

"What's the status of enable-payroll-v2?"

Returns: flag metadata, kill status, treatments, targeting rules, traffic allocation, and segment references for both dev and prod.

Why would you want this?

  • Quickly see if a flag is active or killed without opening the Split UI
  • Compare targeting between dev and prod at a glance
  • Understand the full targeting picture (rules, segments, traffic allocation)

Check Company in Flag

Check if a specific company ID is targeted by a feature flag.

Quick Start:

Is the flag enable-payroll-v2 enabled for company 54321?

Example:

"Does company 12345 have enable-new-reports in prod?"

Returns: whether the company is targeted, by what method (whitelist or segment), and what treatment it would receive.

Why would you want this?

  • Verify a company is correctly targeted before testing
  • Debug why a company does or doesn't see a feature
  • Check targeting without navigating the Split UI

Search Flags for a Company

Find all feature flags that target a specific company ID.

Quick Start:

What flags are enabled for company 12345?

Example:

"Show me all flags targeting company 99887 in prod"

Returns: every flag that targets the company (via whitelist or segment), the treatment, and whether the flag is killed.

Why would you want this?

  • Audit what features a specific company has access to
  • Debug unexpected behavior by checking all active flags
  • Understand a company's full feature set

List Companies in a Flag

List all companies targeted by a specific feature flag.

Quick Start:

What companies have the flag enable-new-reports enabled?

Example:

"List all companies in the enable-dark-mode flag in dev"

Returns: individually targeted keys and segment members, grouped by treatment.

Why would you want this?

  • See who's in a rollout at a glance
  • Verify the right companies are targeted
  • Check segment membership without opening the Split UI

Create a Feature Flag

Create a new feature flag in the Split.io workspace and initialize it in both dev and prod with default on/off treatments (defaulting to off).

Quick Start:

Create a new feature flag called enable-dark-mode

Example:

"Create a flag called enable-new-analytics with description 'Analytics v2 rollout'"

Creates the flag in the workspace and initializes it in both dev and prod with on/off treatments (defaulting to off).

Why would you want this?

  • Quickly create flags without switching to the Split UI
  • Flag is immediately available in both environments
  • Include a description at creation time

Archive a Feature Flag

Archive a feature flag across all environments — flags are archived, not deleted, so their configuration and audit history are preserved. Archiving hides the flag from default views, causes SDKs to return control for it, and reserves its name (it cannot be reused while archived).

Quick Start:

Archive the feature flag old-experiment-flag

Safety: Archiving requires double confirmation. Claude will:

  1. Warn you what archiving does
  2. Ask you to confirm
  3. Ask you to type the exact flag name
  4. Only proceed if the typed name matches exactly

Why would you want this?

  • Clean up old experiment flags without losing their history
  • Retire flags that are no longer needed while keeping an audit trail
  • Keep the flag list tidy