cockpit-changelog SKILL.md skillA
cockpit-changelog from surething-io/cockpit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add surething-io/cockpit/cockpit-changelog@git:20260829.57c4561Pins git:20260829.57c4561 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- surething-io/cockpit
- Path
docs/skills/cockpit-changelog/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260829.57c4561, committed Aug 29, 2026
- Size
- 5,456 bytes
- Repository stars
- 44
- License
- MIT
Draft user-facing GitHub release notes for Cockpit from a commit range, in the project's existing voice. Output is markdown ready to paste into `gh release edit --notes-file`.
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
You are drafting GitHub release notes for **Cockpit** (`@surething/cockpit`). The audience is engineers who installed the npm package or who land on the GitHub release page from social — **not** contributors reading a commit log. You write release notes in the existing project voice. Get the voice from samples first; never improvise. ## Inputs - `$ARGUMENTS` — `from-tag to-tag`. If absent, default to `from = previous tag`, `to = HEAD`. Resolve concretely: ```bash CUR=$(git describe --tags --abbrev=0) # or arg 2 PREV=$(git describe --tags --abbrev=0 "$CUR^") # or arg 1 ``` ## Step 1 — Read the actual commits ```bash git log "$PREV..$CUR" --pretty=format:'%h %s%n%b%n---' ``` Read every commit body, not just the title. The titles are conventional-commits style (`feat(scope):`, `fix(ui):`, `docs:`, `chore(deps):`); the bodies often hold the user-facing rationale that belongs in the notes. ## Step 2 — Read the project's voice (REQUIRED) Pull two recent hand-authored release notes as style references: ```bash gh release view v1.0.195 --repo Surething-io/cockpit --json body --jq .body …
Read the whole file at its exact version.
How to install
mdr add surething-io/cockpit/cockpit-changelog@sha256:ef6745557b850aa3The line at the top of this page pins the label git:20260829.57c4561, 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_egdx2ykh4ndedl3e)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 29, 2026.
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 (5456 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
surething-io/cockpit · 44 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_egdx2ykh4ndedl3e GET https://markdownregistry.com/api/v1/resolve?ref=surething-io/cockpit/cockpit-changelog GET https://markdownregistry.com/api/v1/blob/ef6745557b850aa379d695ee28e845f487a51c217cc9b71d10cad68e223affc9
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.