Home / beakpoint-insights / roost · GitHub

release-notes SKILL.md skillA

release-notes from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add beakpoint-insights/roost/release-notes@git:20261028.9770e89

Pins git:20261028.9770e89 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: beakpoint-insights/roost
Path: skills/release-notes/SKILL.md
Versions recorded: 5
Latest version: git:20261028.9770e89, committed Oct 28, 2026
First version recorded: Oct 27, 2026
Size: 23,629 bytes
Repository stars: 30
License: MIT

Draft customer-facing release notes for an epic that has shipped, ready to paste, one note per feature it shipped (usually one). Dates each note by when customers could first use the feature (the production deploy, release or merge that first carried its last change, shown in an evidence table), never by the tracker's resolution date; writes only what the slices built, listing anything cut; holds a note customers can't use yet (a feature flag, a slice not yet live, a correction to past data…

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 Notes

A release note is public, and hard to take back once it's out. Each one has to be dated by when customers could actually use the feature, describe what was built (not what was planned), and leave anything the evidence doesn't say for the user to fill in. This skill gathers that evidence and drafts the note; the user publishes it.

**First, load the team config with `roost-config`,** and read its tracker adapter.

**Input:** the epic's key. Everything below calls it EPIC. Or a date, for everything released since then: see "Catch-up since a date" at the end, which runs steps 1 to 7 for each epic it finds.

**Evidence the user gives counts.** When the user has already given you facts (the tickets, the PRs, the deploy runs, a page's text), use them as read, and don't look them up again. Look up only what's missing. Whatever you couldn't read, from the user or the tools, goes in the checks (step 7), named.

**Never publish or post anything:** no tracker comments, no status changes, no posts. The reply is the draft.

## 1. Find the work
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add beakpoint-insights/roost/release-notes@sha256:a261736afe899a1d

The line at the top of this page pins the label git:20261028.9770e89, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_m4tfwdneusxbqe34.svg)](https://markdownregistry.com/a/art_m4tfwdneusxbqe34)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Oct 27, 2026 and Oct 28, 2026, more than one a day.

version	committed	commit	size	audit
git:20261028.9770e89 latest	2026-10-28	9770e89	23,629 B	A	view · diff
git:20261028.6011678	2026-10-28	6011678	23,528 B	A	view · diff
git:20261028.fe7bbe6	2026-10-28	fe7bbe6	22,627 B	A	view · diff
git:20261028.e72091c	2026-10-28	e72091c	18,693 B	A	view · diff
git:20261027.599bb58	2026-10-27	599bb58	18,571 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (23629 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

GitHub

beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_m4tfwdneusxbqe34
GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/release-notes
GET https://markdownregistry.com/api/v1/blob/a261736afe899a1dad389602cdf9ddaec99cf04e05b6842399828a5414daebc4

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 beakpoint-insights/roost

automate-tests SKILL.md skill

beakpoint-insights/roost · skills/automate-tests/SKILL.md · Automate the tests linked to a story or slice. Read each test's scenarios, find which already have automation, write…