semantic-release-beta SKILL.md skillA
semantic-release-beta from oleg-koval/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add oleg-koval/agent-skills/semantic-release-beta@git:20260903.188b1cePins git:20260903.188b1ce in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- oleg-koval/agent-skills
- Path
plugins/olko-release/skills/semantic-release-beta/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260903.188b1ce, committed Sep 3, 2026
- First version recorded
- Aug 24, 2026
- Size
- 2,733 bytes
- Repository stars
- 3
- License
- MIT
Set up or repair a Node.js release pipeline built on semantic-release-npm-github-publish, with a stable channel on main and a prerelease channel on a beta branch, including the GitHub Actions validation and npm publishing behaviour. Use when the user wants "semantic release set up", "a beta release channel", "prerelease publishing", "automated npm publishing", or when an npm package's releases are still manual and should become commit-driven. For writing the notes of a single release use…
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
# semantic-release-beta
Use this skill when a project needs a reusable beta prerelease workflow with:
- `semantic-release`
- `semantic-release-npm-github-publish`
- GitHub Actions
- a stable `main` branch
- a prerelease `beta` branch
- npm publishing with `beta` prerelease versions
- changelog generation, GitHub releases, npm publishing, and release commits through the maintained preset
## Trigger phrases
- add a beta release workflow
- publish prereleases from a `beta` branch
- set up `semantic-release` with `main` and `beta`
- use `semantic-release-npm-github-publish`
- add release validation or dry-run checks in CI
## Workflow
1. Inspect the repository first.
2. Install or update `semantic-release`, `semantic-release-npm-github-publish`, and the peer plugins expected by the preset.
3. Configure the repo-local semantic-release file to extend `semantic-release-npm-github-publish` and set branches explicitly:
- `main` for stable releases
- `{ name: "beta", channel: "beta", prerelease: "beta" }` for prereleases
4. Add scripts if missing:
- `semantic-release`: `semantic-release`
- `release:dry-run`: `semantic-release --dry-run --no-ci`
…Read the whole file at its exact version.
How to install
mdr add oleg-koval/agent-skills/semantic-release-beta@sha256:e4464d5b63312189The line at the top of this page pins the label git:20260903.188b1ce, 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_hjxzcslsyzu3xhbi)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 24, 2026 and Sep 3, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.188b1ce latest | 2026-09-03 | 188b1ce | 2,733 B | A | view · diff |
| git:20260824.c71bceb | 2026-08-24 | c71bceb | 2,435 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 (2733 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
oleg-koval/agent-skills · 3 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hjxzcslsyzu3xhbi GET https://markdownregistry.com/api/v1/resolve?ref=oleg-koval/agent-skills/semantic-release-beta GET https://markdownregistry.com/api/v1/blob/e4464d5b6331218976619890e12df97b64cdcacb3e8376dfe425737a93ecffcc
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 oleg-koval/agent-skills
Every file in oleg-koval/agent-skills