project-release-maintainer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited project-release-maintainer (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This is a composable overlay, not a standalone workflow. Use alongside the repo's implementation skill for publication-facing and packaging-sensitive changes. Compose with documenter when the main artifact is durable release, install, or contributor documentation.
The change affects README, release checklists, install rules, shipped assets, workflows, licenses, or other publication-facing artifacts.
Internal code changes that don't affect the shipped surface (use the implementation skill directly), vendored dependency work (use project-vendor-boundary), or config/test work (use project-config-and-tests).
the repo does not already contain or that the user did not explicitly request
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.