release SKILL.md skillA
release from awslabs/loom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add awslabs/loom/release@git:20260709.976e096Pins git:20260709.976e096 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- awslabs/loom
- Path
.claude/skills/release/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260709.976e096, committed Jul 9, 2026
- Size
- 2,406 bytes
- Repository stars
- 200
- License
- Apache-2.0
Increment the release version, draft release notes, and prepare a GitHub 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
# Release Preparation Prepare a new release for the Loom project. ## Step 1: Read Current Version Read the current version from both files: - `backend/pyproject.toml` — the `version` field under `[project]` - `frontend/package.json` — the `"version"` field Display the current version to the user. ## Step 2: Determine New Version If `$ARGUMENTS` is provided and is a valid semantic version (e.g. `1.2.0`), use it as the new version. Otherwise, ask the user what the new version should be. Suggest the next patch, minor, and major versions based on the current version (e.g. if current is `1.1.0`, suggest `1.1.1`, `1.2.0`, or `2.0.0`). Wait for the user to confirm before proceeding. ## Step 3: Update Version Files Update the version in all three files: - `backend/pyproject.toml`: update the `version = "..."` line - `frontend/package.json`: update the `"version": "..."` line - `backend/app/main.py`: update both `version="..."` occurrences (FastAPI app and health endpoint) ## Step 4: Commit Version Changes Commit the version bumps: 1. Run `git add backend/pyproject.toml frontend/package.json backend/app/main.py` 2. Commit with message `chore: bump version to <new-version>` …
Read the whole file at its exact version.
How to install
mdr add awslabs/loom/release@sha256:62f46d460d2efd89The line at the top of this page pins the label git:20260709.976e096, 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_wwalotgsdu4coonn)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 9, 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 (2406 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
awslabs/loom · 200 stars · license Apache-2.0 · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wwalotgsdu4coonn GET https://markdownregistry.com/api/v1/resolve?ref=awslabs/loom/release GET https://markdownregistry.com/api/v1/blob/62f46d460d2efd897671a47efb00025eb341f2725e724d4a0825c607423b9489
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.