release SKILL.md skillA
release from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/release@git:20261106.96eea03Pins git:20261106.96eea03 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/release/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261106.96eea03, committed Nov 6, 2026
- First version recorded
- Oct 1, 2026
- Size
- 10,254 bytes
- Repository stars
- 12
- License
- MIT
Run a team release: assemble the change list from the diff, write release notes for the audience that reads them, produce the pre-flight and post-deploy checklist with an owner per step, state the rollback path, audit the licenses of the dependencies it ships against the project's own policy, and record who approved the go decision. Use before deploying to staging or production, when cutting a version, when writing notes for a client, or when the licenses of what a release ships need checking.…
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 Management (`atk:release`) Turns a set of merged commits into a release a team can execute at a known hour with a known way back. The rollback path is written before the deploy, not improvised during it. ## Scope Handles: collecting the change list from git and the tracker, writing release notes per audience, building the checklist with owners and timings, listing migrations and config changes, the license audit of the dependencies it ships, stating the rollback path, and recording the go or no-go decision. Does NOT handle: executing the deployment, which the pipeline and SRE own; testing (`atk:qa`); or handling a failed release, which is `atk:incident`. ## Roles PM owns the go decision and the client communication. SRE owns execution and the rollback. QA signs off the test result. Tech Lead signs off the technical risk. See `shared/team-roles.md`. ## Invocation ```bash /atk:release <version> # Full release artifact for a version /atk:release v1.3.0..HEAD # Build from an explicit tag or commit range /atk:release --notes --audience client # Client-facing notes only, no internal detail …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/release@sha256:5e790301d9fc3170The line at the top of this page pins the label git:20261106.96eea03, 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_maum63byqw2m2vkh)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 1, 2026 and Nov 6, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.96eea03 latest | 2026-11-06 | 96eea03 | 10,254 B | A | view · diff |
| git:20261105.568f91a | 2026-11-05 | 568f91a | 10,403 B | A | view · diff |
| git:20261022.a5e6ec1 | 2026-10-22 | a5e6ec1 | 10,213 B | A | view · diff |
| git:20261016.18521b0 | 2026-10-16 | 18521b0 | 9,990 B | A | view · diff |
| git:20261014.03c655e | 2026-10-14 | 03c655e | 9,285 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 9,076 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 (10254 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
lamngockhuong/aiteamkit · 12 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_maum63byqw2m2vkh GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/release GET https://markdownregistry.com/api/v1/blob/5e790301d9fc317049ce74aed17d91a8b574990396eb6e303af0c4e48202f8ac
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 lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit