Loading the registry…
Analyze 2-4 plausible architecture options for a non-trivial software change instead of jumping to a single design. Trigger when the user asks for an architecture plan, design options, trade-off analysis, solution variants, refactor strategy options, migration options, or phrases like "давай подумаем над архитектурой", "разложи варианты", "сравни варианты решения", "какой вариант архитектуры лучше", or similar. Start from the current state and real constraints, enumerate only realistic options, compare them on trade-offs, complexity, cost, risk, migration pain, testing implications, and scaling implications, then recommend one option and explicitly reject the others with concrete reasons. Keep the analysis implementation-oriented and minimal: do not invent unnecessary layers, subsystems, abstractions, or future-proofing unless they are justified by current constraints. Do not use for generic brainstorming, roadmap planning, or writing a full implementation plan after the architecture has already been chosen.
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.
53 critical findings reported by agent-audit-kit, 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 -- architecture-options-analysis
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- architecture-options-analysis ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 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
60 findings · 10.9s
v0.3.26
58 findings · 1.1s
v0.1.0
0 findings · 3.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.9s
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 12, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-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 118 findings above stand exactly as their scanners reported them, at full severity.