Individual skill
runtime-config-flagd
Feature flag management via flagd (OpenFeature). Use to list, inspect, and toggle feature flags in the OTel Demo environment. Flags control incident injection scenarios (payment failures, CPU spikes, memory leaks, etc.) and can be toggled for remediation.
sre-agent/.claude/skills/runtime-config-flagd/SKILL.md
Source commit 2323af0551856ff4669b73dc36329d16aa19ed24
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 179
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-sre Repository topic
- site-reliability-engineering Repository topic
- ai-agent Repository topic
- devops Repository topic
- episodic-memory Repository topic
- incident-investigation Repository topic
- incident-response Repository topic
- knowledge-graph Repository topic
- sre-agent Repository topic
- self-hosted Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesSKILL.mdcore · 7,013 bytesscripts/__init__.pyruns · 39 bytesscripts/flagd_client.pyruns · 7,850 bytesscripts/get_flag.pyruns · 1,585 bytesscripts/list_flags.pyruns · 3,118 bytesscripts/list_scenarios.pyruns · 8,457 bytesscripts/set_flag.pyruns · 1,951 bytes
Read excerpt
# Feature Flag Management (flagd)
## How It Works
The OpenTelemetry Demo uses [flagd](https://flagd.dev/) as its feature flag provider. Flags are stored in a Kubernetes ConfigMap and loaded by the flagd service. Services check flags at runtime via the OpenFeature SDK to decide whether to inject failures.
**Flag lifecycle:**
1. Flag definitions live in a ConfigMap (`flagd-config` in `otel-demo` namespace)
2. flagd watches the ConfigMap and hot-reloads on changes
3. Services evaluate flags via gRPC and behave accordingly
4. To remediate an incident, set the flag's default variant to `off`
## Available Scripts
