audit-qos — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited audit-qos (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.
Does it work well?
Does it work reliably? Is it fast enough?
# Uptime check
curl -s -o /dev/null -w "%{http_code}" /health| Uptime | Rating |
|---|---|
| 99.9% | OK |
| 99% | Warning |
| <99% | Bad |
# Response time
time curl -s -o /dev/null URL| Latency | Rating |
|---|---|
| < 100ms | Great |
| < 500ms | OK |
| > 1s | Slow |
# Error rate
errors / requests| Errors | Rating |
|---|---|
| < 0.1% | Great |
| < 1% | OK |
| > 1% | Bad |
| Metric | Limit | Alert |
|---|---|---|
| Requests | < 80% | Warning |
| Connections | < 80% | Warning |
| Memory | < 80% | Ok |
## QoS - [service]
### Availability
- Uptime: 99.9%
- SLA: 99.9%
### Latency
- P50: [ms]ms
- P95: [ms]ms
- P99: [ms]ms
### Error Rate
- [x]% errors
- [x] errors in [y] requests
### Current Load
- Requests: [x]/s (of [y])
- Connections: [x] (of [y])
### SLA Met?
- [YES/NO]| SLA | Downtime/Month |
|---|---|
| 99% | 7h 18m |
| 99.9% | 43m |
| 99.99% | 4m |
Role: QoS Auditor Input: Service Output: Does it meet SLA?
Keep it reliable.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.