cs-release-readiness-brief SKILL.md skillA
cs-release-readiness-brief from polar-bear-org/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add polar-bear-org/claude-skills/cs-release-readiness-brief@git:20261026.a2f0899Pins git:20261026.a2f0899 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- polar-bear-org/claude-skills
- Path
packs/ai-for-customer-service-pack/skills/cs-release-readiness-brief/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,042 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Prepares a release readiness brief for support before a product change ships, with a change table, the questions customers will ask, day-one saved replies and article updates, launch contacts and a go or hold check. Use for "run cs-release-readiness-brief", "release readiness", "support launch brief", "product changed and support was not told", "prepare support for a release", "launch readiness checklist for support", "day one support kit", part of the AI for Customer Service Pack by 90n.
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
# Release Readiness Brief ## When To Use Product ships changes without telling support and confused tickets flood in. Agents learn about the new pricing page from the first angry customer, and nobody knows who in product can answer. Use this to answer: is support ready for this change on day one, and if not, what is missing before it ships. ## When Not To Use If the change has already gone wrong and customers are affected now, use Incident Communication Plan; readiness is for planned change, not unplanned failure. For a single new answer with no wider change, write it straight into Canned Responses Library. ## Inputs - Release notes, a ticket from product or engineering, or a plain description of the change - The release date and who is affected (plans, regions, channels) - Your current saved replies and help articles on the area If you have none of this, I start from a one-line description of the change and mark the output as a first draft. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/cs-release-readiness-brief@sha256:552fef881969a814The line at the top of this page pins the label git:20261026.a2f0899, 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_cd7hsrsqgo553pus)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 27, 2026 and Oct 26, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.a2f0899 latest | 2026-10-26 | a2f0899 | 5,042 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 4,994 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 (5042 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
polar-bear-org/claude-skills · 51 stars · license a license file GitHub does not identify · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cd7hsrsqgo553pus GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-release-readiness-brief GET https://markdownregistry.com/api/v1/blob/552fef881969a81457ddaa05fbed8d5d9031adeb45c2efa1845c4f4f3c2fd02a
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.