Loading the registry…
Review any project's .claude/ setup against Claude Code best practices and produce an actionable improvement report. Use when: "/claude-reviewer", "review my claude config", "audit .claude setup", "check my CLAUDE.md", "how good is my claude config", "rate this project's claude setup". NOT for: reviewing individual skill quality (use /skill-reviewer), code review, PR review.
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.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'omriariav/omri-marketplace (claude-reviewer)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'omriariav/omri-marketplace (claude-reviewer)' ~/.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
111 findings · 11.2s
v0.3.74
38 findings · 4.9s
v0.1.0
0 findings · 4.5s
v0.1.0
7 findings · 4.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
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 20, 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.
Out of 156 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 131 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
22 HIDDEN_DATA_FILE
Files: /repo/plugins/gdoc-math/.grok-plugin/plugin.json, /repo/plugins/copy/.codex-plugin/plugin.json, /repo/plugins/coacher/.cursor-plugin/hooks.json and 18 more · reported by cisco-skill-scanner
1 ALLOWED_TOOLS_GLOB_VIOLATION
Files: /repo/plugins/find-session/skills/find-session/repo/plugins/find-session/skills/find-session/SKILL.md · reported by cisco-skill-scanner
1 ALLOWED_TOOLS_GREP_VIOLATION
Files: /repo/plugins/gdoc-math/skills/gdoc-math/repo/plugins/gdoc-math/skills/gdoc-math/SKILL.md · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
131 The review call did not complete.
Rules: AAK-MARKETPLACE-001, PIPELINE_TAINT_FLOW, opt.nerlo-rules.nerlo-install-pipe-to-shell and 12 more · Files: .grok-plugin/marketplace.json, .cursor-plugin/marketplace.json, .claude-plugin/marketplace.json and 63 more · reported by agent-audit-kit, cisco-skill-scanner, nerlo-install-instruction
Critical findings indicate shell execution, network egress, and sensitive data handling risks.
Critical findings are present in multiple Python scripts, indicating potential issues with sensitive data handling or execution paths. High severity findings include shell execution via `bash` and piping to shell during installation, alongside potential taint flow vulnerabilities. The artifact also exhibits undeclared network egress and file write capabilities, raising concerns about data exfiltration and system modification.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 13 of 13; the rest are in the per-scanner reports above.