Loading the registry…
Karpathy-style autoresearch loop for the orchestrator. Hypothesizers draft a small number of paths; one biased worker takes ownership of each path and hill-climbs when there is a measurable worktree artifact (every experiment a commit, mail-as-pointer-to-git). For literature/research-only runs, workers may instead mail cited scratch files and the orchestrator publishes the report in `$PLANE_SESSION_DIR`. The orchestrator watches, prunes diminishing-returns paths, and ends with a written report plus committed worktree deliverables only when they exist. Activate when the task is open-ended research with measurable progress (a metric, a benchmark, a "find the best X"). Pairs with sub-skills `autoresearch-worker` and `autoresearch-hypothesizer`, which the orchestrator activates by naming them in the worker spawn prompts. Stacks cleanly with `planning-with-files`.
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.
9 critical findings reported by cisco-skill-scanner, agent-audit-kit, 7 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 -- 'fuzzy-dynamics/strings (autoresearch)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'fuzzy-dynamics/strings (autoresearch)' ~/.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
482 findings · 75.3s
v0.3.26
258 findings · 24.4s
v0.1.0
38 findings · 13.5s
v0.1.0
62 findings · 13.5s
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
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 15, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·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 840 findings above stand exactly as their scanners reported them, at full severity.