creating-releases-json SKILL.md skillA
creating-releases-json from buildinternet/releases is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add buildinternet/releases/creating-releases-json@git:20261003.af6e332Pins git:20261003.af6e332 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- buildinternet/releases
- Path
skills/creating-releases-json/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261003.af6e332, committed Oct 3, 2026
- First version recorded
- Jul 8, 2026
- Size
- 18,064 bytes
- Repository stars
- 13
- License
- Apache-2.0
Create or update a releases.json manifest so registries and agents can find where a company or project publishes its release notes. Use this whenever someone wants to "list our product on Releases", "add a releases.json", "get indexed on Releases Index", "here's our website, make us a manifest", declare a changelog / updates page / RSS feed / GitHub releases / App Store listing / CHANGELOG for discovery, publish a /.well-known/releases.json, or edit an existing one — even if they don't say…
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
# Creating a releases.json manifest
`releases.json` is a small, owner-declared file that states **what products a
company ships and where it publishes release notes** — a changelog, an updates
page, an RSS/Atom feed, GitHub Releases, an App Store listing, or a hosted
`CHANGELOG` file. Any registry or agent that reads the format (starting with
[releases.sh](https://releases.sh)) learns where the release notes live directly
from the owner instead of guessing.
**Authority comes from where the file lives, not from what it claims.** A file at
`https://{domain}/.well-known/releases.json` speaks for that whole company; a
`releases.json` at a repository root speaks only for that repo. That is the entire
trust model — if you can publish the file at the URL, you can declare what it says.
Your job with this skill: figure out which scope applies, discover the locations
where release notes **actually** live (never invent them), model the company's
products without over-fragmenting, write a correctly-shaped file, validate it, and
help get it published.
## How you'll be asked to run this
Most of the time there is **no codebase** — someone just says *"here's our website,
…Read the whole file at its exact version.
How to install
mdr add buildinternet/releases/creating-releases-json@sha256:4da87e0a6ebfb4eaThe line at the top of this page pins the label git:20261003.af6e332, 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_7vznb7vnu57bgn7d)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 8, 2026 and Oct 3, 2026, about one every 43 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.af6e332 latest | 2026-10-03 | af6e332 | 18,064 B | A | view · diff |
| git:20261002.5caeb2c | 2026-10-02 | 5caeb2c | 18,058 B | A | view · diff |
| git:20260708.3a7015f | 2026-07-08 | 3a7015f | 16,191 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 (18064 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
buildinternet/releases · 13 stars · license Apache-2.0 · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7vznb7vnu57bgn7d GET https://markdownregistry.com/api/v1/resolve?ref=buildinternet/releases/creating-releases-json GET https://markdownregistry.com/api/v1/blob/4da87e0a6ebfb4ea59307e3cb9b9522014cbfcffa66d171f2fc2d391da853d1a
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.