launchdarkly-release-plans SKILL.md skillB
launchdarkly-release-plans from launchdarkly/ai-tooling is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add launchdarkly/ai-tooling/launchdarkly-release-plans@v1.2.0Pins v1.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- launchdarkly/ai-tooling
- Path
skills/release-autopilot/launchdarkly-release-plans/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.0, committed Nov 18, 2026
- First version recorded
- Nov 13, 2026
- Size
- 31,304 bytes
- Repository stars
- 31
- License
- a license file GitHub does not identify
List, create, edit, make default, and delete LaunchDarkly release plans of both kinds: environment release plans (one environment's phases, rollout steps, and rollback metrics, with starter plans) and flag release plans (a project's environments in release order, each with its environment release plan, which Release Autopilot proposes releases from on pull requests). Also starts a flag's release from a flag release plan. Use when the user wants to see, list, build, change, or remove a release…
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
# LaunchDarkly Release Plans You're using a skill that reads and changes LaunchDarkly release plans. There are two kinds: - An **environment release plan** releases a flag in one environment: its phases, rollout steps, holds, and rollback metrics. A plan with metrics is guarded, so a regression can roll the release back. A plan without metrics is progressive. Each environment can have one default plan. - A **flag release plan** is project-level. It lists the project's environments in release order, and names the environment release plan each one releases with (or says the environment releases immediately). When Release Autopilot proposes a release on a pull request, it uses the project's flag release plans, and it proposes none when the project has none. A project can have one default flag release plan. A project does not need one to release: the `flag-release` skill starts a flag's release from the flag release plan with `create-flag-release` when there is one to use, and otherwise from each environment's release plan with `create-automated-rollout-config` (the environment's default, or the plan that `environmentReleasePlanKey` names). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kvcfj7juyix23ucb/8b0ff3d2acabe37a143e866a26b4f00fa94641acd0e821fb3e10ef3923588757.json
Then /plugin install launchdarkly-release-plans@markdownregistry-kvcfj7juyix23ucb in Claude Code. It installs v1.2.0, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add launchdarkly/ai-tooling/launchdarkly-release-plans@sha256:8b0ff3d2acabe37aThe line at the top of this page pins the label v1.2.0, 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_kvcfj7juyix23ucb)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in launchdarkly/ai-tooling/launchdarkly-release-plans since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of launchdarkly-release-plans from somewhere else? Ask it: where did my launchdarkly-release-plans come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 13, 2026 and Nov 18, 2026, about one every day. Its first recorded version is graded A and its latest B.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-11-18 | c113191 | 31,304 B | B | view · diff |
| v1.1.2 | 2026-11-17 | 601d84e | 30,580 B | B | view · diff |
| v1.1.1 | 2026-11-14 | 1f59b83 | 28,355 B | B | view · diff |
| v1.0.1 | 2026-11-13 | 94c75aa | 20,864 B | A | view · diff |
| v1.0.0 | 2026-11-13 | 3cd1606 | 19,857 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/launchdarkly-release-plans/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No prompt-injection phrasing (matched: Do not tell the user)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (31304 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
launchdarkly/ai-tooling · 31 stars · license a license file GitHub does not identify · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kvcfj7juyix23ucb GET https://markdownregistry.com/api/v1/resolve?ref=launchdarkly/ai-tooling/launchdarkly-release-plans GET https://markdownregistry.com/api/v1/blob/8b0ff3d2acabe37a143e866a26b4f00fa94641acd0e821fb3e10ef3923588757
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.