audit-reliability — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited audit-reliability (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.
Can it recover?
When it breaks, does it come back?
// What happens when X fails?
try {
doX()
} catch {
// Does it fail safe?
return default
}| Check | Issue | Fix |
|---|---|---|
| No fallback | Everything dies | Add default |
| No retry | One fail = fail | Retry |
| No circuit | Cascade fail | Circuit break |
// Can it restart?
process.on('uncaught', () => {
// Log and restart?
})| Check | Issue | Fix |
|---|---|---|
| No restart | Stay down | Auto-restart |
| No logging | Can't debug | Log it |
| No alerts | Can't know | Alert |
// What if DB fails?
await db.save(x)
// vs
await db.save(x)
.catch(log)| Check | Issue | Fix |
|---|---|---|
| No backup | Lost forever | Back up |
| No transactions | Partial | Use transaction |
| No validation | Bad data | Validate |
| Check | Limit |
|---|---|
| Auto-scale | Yes/No |
| Max instances | [n] |
| Queue depth | [n] |
## Reliability - [system]
### Failure Mode
- [SAFE/FAIL] If [X] fails: [behavior]
### Recovery
- [YES/NO] Auto-restart
- [YES/NO] Alert on fail
- [YES/NO] Log on fail
### Data
- [YES/NO] Backup
- [YES/NO] Transactions
### Capacity
- [n] max
- Auto-scale: [YES/NO]
### MTTR (mean time to recover)
- Target: [m]minRole: Reliability Auditor Input: System Output: Can recover?
Plan for failure.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.