deploying-safely — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited deploying-safely (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
A deploy is an outward-facing, hard-to-undo action. The goal is to ship often AND make a bad release boring to recover from. Confirm before deploying unless the user has clearly authorized it.
or hand-tweak on the way out.
once. Watch the new version's health (errors, latency) before widening.
and that the previous version still works. Rollback should be faster than forward-fix.
and turn behaviour on/off without a redeploy — and kill it instantly if it misbehaves.
migration, or drop something the old version still uses (see database-migrations' expand/contract).
"it deployed" — declare it on "it's serving correctly" (see verify-before-done).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.