managing-unleash

name	managing-unleash
description	Use when working with Unleash — unleash feature toggle management, activation strategies, environment configuration, and usage metrics. Covers toggle lifecycle, gradual rollout strategies, constraint-based targeting, project management, and API token administration. Use when managing feature toggles, configuring rollout strategies, reviewing toggle usage, or auditing changes in Unleash.
connection_type	unleash
preload	false

Unleash Management Skill

Manage and analyze feature toggles, strategies, projects, and environments in Unleash.

API Conventions

Authentication

All API calls use the Authorization: $UNLEASH_API_KEY header (admin token). Never hardcode tokens.

Base URL

$UNLEASH_URL/api (self-hosted or Unleash-hosted)

Core Helper Function

#!/bin/bash

UNLEASH_BASE="${UNLEASH_URL:-https://app.unleash-hosted.com}"

unleash_api() {
    local method="$1"
    local endpoint="$2"
    local data="${3:-}"

    if [ -n "$data" ]; then
        curl -s -X "$method" \
            -H "Authorization: $UNLEASH_API_KEY" \
            -H "Content-Type: application/json" \
            "${UNLEASH_BASE}/api${endpoint}" \
            -d "$data"
    else
        curl -s -X "$method" \
            -H "Authorization: $UNLEASH_API_KEY" \
            -H "Content-Type: application/json" \
            "${UNLEASH_BASE}/api${endpoint}"
    fi
}

Output Rules

• TOKEN EFFICIENCY: Extract only needed fields with jq
• Target <=50 lines per script output
• Never dump full API responses

Discovery Phase

List Projects and Toggles

#!/bin/bash
echo "=== Projects ==="
unleash_api GET "/admin/projects" \
    | jq -r '.projects[] | "\(.id)\t\(.name)\t\(.featureCount) toggles"' | column -t

echo ""
PROJECT_ID="${1:-default}"
echo "=== Feature Toggles ==="
unleash_api GET "/admin/projects/${PROJECT_ID}/features" \
    | jq -r '.features[0:25][] | "\(.type)\t\(.name)\t\(.enabled)\t\(.stale)"' | column -t

List Environments

#!/bin/bash
echo "=== Environments ==="
unleash_api GET "/admin/environments" \
    | jq -r '.environments[] | "\(.name)\t\(.type)\t\(.enabled)"' | column -t

echo ""
echo "=== Strategies ==="
unleash_api GET "/admin/strategies" \
    | jq -r '.strategies[] | "\(.name)\t\(.editable)\t\(.description[0:50])"' | column -t

Analysis Phase

Toggle Status by Environment

#!/bin/bash
PROJECT_ID="${1:-default}"

echo "=== Toggle Status ==="
unleash_api GET "/admin/projects/${PROJECT_ID}/features" \
    | jq -r '.features[0:20][] | "\(.name)\t" + ([.environments[] | "\(.name):\(.enabled)"] | join("\t"))' \
    | column -t

echo ""
echo "=== Stale Toggles ==="
unleash_api GET "/admin/projects/${PROJECT_ID}/features" \
    | jq -r '.features[] | select(.stale == true) | "\(.name)\t\(.type)\tcreated:\(.createdAt[0:10])"' | column -t | head -10

Event Log

#!/bin/bash
echo "=== Recent Events ==="
unleash_api GET "/admin/events?limit=20" \
    | jq -r '.events[] | "\(.createdAt[0:16])\t\(.createdBy)\t\(.type)\t\(.data.name // .featureName // "")"' \
    | column -t

echo ""
echo "=== Toggle Metrics ==="
TOGGLE_NAME="${1:?Toggle name required}"
unleash_api GET "/admin/client-metrics/features/${TOGGLE_NAME}" \
    | jq '{name: .featureName, lastHourRequests: .lastHourUsage | map(.yes + .no) | add, environments: [.lastHourUsage[] | .environment] | unique}'

Output Format

• Use tab-separated columns with column -t
• Limit lists to 15-25 items
• Show summaries before details

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

Shortcut	Counter	Why
"I'll skip discovery and check known resources"	Always run Phase 1 discovery first	Resource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"	Follow the full discovery → analysis flow	Quick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"	Audit configuration explicitly	Defaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"	Always check relevant metrics when available	API/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"	Try the command and report the actual error	Assumed permission failures prevent useful investigation; actual errors are informative

Common Pitfalls

• Admin vs client API: Admin API (/admin/) for management; client API (/client/) for SDKs
• Toggle types: release, experiment, operational, kill-switch, permission
• Strategies: Built-in strategies include default, userWithId, gradualRolloutRandom, flexibleRollout
• Stale toggles: Toggles older than lifecycle threshold are marked stale -- review and archive regularly
• Constraints: Strategy constraints allow targeting by context fields
• Self-hosted: Base URL varies -- always use $UNLEASH_URL env variable