release 100/100 — SaferSkills

Is release safe to install?

SaferSkills independently audited 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.

.agents/skills/release/SKILL.md · 1 file

.agents/skills/release/SKILL.md1.7 KB · Markdown

name: release

description: Prepare a release by generating release notes from git history, committing them, tagging, and pushing.

argument-hint: <version-tag e.g. v1.0.0>

Prepare a release for version $ARGUMENTS.

Steps

Validate the version tag — ensure it starts with v and follows semver (e.g. v1.0.0). If no argument is provided, ask the user for the version.

Find the previous tag — run git tag --sort=-v:refname to find the most recent existing tag. If there is no previous tag, the changelog covers all commits.

Generate the changelog — run git log --oneline <previous-tag>..HEAD to get the list of commits since the last release. Group them into a readable changelog with sections like "What's Changed". Include commit messages but exclude merge commits.

Write RELEASE_NOTES.md — write the changelog to RELEASE_NOTES.md in the project root. Format it as:

   ## What's Changed in $ARGUMENTS

   - Commit message here (short hash)
   - Another commit message (short hash)
   ...

Show the release notes to the user — display the contents of RELEASE_NOTES.md and ask the user to confirm or request edits before proceeding.

Commit the release notes — stage and commit RELEASE_NOTES.md with message: docs: add release notes for $ARGUMENTS

Create the tag — run git tag $ARGUMENTS

Push — run git push origin main --tags to push both the commit and the tag. This will trigger the release workflow.

Confirm — tell the user the tag has been pushed and the GitHub Actions release workflow will create the GitHub release with the committed notes and build artifacts.

release— agent skill

Is release safe to install?

Steps

Audit the pieces. Scan the whole. Decide.