Loading the registry…
Adds the current device to an existing Exo cluster with as little friction as possible — diagnoses everything needed up front (Exo install, mlx, Metal Toolchain, Python version compatibility) in one pass, asks for confirmation exactly once covering the whole install plan, then executes end-to-end and verifies the device actually joined the cluster. Runs locally, on the device being added — invoke it by opening a Claude Code session (or SSH session you're already in) on that device and asking to "add this machine to the cluster" or "join the Exo cluster" or "daisy chain this device". Deliberately does not reach out to or install anything on other devices remotely — see local-offload's Troubleshooting for why (running installers on machines you can't directly watch has a meaningfully worse failure mode than doing it in front of a human).
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 agent-audit-kit. 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 -- 'bishop07102001-code/claude-efficiency-suite (daisy-chain)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'bishop07102001-code/claude-efficiency-suite (daisy-chain)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
43 findings · 7.8s
v0.3.74
9 findings · 2.1s
v0.1.0
0 findings · 3.8s
v0.1.0
8 findings · 3.8s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Scan Halted | — | 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 applicable | rejected |
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 60 findings above stand exactly as their scanners reported them, at full severity.