skillsaw-release SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
skillsaw-release from stbenjam/skillsaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stbenjam/skillsaw/skillsaw-release@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stbenjam/skillsaw
- Path
.apm/skills/skillsaw-release/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Sep 5, 2026
- First version recorded
- Aug 25, 2026
- Size
- 5,685 bytes
- Repository stars
- 69
- License
- Apache-2.0
Bump the version, generate release notes, and publish a new skillsaw release to PyPI. Use when cutting a new 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
<!-- Source paths below are repo-root-relative references, not links navigable from this skill's directory. -->
<!-- skillsaw-disable content-unlinked-internal-reference -->
# skillsaw Release
Follow these steps to release a new version of the **skillsaw** linter.
## Step 1: Run pre-flight checks
Before releasing, verify:
1. Check you are on the `main` branch, it is clean (`git status`), and up to
date with `origin/main` (`git pull origin main`).
2. Verify the current `main` commit has a successful **push** run of the
`Tests` workflow. Do not accept the reduced PR test run: pull requests run
Python 3.9 plus the 3.14 coverage job, while a `main` push must have passed
Python 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14. The workflow run must test the
exact `HEAD` being released:
```bash
main_sha=$(git rev-parse HEAD)
run_id=$(gh run list --workflow test.yml --branch main --commit "$main_sha" \
--event push --status success --limit 1 --json databaseId --jq '.[0].databaseId')
test -n "$run_id" && test "$run_id" != "null" || {
echo "No successful Tests workflow run exists for main at $main_sha" >&2
exit 1
}
…Read the whole file at its exact version.
How to install
mdr add stbenjam/skillsaw/skillsaw-release@sha256:32913dd646301fb5The line at the top of this page pins the label v1.0, 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_xc2sixdvn46d5xmw)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 25, 2026 and Sep 5, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-09-05 | 91a8865 | 5,685 B | A | view · diff |
| v1.0 | 2026-08-28 | 14ce14b | 5,623 B | A | view · diff |
| v1.0 | 2026-08-28 | a31d726 | 4,611 B | A | view · diff |
| v1.0 | 2026-08-25 | 95ab2a5 | 4,246 B | A | view · diff |
| v1.0 | 2026-08-25 | 8e270ee | 4,273 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 (5685 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
stbenjam/skillsaw · 69 stars · license Apache-2.0 · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xc2sixdvn46d5xmw GET https://markdownregistry.com/api/v1/resolve?ref=stbenjam/skillsaw/skillsaw-release GET https://markdownregistry.com/api/v1/blob/32913dd646301fb5810fab072d28facb84b8c672c81b96246d29e187b8d2ab2b
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 stbenjam/skillsaw
Every file in stbenjam/skillsaw