pre-release-verification-10db88 100/100

Is pre-release-verification-10db88 safe to install?

SaferSkills independently audited pre-release-verification-10db88 (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.

plugins/quality-gates/skills/pre-release-verification/SKILL.md · 1 file

plugins/quality-gates/skills/pre-release-verification/SKILL.md2.1 KB · Markdown

name: pre-release-verification

description: Use when a release candidate needs final checks before tagging, publishing, or production deployment.

Purpose

Block releases until the repository state, CI status, local validation, and publish metadata are known and reproducible.

When to Use

Before creating a release tag.
Before deploying to production.
Before approving a release candidate prepared by another agent.
When CI is green but local package or catalog checks still need proof.

Do not use as a substitute for fixing failures. If any gate fails, stop and report the blocker.

Inputs

Intended version or deployment identifier
Current branch and commit
CI status for the release commit
Project-specific build, lint, test, and packaging commands

Workflow

Confirm the working tree is clean:

git status --short

Confirm the release commit and recent history:

git log --oneline --decorate -n 10

Confirm CI is green for the exact commit. For GitHub:

gh run list --limit 5
gh run view <run-id> --json conclusion,status,headSha,url

Run local validation. Use the project's documented commands, for example:

npm run build
npm test
python scripts/validate-skills.py
python scripts/validate-catalog.py

Check for secrets or accidental local files:

git diff --stat
git status --short

Report go/no-go with exact evidence.

Output

RELEASE VERIFICATION: go / no-go
Commit: <sha>
CI: <status and URL>
Local checks: <commands and results>
Blockers: <none or list>
Next action: <tag / deploy / stop>

Verification

[ ] Working tree was clean or dirty files were reported.
[ ] CI status was tied to the exact release commit.
[ ] Local validation commands exited 0.
[ ] No secrets or accidental local files were included.
[ ] Go/no-go recommendation included evidence, not confidence.

Failure Modes

Releasing from an uncommitted or untracked local state.
Checking CI for a different commit than the release candidate.
Treating lint/build success as full test coverage.
Continuing after a failed gate because the release is "small".

pre-release-verification-10db88— agent skill

Is pre-release-verification-10db88 safe to install?

Purpose

When to Use

Inputs

Workflow

Output

Verification

Failure Modes

Audit the pieces. Scan the whole. Decide.