sync-docs-release SKILL.md skillA
sync-docs-release from richkuo/rk-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add richkuo/rk-skills/sync-docs-release@git:20261006.4c6da76Pins git:20261006.4c6da76 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- richkuo/rk-skills
- Path
skills/sync-docs-release/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261006.4c6da76, committed Oct 6, 2026
- First version recorded
- Jul 4, 2026
- Size
- 3,390 bytes
- Repository stars
- 50
- License
- MIT
Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs (which lands its edits through its own docs PR) → optional merge of that PR → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release", "update docs and publish a release".
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
# sync-docs-release Runs three operations in strict sequence, all in the main session. Do not skip steps or reorder them, and do not delegate any step to a subagent. ## Step 1 — Sync docs Invoke the `sync-docs` skill via the Skill tool and follow it to completion here, passing the user's request plus any session context (target branch, last-sync SHA, specific files). sync-docs works in its own worktree off the latest `origin/<default>` and ends with either "no doc changes" or an open docs PR. Summarize the doc edits and the PR for the user before proceeding. ## Step 2 — Decide how the docs PR relates to the release If sync-docs reported no doc changes, go straight to Step 3. When the caller's approved plan already authorizes the docs-sync PR and its merge (as the `milestone-workflow` close-out does with merging on), take the merge-then-release choice below without asking. Otherwise ask the user once (AskUserQuestion) how Step 3 should relate to it: - **Merge the doc PR once its checks pass, then release from the updated default branch** (recommend this one). - **Release now without the doc changes**, leaving the PR open. - **Stop here** with no release. …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/sync-docs-release@sha256:facf6e972eb71416The line at the top of this page pins the label git:20261006.4c6da76, 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_nctb6aqcay7kp5wz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 4, 2026 and Oct 6, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.4c6da76 latest | 2026-10-06 | 4c6da76 | 3,390 B | A | view · diff |
| git:20260929.e22e7d7 | 2026-09-29 | e22e7d7 | 3,751 B | A | view · diff |
| git:20260808.d2de7e3 | 2026-08-08 | d2de7e3 | 4,701 B | A | view · diff |
| git:20260728.e421935 | 2026-07-28 | e421935 | 5,060 B | A | view · diff |
| git:20260724.bd6a02a | 2026-07-24 | bd6a02a | 5,412 B | A | view · diff |
| git:20260704.c7939e4 | 2026-07-04 | c7939e4 | 2,468 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 (3390 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
richkuo/rk-skills · 50 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nctb6aqcay7kp5wz GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/sync-docs-release GET https://markdownregistry.com/api/v1/blob/facf6e972eb7141676a9eebdd4fd2e8eeab59d88b35b68995a033f4024bd4110
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.