pooled-release SKILL.md skillA
pooled-release from stealth-factory/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stealth-factory/skills/pooled-release@v1.2.1Pins v1.2.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stealth-factory/skills
- Path
skills/pooled-release/SKILL.md- Versions recorded
- 4
- Latest version
- v1.2.1, committed Aug 15, 2026
- First version recorded
- Jun 27, 2026
- Size
- 9,576 bytes
- Repository stars
- 5
- License
- MIT
Cut fewer, batched releases (a 'release train') instead of one per merge — by triggering semantic-release on demand or on a cadence rather than on every push to main. Use when releasing on every merge is too noisy, when you want one larger readable changelog per release, to add a manual 'cut a release' button (workflow_dispatch) or a scheduled/weekly release, to set up prerelease channels (next/beta → promote to stable), or when deciding whether you need a release branch.
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
# Pooled releases (release trains) Release on every merge is great for a fast-moving lib, but sometimes you want **fewer, fatter releases** — one readable changelog per cut, not a version bump per PR. For the manual and scheduled models it does that **without changing how you develop** — it only changes the release **trigger** (the prerelease-channel model in Model 3 does shift where you target work; see there). It builds directly on [`semantic-release-automation`](../semantic-release-automation/SKILL.md) — same plugin pipeline, same Conventional Commits; read that first. ## The key idea: decouple *merge* from *release* Trunk-based development still wants frequent small merges to `main` — that's unchanged, so **dev velocity and PR flow don't change**. The only thing you move is **when a release is published**: | | Trigger | Result | | --- | --- | --- | | **Per-merge (default)** | `on: push: [main]` | a release every qualifying merge — many small ones | | **Pooled (this skill)** | `workflow_dispatch` and/or `schedule` | semantic-release batches **all** commits since the last tag into **one** release | …
Read the whole file at its exact version.
How to install
mdr add stealth-factory/skills/pooled-release@sha256:b89ad0992b108a70The line at the top of this page pins the label v1.2.1, 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_i52z2gh5xb6sahxf)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 27, 2026 and Aug 15, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.1 latest | 2026-08-15 | 9b11598 | 9,576 B | A | view · diff |
| v1.2.1 | 2026-07-02 | fb71220 | 9,575 B | A | view · diff |
| v1.1.0 | 2026-06-28 | 883cd1d | 8,303 B | A | view · diff |
| v1.0.0 | 2026-06-27 | 1d13d5e | 7,845 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 (9576 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
stealth-factory/skills · 5 stars · license MIT · pushed 2026-10-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i52z2gh5xb6sahxf GET https://markdownregistry.com/api/v1/resolve?ref=stealth-factory/skills/pooled-release GET https://markdownregistry.com/api/v1/blob/b89ad0992b108a70927c72a3b4e55b4b69442a3119dd83681174f439b3457e2c
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.