Loading the registry…
Take a UI screen recording (mobile/desktop/web/marketing video) and do one of four things — your pick: (1) just extract the frames as PNGs, (2) analyze the design system shown in the video and list the distinct screens, (3) compare the video against files in your codebase and produce a concrete list of edits to make those files feel like the video, or (4) scaffold a real frontend app (Vite + React + TypeScript + Tailwind) that recreates the UI's behavior — not just its appearance — with working interactions and animations. Option 3 always shows you the proposed changes first and waits for your approval before editing. Requires ffmpeg; mode 4 additionally needs Node.js to run the generated app. Mode 4 reads the `frontend-design` skill (if installed) before generating to inherit its component-quality and aesthetic guidance. Trigger whenever the user mentions a screen recording, video walkthrough, mobile-app demo, desktop-app capture, marketing/product video, or wants to extract design insights from a clip — even if they don't explicitly say "use the video skill". Phrases like "I have this video of a UI", "extract frames from this recording", "what's the design system in this video", "make my components look like this clip", "build a frontend app from this video", or "I have a UI demo, here are files I want to update" should all trigger it. The skill itself will ask which of the four modes to run.
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 -- video-to-ui
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- video-to-ui ~/.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
57 findings · 9.1s
v0.3.26
3 findings · 6.7s
v0.1.0
3 findings · 3.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.7s
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 · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
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 | Flagged58 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-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 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 63 findings above stand exactly as their scanners reported them, at full severity.