tag-release 100/100 — SaferSkills

Is tag-release safe to install?

SaferSkills independently audited tag-release (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/tag-release/SKILL.md · 1 file

skills/tag-release/SKILL.md1.3 KB · Markdown

description: Suggest and apply the next semver tag based on commits since the last tag.

disable-model-invocation: true

Suggest and apply the next semver tag based on commits since the last tag.

Note: For team repos or any repo with a CI/CD pipeline, automated tagging via a pipeline (e.g. GitHub Actions triggered on merge to main) is strongly preferred over running this command manually. Use this command for solo projects or when no pipeline is set up.

Steps:

Run git tag --sort=-version:refname | head -1 to find the most recent tag. If no tags exist, suggest v0.1.0 as the first tag.
Run git log <last-tag>..HEAD --oneline to see commits since the last tag. If there are no commits since the last tag, tell the user there is nothing to release and stop.
Determine the next semver version:

Bump major if any commit contains BREAKING CHANGE
Bump minor if any commit is type feat
Bump patch for all other changes

Show the user the proposed tag, the version bump reason, and the list of commits that will be included.
Ask the user to confirm before proceeding.
On confirmation, run git tag <version> to create the tag, then git push origin <version> to push it.
Confirm the tag was pushed and print the tag name.

$ARGUMENTS

tag-release— agent skill

Is tag-release safe to install?

Audit the pieces. Scan the whole. Decide.