feature-flags

Inspect Studio feature flag configurations across local and Helm deployment environments.

58|16|Updated May 14, 2026
One-click install
npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill feature-flags-nvidia-nemo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags
Source: https://github.com/NVIDIA-NeMo/nemo-platform/tree/main/web/.agents/skills/feature-flags
Command: npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill feature-flags-nvidia-nemo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing feature flags across multiple environments, helping developers and operators quickly identify why a specific feature is enabled or disabled.

Core Features & Use Cases

  • Environment Inspection: View the effective state of flags across local development and various deployment targets.
  • Configuration Management: Provides a clear workflow for adding, graduating, or removing feature flags in the codebase.
  • Use Case: Use this skill to debug why a new UI component is hidden in the production environment by comparing the local override values against the deployment-specific Helm configurations.

Quick Start

Run the feature flags skill to inspect the current matrix of all flags and their effective values across your environments.

Frequently Asked Questions about feature-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug why a Studio feature flag is disabled in a deployment environment?

You can debug feature flag visibility by analyzing cascades between code defaults, local overrides, and Helm deployment values. The skill inspects effective flag states across environments to identify why a feature is hidden.

What is the best way to manage feature flag overrides across local and deployment environments?

Manage feature flag overrides by inspecting the matrix of all flags and their effective values across local development and deployment targets. This ensures consistent state management through standardized naming conventions and configuration mapping.

How do you resolve conflicts between local feature flag overrides and Helm deployment values?

Resolve flag conflicts by analyzing the cascade of configuration layers from code defaults to local overrides and Helm values. This process maps the effective state to pinpoint exactly which layer is overriding the expected feature visibility.

Can I inspect all Studio feature flag states across multiple environments at once?

Yes, you can inspect the current matrix of all flags and their effective values across local and deployment environments. This provides a clear workflow for viewing environment states and managing the addition or removal of feature flags.

Why does a feature flag show different states between local development and production deployment?

Different feature flag states occur due to cascading configurations between local overrides and Helm deployment values. Analyzing these configuration layers reveals exactly which deployment-specific setting overrides the code defaults to alter feature visibility.