How do I install the Skillsaw Update skill?

Run npx skillmds@latest add stbenjam/skillsaw-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skillsaw Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skillsaw Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skillsaw Update free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Skillsaw Update?

stbenjam (@stbenjam) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skillsaw Update by stbenjam — Agent Skill

Name: Skillsaw Update
Rating: 4.2 (5 reviews)
Author: stbenjam

Skillsaw Update

Update a repository to the newest skillsaw — upgrade the install, report new rules and their findings in your repo, and bump version pins (GitHub Action SHAs, Makefile targets, pre-commit hooks). Use when a new skillsaw release is out and you want its latest checks.

stbenjam Updated Sep 22, 2026

File contents

skillsaw Update

Update this repository from its installed skillsaw to the newest release: upgrade the local install, report which rules are new and what they find in this repository, and bump every pinned skillsaw version (GitHub Actions SHAs, Makefile targets, pre-commit hooks, container tags).

Workflow

Ask one routing question at a time and wait for the answer. An explicit choice in the user's request already counts as an answer. Read a reference only after its condition or a yes answer routes to it; do not read the reference to formulate the question. After completing it, return here. If the answer is no, continue to the next checkpoint without reading it. Carry forward the command prefixes, versions, rule lists, and changed-file list.

Resolve every references/... path relative to the directory containing this SKILL.md, never relative to the target repository or the process's current working directory. If this file was fetched from the web, resolve each reference against the parent URL of this file and fetch it from that sibling location.

Replace brace-delimited fields below with facts from the repository or scan; never show placeholders to the user, and render singular or plural wording naturally.

1. Upgrade to the newest version

Read versions. It records the installed and latest versions, captures the old rule list, upgrades the install (or selects the new command prefix), and verifies the result. Report both versions before offering changes.

2. Report new rules

Read new rules. It diffs the old and new rule lists, explains each added rule, and scans the repository with the new version so every new rule is presented with its actual findings here.

3. Update version pins

If the repository pins skillsaw anywhere (GitHub Actions workflows, Makefile targets, pre-commit hooks, container image tags), ask:

I found skillsaw pinned in {locations}. Bumping them to {latest} keeps CI and local runs on the version just installed. Should I update those pins?

If yes, read pins. If no, preserve the locations.

4. Triage findings from new rules

If the new version reports findings from added rules, read triage and present its summary table for confirmation before making changes. Carry the agreed buckets forward.

5. Verify the result

After all accepted routes finish, always read verification.

---name: skillsaw-updatedescription: Update a repository to the newest skillsaw — upgrade the install, report new rules and their findings in your repo, and bump version pins (GitHub Action SHAs, Makefile targets, pre-commit hooks). Use when a new skillsaw release is out and you want its latest checks.license: Apache-2.0---# skillsaw UpdateUpdate this repository from its installed skillsaw to the newest release:upgrade the local install, report which rules are new and what they find inthis repository, and bump every pinned skillsaw version (GitHub ActionsSHAs, Makefile targets, pre-commit hooks, container tags).## WorkflowAsk one routing question at a time and wait for the answer. An explicit choicein the user's request already counts as an answer. Read a reference only afterits condition or a yes answer routes to it; do not read the reference toformulate the question. After completing it, return here. If the answer is no,continue to the next checkpoint without reading it. Carry forward the commandprefixes, versions, rule lists, and changed-file list.Resolve every `references/...` path relative to the directory containing this`SKILL.md`, never relative to the target repository or the process's currentworking directory. If this file was fetched from the web, resolve eachreference against the parent URL of this file and fetch it from that siblinglocation.Replace brace-delimited fields below with facts from the repository or scan;never show placeholders to the user, and render singular or plural wordingnaturally.### 1. Upgrade to the newest versionRead [versions](references/01-versions.md). It records the installed andlatest versions, captures the old rule list, upgrades the install (or selectsthe new command prefix), and verifies the result. Report both versions beforeoffering changes.### 2. Report new rulesRead [new rules](references/02-new-rules.md). It diffs the old and new rulelists, explains each added rule, and scans the repository with the newversion so every new rule is presented with its actual findings here.### 3. Update version pinsIf the repository pins skillsaw anywhere (GitHub Actions workflows, Makefiletargets, pre-commit hooks, container image tags), ask:> I found skillsaw pinned in {locations}. Bumping them to {latest} keeps CI> and local runs on the version just installed. Should I update those pins?If yes, read [pins](references/03-pins.md). If no, preserve the locations.### 4. Triage findings from new rulesIf the new version reports findings from added rules, read[triage](references/04-triage.md) and present its summary table forconfirmation before making changes. Carry the agreed buckets forward.### 5. Verify the resultAfter all accepted routes finish, always read[verification](references/05-verify.md).

Frequently asked questions