smd-release SKILL.md skillA
smd-release from bislink360/semantic-markdown is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bislink360/semantic-markdown/smd-release@git:20261107.72759d3Pins git:20261107.72759d3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bislink360/semantic-markdown
- Path
.claude/skills/smd-release/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261107.72759d3, committed Nov 7, 2026
- First version recorded
- Oct 22, 2026
- Size
- 17,455 bytes
- Repository stars
- 3
- License
- MIT
Branch, version, verify and publish Semantic Markdown releases (VS Code extension, npm package `semantic-markdown`, agent skills, GitHub release) without breaking existing users. Use this skill for any change destined for the public bislink360/semantic-markdown repository — starting a feature or fix branch, preparing or reviewing a pull request, bumping versions, writing the changelog, checking backward compatibility, tagging, or publishing to the VS Code Marketplace, Open VSX, npm or GitHub…
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
# Releasing Semantic Markdown One repository ships four artifacts that must stay in lockstep: | Artifact | Where | Version source | |---|---|---| | VS Code extension `bislink360.semantic-markdown` | VS Code Marketplace, Open VSX + `.vsix` on GitHub Releases | `extension/package.json` | | npm package `semantic-markdown` (library + `smd` CLI) | npmjs.com | `npm/package.json` (same version) | | Agent skills `semantic-markdown-reader` / `-writer` | `skills/`, zips on GitHub Releases | bundle the CLI, so they follow the same version | | Format spec | `smd: 2` in new documents (`smd: 1` documents keep the v1 rules) | `SMD_VERSION` in `extension/src/core/spec.ts`; changes only for format-breaking releases | Existing documents, CI pipelines (`smd validate`), library users and agents all depend on today's behaviour. **The primary goal of this process is that nothing breaks silently.** Every incompatible change is found by the checker, called out to the human, and shipped only as a major version. ## Workflow ### 1. Branching: follow the release train (version-control skill) Branches follow the **version-control** skill's release train: …
Read the whole file at its exact version.
How to install
mdr add bislink360/semantic-markdown/smd-release@sha256:c0953e6ac36a2af4The line at the top of this page pins the label git:20261107.72759d3, 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_2ln4h7na5l2pdbo4)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 22, 2026 and Nov 7, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.72759d3 latest | 2026-11-07 | 72759d3 | 17,455 B | A | view · diff |
| git:20261105.251a34f | 2026-11-05 | 251a34f | 17,435 B | A | view · diff |
| git:20261031.87b660a | 2026-10-31 | 87b660a | 17,387 B | A | view · diff |
| git:20261031.2ff6a0e | 2026-10-31 | 2ff6a0e | 16,498 B | A | view · diff |
| git:20261022.2184a11 | 2026-10-22 | 2184a11 | 16,230 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 (17455 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
bislink360/semantic-markdown · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ln4h7na5l2pdbo4 GET https://markdownregistry.com/api/v1/resolve?ref=bislink360/semantic-markdown/smd-release GET https://markdownregistry.com/api/v1/blob/c0953e6ac36a2af4306e23468717d9d89192edc5286645d107bf741ee4733923
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 bislink360/semantic-markdown
Every file in bislink360/semantic-markdown