clud-tag-release SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
clud-tag-release from talos-hq/clud is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add talos-hq/clud/clud-tag-release@git:20261028.1d1ca1cPins git:20261028.1d1ca1c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- talos-hq/clud
- Path
crates/clud-bin/assets/skills/clud-tag-release/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261028.1d1ca1c, committed Oct 28, 2026
- First version recorded
- Jun 3, 2026
- Size
- 8,676 bytes
- Repository stars
- 16
- License
- a license file GitHub does not identify
Tag a release and let the auto-release workflow build it. Validates version match, clean main, no duplicate tag — then pushes the tag and surfaces the workflow URL.
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
<!-- managed-by: clud --> # /clud-tag-release Tag a release the way `zackees/zccache` does it: the tag is the trigger, the workflow does the rest. Five hard rules: 1. **Tag must equal workspace version.** Read the version from `Cargo.toml [workspace.package].version` (workspace) or `Cargo.toml [package].version` (single crate) or `pyproject.toml [project].version`. The tag pushed must match — `1.2.3` and `v1.2.3` are both fine, but `1.2.3` ≠ `1.2.4`. If they don't match, stop and tell the user to bump first; do not silently retag. 2. **Tag from clean default branch only.** Working tree clean, on `main`/`master`, in sync with `origin`. Never tag from a feature branch or a dirty tree. 3. **No duplicates.** Tag must not exist locally or on origin; no GitHub release record for that tag yet. If it does, stop — re-tagging a published release is destructive. 4. **Push the tag — don't `gh release create`.** `gh release create` creates the release record directly and bypasses the auto-release workflow's preflight (version validation, idempotency check, registry skip-existing). The deliverable is an annotated tag pushed to origin; the workflow does everything else. …
Read the whole file at its exact version.
How to install
mdr add talos-hq/clud/clud-tag-release@sha256:9d6a928d7c3817b0The line at the top of this page pins the label git:20261028.1d1ca1c, 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_qzg5x74u343sg5lc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 3, 2026 and Oct 28, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.1d1ca1c latest | 2026-10-28 | 1d1ca1c | 8,676 B | A | view · diff |
| git:20261027.e9c13ee | 2026-10-27 | e9c13ee | 8,279 B | A | view · diff |
| git:20261016.9e7b69e | 2026-10-16 | 9e7b69e | 8,245 B | A | view · diff |
| git:20260812.7b95cc6 | 2026-08-12 | 7b95cc6 | 7,633 B | A | view · diff |
| git:20260807.dd89e45 | 2026-08-07 | dd89e45 | 8,087 B | A | view · diff |
| git:20260605.a6a1dc4 | 2026-06-05 | a6a1dc4 | 8,090 B | A | view · diff |
| git:20260603.6f93a5c | 2026-06-03 | 6f93a5c | 7,743 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 (8676 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
talos-hq/clud · 16 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qzg5x74u343sg5lc GET https://markdownregistry.com/api/v1/resolve?ref=talos-hq/clud/clud-tag-release GET https://markdownregistry.com/api/v1/blob/9d6a928d7c3817b08c88210a37a209378970c9e4c5d801fb5ee47fe6df190c80
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.