Loading the registry…
Decide whether an AI agent may DO a write/change action on its own, or must stop and get a clear yes from a human first. Use BEFORE any action that writes, edits, commits, pushes, deploys, sends, publishes, or reconfigures a system — and whenever a request is a vague "do whatever is needed", "fix this", "handle it", "make it better" that names no specific scope. Sorts what looks like permission into three things — a goal, a method, and a green light — and only a green light means go. Includes a four-step check, rules for risky ("hot") areas like production, databases, and anything users see, and a rule for following through on a green light you already have. Triggers on: can the agent do this without asking, is this safe to do, do I need approval, did they actually say yes, guardrails, autonomy boundary, hot zone, irreversible action.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by cisco-skill-scanner, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'quitohooded/keel-skills (authorization-protocol)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'quitohooded/keel-skills (authorization-protocol)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
66 findings · 13.0s
v0.3.74
3 findings · 5.2s
v0.1.0
0 findings · 5.2s
v0.1.0
0 findings · 5.2s
v0.71.0
15 findings · 0.3s
v2.3.8
17 findings · 9.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.3s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Flagged33 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 101 findings above stand exactly as their scanners reported them, at full severity.