tag-release-ansible 100/100

Is tag-release-ansible safe to install?

SaferSkills independently audited tag-release-ansible (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-ansible/SKILL.md · 1 file

skills/tag-release-ansible/SKILL.md2.2 KB · Markdown

description: Bump the version in an Ansible Galaxy collection or role, tag the release, and push.

disable-model-invocation: true

Bump the version in an Ansible Galaxy collection or role, tag the release, and push.

Note: For team repos or any repo with a CI/CD pipeline, automated versioning and publishing 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:

Detect the project type:

If galaxy.yml exists, this is an Ansible collection.
If meta/main.yml exists but no galaxy.yml, this is an Ansible role.
If neither exists, tell the user this does not appear to be an Ansible Galaxy project and stop.

Read the current version from galaxy.yml (field: version) or meta/main.yml (field: version under galaxy_info).
Run git tag --sort=-version:refname | head -1 to find the most recent tag. Run git log <last-tag>..HEAD --oneline to see commits since the last tag. If no tags exist, use all commits. If there are no new commits, tell the user there is nothing to release and stop.
Determine the version bump:

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

Show the user the current version, the proposed new version, the bump reason, and the list of commits that will be included.
Ask the user to confirm before proceeding.
On confirmation, update the version field in galaxy.yml or meta/main.yml to the new version.
Stage the changed file: git add galaxy.yml or git add meta/main.yml.
If CHANGELOG.md exists, regenerate the ## Unreleased section using the same rules as the /changelog command, rename it to ## <new-version>, and stage CHANGELOG.md with git add CHANGELOG.md.
Commit the version bump: git commit -m "chore(release): <new-version>".
Create and push the tag: git tag <new-version> && git push && git push origin <new-version>.
Confirm the tag was pushed and print the tag name and a reminder to import the new version on Ansible Galaxy if not using an automated import webhook.

$ARGUMENTS

tag-release-ansible— agent skill

Is tag-release-ansible safe to install?

Audit the pieces. Scan the whole. Decide.