featureops
Manage feature flags with Unleash — evaluate whether a code change needs a flag, create flags with consistent naming, wrap code behind flags, plan progressive rollouts, and clean up stale flags. Use when working with feature flags, feature toggles, rollouts, releases, experiments, kill-switches, canary deploys, or the Unleash MCP server. Ships as a customizable FeatureOps template — set your team's policy in an override file (`.unleash/featureops.md`); no need to edit the skill.
Install
With your agent
Install OMGSkills skill "unleash/unleash-claude-skills:skills/featureops" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Unleash/unleash-claude-skills /tmp/unleash-claude-skills && ln -s /tmp/unleash-claude-skills/skills/featureops ~/.claude/skills/featureopsFrom README
Unleash · FeatureOps Template This skill brings FeatureOps — the discipline of controlling software behavior at runtime — into your coding agent. It drives the Unleash MCP server to evaluate changes for risk, create flags with consistent naming, generate SDK guard code, manage rollouts, and clean up stale flags. The defaults work out of the box, but feature-management conventions vary across teams and industries. This skill ships as a customizable template: every tunable value lives in one policy file, which you override per project without editing the skill — see Active policy and Customize for your team. check This skill needs the Unleash MCP server connected. When installed as a Claude Code plugin, the server is registered automatically from the bundled .mcp.json; you only need to set three environment variables in the shell that launches your agent.