feature-flags SKILL.md skillA
feature-flags from skillmedev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillmedev/skills/feature-flags@git:20261005.bea4ea5Pins git:20261005.bea4ea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillmedev/skills
- Path
skills/feature-flags/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.bea4ea5, committed Oct 5, 2026
- First version recorded
- Jul 5, 2026
- Size
- 7,271 bytes
- Repository stars
- 19
- License
- MIT
Designs feature-flag systems and lifecycle policy - flag taxonomy (release, ops/kill-switch, experiment, permission), percentage rollouts with stable bucketing, safe defaults, and mandatory removal deadlines so flags don't rot into dead code. Use when someone asks "how should I roll this out behind a flag", "kill switch vs feature flag", "how do I do a percentage rollout", "we have hundreds of stale flags", or is wiring up LaunchDarkly or a homegrown flag service. Do NOT use for designing the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Feature Flags Flags decouple deploy from release: code ships dark and turns on safely, in stages, with an instant off switch. The costly mistake this skill prevents is flag debt - every flag is a fork in your codebase that doubles the test matrix, and a flag without an owner and a removal deadline set at creation becomes permanent dead code that someone flips three years later during an incident with no idea what it does. ## Operating procedure ### Step 1: Gather inputs Before creating any flag, collect: 1. Purpose - which of the four types below it is. If the answer is "two of them", that is two flags. 2. Blast radius if the new path misbehaves (cosmetic / degraded / data-corrupting / revenue-affecting). 3. Bucketing key - usually user id; sometimes account id so a whole team sees one variant. 4. Owner (a person, not a team) and the removal condition. 5. Safe default - the value served if the flag service is unreachable. ### Step 2: Classify the flag - lifecycle follows type - Release flag: gates unfinished or risky features during rollout. Lifetime: days to weeks. Removal deadline set at creation, maximum 90 days out; most should die within 30 days of full rollout. …
Read the whole file at its exact version.
How to install
mdr add skillmedev/skills/feature-flags@sha256:e9a7706784cce632The line at the top of this page pins the label git:20261005.bea4ea5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3vvg6n75jjbwbvo2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 5, 2026 and Oct 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.bea4ea5 latest | 2026-10-05 | bea4ea5 | 7,271 B | A | view · diff |
| git:20260705.a28c4ce | 2026-07-05 | a28c4ce | 7,236 B | A | view · diff |
| git:20260705.acb5571 | 2026-07-05 | acb5571 | 7,290 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7271 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
skillmedev/skills · 19 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3vvg6n75jjbwbvo2 GET https://markdownregistry.com/api/v1/resolve?ref=skillmedev/skills/feature-flags GET https://markdownregistry.com/api/v1/blob/e9a7706784cce632539c221cb078fb6365bcc3decedd5b798cd24a28b27e7627
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from skillmedev/skills
Every file in skillmedev/skills