release-docs SKILL.md skillA
release-docs from seedcord/seedcord is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add seedcord/seedcord/release-docs@git:20261020.e57e1e6Pins git:20261020.e57e1e6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- seedcord/seedcord
- Path
.agents/skills/release-docs/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.e57e1e6, committed Oct 20, 2026
- Size
- 4,577 bytes
- Repository stars
- 26
- License
- Apache-2.0
Bring every user-facing surface up to date for a seedcord release (changesets, READMEs, the home page, then the guide). A maintainer-run job across one main session, helper sessions, and Sonnet subagents.
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 docs A release changes what users can do. This run makes every surface a user reads say so: the changesets, the READMEs, the home page, and the guide. Run it on the release branch once the code is done. The maintainer judges everything a user reads. You do the legwork, ground every claim, and hand each phase over staged. ## Setup 1. Make a sibling worktree off local `next`, like `git worktree add -b docs-refresh ../docs-refresh next`, with the sandbox off. Open it with `code ../docs-refresh`, also outside the sandbox. 2. `pnpm install`, then build what each phase needs. The home site needs `pnpm turbo run build --filter='./apps/home^...'` before `next dev` starts. 3. Load the four skills `AGENTS.md` lists, plus `guide-voice` and `changeset-guidelines`. 4. Start a guide notes file in the session scratchpad. Every fact cut from a README or the home page goes in it, with the guide page it belongs on. The guide phase reads it. Done when the worktree builds and the notes file exists. ## The run Run the phases in this order. Each one ends when the maintainer commits it, and the next one reads what the last one settled. …
Read the whole file at its exact version.
How to install
mdr add seedcord/seedcord/release-docs@sha256:ba5ef5e0d8ca5514The line at the top of this page pins the label git:20261020.e57e1e6, 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_unaipuzqlv3vvrhv)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 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 (4577 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
seedcord/seedcord · 26 stars · license Apache-2.0 · pushed 2026-10-22 · branch next
API
GET https://markdownregistry.com/api/v1/artifacts/art_unaipuzqlv3vvrhv GET https://markdownregistry.com/api/v1/resolve?ref=seedcord/seedcord/release-docs GET https://markdownregistry.com/api/v1/blob/ba5ef5e0d8ca5514d2c7fccfc23acaad73e15b06c3145fe1638b952f6e9a9203
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 seedcord/seedcord
Every file in seedcord/seedcord