Loading the registry…
Use before/while writing or editing UI in Know Your Ward when the change is genuinely visual — new components, restyles, bug fixes to spacing/color/font/radius/elevation/touch-target, or any change-request that touches visuals. Enforces exact reuse of existing tokens/classes/patterns for components that already exist, and full-token-system compliance (color+spacing+radius+elevation+font+touch-target) for brand-new components. Also defines this skill's own self-update rule. Does not apply merely because a change happens to land inside `src/styles/`, `index.html`, or a view-render function in `src/js/` — a lot of edits in those files (new text, a new data field rendered through markup/classes that already exist, a copy change) touch no color/spacing/token/component decision at all, and don't need this skill. Trigger on phrases like "style this", "add a button/card/badge", "change the color/spacing/font of X", "new component", "redesign", "UI bug", or any edit that actually adds/changes a visual value or introduces a new markup/component pattern.
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.
1166 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 -- design-theme-protocols
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- design-theme-protocols ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v1.4.0
0 findings · 0.6s
v2.0.11
Incomplete run
0 findings · 17.3s
v0.3.26
1168 findings · 4.3s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 3.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 1.4s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.1s
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
No report in this scan: nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 14, 2026 | Caution96 | — | agentshield: completecisco-skill-scanner ·!: incompleteagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_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 Caution 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 1,168 findings above stand exactly as their scanners reported them, at full severity.