release SKILL.md skillA
release from sshadows/lethal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sshadows/lethal/release@git:20261021.98334d7Pins git:20261021.98334d7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sshadows/lethal
- Path
.claude/skills/release/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261021.98334d7, committed Oct 21, 2026
- First version recorded
- Aug 17, 2026
- Size
- 10,171 bytes
- Repository stars
- 10
- License
- MIT
Cut a LethAL release end to end — version bump, CHANGELOG section, README version references, the local and live gates, then the tag that triggers .github/workflows/release.yml. Use when asked to cut, tag, ship or publish a release, to bump the version, or when a release draft needs finishing. Covers the Azure Trusted Signing setup for the Windows binary and the two things the workflow deliberately leaves to a human.
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
# Cutting a release
LethAL ships as a **standalone compiled binary**, not an npm package. A release is one git tag; the
tag triggers `.github/workflows/release.yml`, which builds five targets, signs the Windows one, and
opens a **draft** GitHub release. `docs/releasing.md` is the reference for what the build produces
and why; this skill is the order of operations.
**The tag is the trigger, not the source of truth.** The root `package.json` `version` is, and
`scripts/build-binary.ts` stamps it into every filename. The workflow refuses a tag that disagrees
with it, so a mismatch fails in seconds rather than shipping filenames that contradict the tag.
## Order, and why it is this order
Everything that can fail locally fails locally. The tag is last, because a pushed tag is the one
step that is annoying to undo.
### 1. Decide the version
Read the current one and the last released section:
```bash
bun --print 'require("./package.json").version'
grep -n "^## \[" CHANGELOG.md | head -5
```
If the current version already has a dated `## [x.y.z]` section, it was cut before — **bump**, do
not reuse it. Reusing a released version relabels work that shipped under a different number.
…Read the whole file at its exact version.
How to install
mdr add sshadows/lethal/release@sha256:bcf9483688371b79The line at the top of this page pins the label git:20261021.98334d7, 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_mspughifj2tl5she)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 17, 2026 and Oct 21, 2026, about one every 32 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.98334d7 latest | 2026-10-21 | 98334d7 | 10,171 B | A | view · diff |
| git:20260818.afe3aa8 | 2026-08-18 | afe3aa8 | 10,149 B | A | view · diff |
| git:20260817.2f452db | 2026-08-17 | 2f452db | 8,553 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 (10171 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
sshadows/lethal · 10 stars · license MIT · pushed 2026-11-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_mspughifj2tl5she GET https://markdownregistry.com/api/v1/resolve?ref=sshadows/lethal/release GET https://markdownregistry.com/api/v1/blob/bcf9483688371b79733fba034eba6038ba4f7cb1c916ffea07f7175b372eae12
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.