agentleFS
Sign inStart free
thisrohanguptathisrohangupta/harness-skills/skills/manage-feature-flags/SKILL.md

manage-feature-flags

Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub

Manage Harness Feature Flags via MCP. Create boolean or multivariate flags, list flags by project or workspace, get flag details with environment state, toggle flags on/off per environment, and delete flags. Use when asked to create a feature flag, toggle a flag, list flags, check flag status, enable or disable a feature, or manage feature rollouts. Trigger phrases: feature flag, toggle flag, create flag, enable feature, disable feature, flag status, feature rollout, kill switch.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create, list, toggle, and delete Harness Feature Flags via MCP.

    line 19
  2. Distinctive:

    Verify the flag identifier and environment before toggling.

    line 124
  3. Distinctive:

    Verify the flag identifier is correct (case-sensitive)

    line 132
  4. Distinctive:

    Check that the flag exists in the target project

    line 133
  5. Very specific:

    Use harness_list without filters to see all flags, then narrow down

    line 137
  6. Very specific:

    Use boolean for simple on/off flags

    line 140
  7. Very specific:

    Use multivariate when you need multiple string/number/JSON variations

    line 141

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Manage Feature Flags

Create, list, toggle, and delete Harness Feature Flags via MCP.

Instructions

Step 1: List Existing Flags

Call MCP tool: harness_list
Parameters:
  resource_type: "feature_flag"
  org_id: "<organization>"
  project_id: "<project>"

Filter by name or environment:

Call MCP tool: harness_list
Parameters:
  resource_type: "feature_flag"
  org_id: "<organization>"
  project_id: "<project>"
  name: "dark_mode"
  environment: "production"

Step 2: Get Flag Details

Call MCP tool: harness_get
Parameters:
  resource_type: "feature_flag"
  resource_id: "<flag_identifier>"
  org_id: "<organization>"
  project_id: "<project>"
  environment: "<environment>"

Step 3: Create a Flag

Call MCP tool: harness_create
Parameters:
  resource_type: "feature_flag"
  org_id: "<organization>"
  project_id: "<project>"
  body:
    identifier: "dark_mode"
    name: "Dark Mode"
    kind: "boolean"
    permanent: false
    description: "Enable dark mode UI theme"

Flag kinds:

  • boolean -- simple on/off toggle
  • multivariate -- multiple variations (e.g., string, number, JSON)

Step 4: Toggle a Flag

Call MCP tool: harness_execute
Parameters:
  resource_type: "feature_flag"
  action: "toggle"
  resource_id: "<flag_identifier>"
  org_id: "<organization>"
  project_id: "<project>"
  enable: true
  environment: "production"

Set enable: true to turn on, enable: false to turn off. The environment parameter is required.

Step 5: Delete a Flag

Call MCP tool: harness_delete
Parameters:
  resource_type: "feature_flag"
  resource_id: "<flag_identifier>"
  org_id: "<organization>"
  project_id: "<project>"

FME Resources

For Split.io-backed Feature Management & Experimentation (FME), use these additional resource types:

Resource TypeOperationsDescription
fme_workspacelistList FME workspaces
fme_environmentlistList FME environments
fme_feature_flaglist, getList/get flags by workspace (no environment required)

Examples

  • "Create a feature flag for dark mode" -- Create boolean flag with identifier dark_mode
  • "Turn on the new-checkout flag in staging" -- Toggle with enable: true, environment: "staging"
  • "Kill the experimental-search feature in production" -- Toggle with enable: false, environment: "production"
  • "List all feature flags in the payments project" -- List with project scope
  • "Is the beta-dashboard flag enabled?" -- Get flag details with environment

Performance Notes

  • Verify the flag identifier and environment before toggling. Toggling the wrong flag can cause production issues.
  • List existing flags before creating to avoid duplicates.
  • Confirm the flag type (boolean vs. multivariate) matches the intended use case.

Troubleshooting

Flag Not Toggling

  • The environment parameter is required for toggle -- specify which environment to target
  • Verify the flag identifier is correct (case-sensitive)
  • Check that the flag exists in the target project

Flag Not Found

  • Identifiers are project-scoped -- confirm the correct org_id and project_id
  • Use harness_list without filters to see all flags, then narrow down

Boolean vs Multivariate

  • Use boolean for simple on/off flags
  • Use multivariate when you need multiple string/number/JSON variations

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free