vlm-critic

Compare baseline and current screenshots to write per-route vlm_verdict and vlm_summary into index.json.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill vlm-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vlm-critic
Source: https://github.com/paulingham/.claude/tree/main/skills/vlm-critic
Command: npx skills add https://github.com/paulingham/.claude --skill vlm-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final Gate teammate for the vlm-critic agent orchestrates visual-regression evaluation by reading index.json routes and plan.md, comparing baseline and current PNG pairs, and writing per-route vlm_verdict and vlm_summary back into index.json, then returning an aggregate verdict of VISUAL_DIFF_PASS or VISUAL_DIFF_FAIL to gate the product-release.

Core Features & Use Cases

  • Reads design-qc input (index.json and plan.md) to determine scope and visible deltas for each route.
  • Produces per-route verdicts (PASS/FAIL) and concise vlm_summary notes, then writes them to index.json.
  • Enforces strict read-guard rules to limit multimodal access and returns a deterministic, gated outcome for all routes.

Quick Start

Spawn the vlm-critic during the Final Gate to produce per-route visual-regression verdicts by reading index.json and plan.md, and write vlm_verdict and vlm_summary back to index.json.

Frequently Asked Questions about vlm-critic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect semantic visual regressions in screenshots before a release?

To detect semantic visual regressions, compare baseline and current PNG screenshots across defined routes and generate a PASS or FAIL verdict for each one. This process evaluates visible deltas and writes concise summary notes directly into your index.json file to gate the release.

What is a Final Gate visual regression check in an automation pipeline?

A Final Gate visual regression check is a strict automated review step that compares captured design-qc screenshots against baselines. It enforces deterministic outputs and read-guards multimodal access, returning an aggregate VISUAL_DIFF_PASS or VISUAL_DIFF_FAIL outcome to gate product-release readiness.

How do I write per-route visual regression verdicts back into index.json?

You write per-route verdicts by reading index.json routes and plan.md, evaluating the screenshot pairs for each route, and updating index.json with a vlm_verdict of PASS or FAIL alongside a short vlm_summary to document the semantic diff findings.

Can I restrict multimodal file reads during automated visual regression testing?

Yes, you can restrict multimodal file reads by enforcing a vlm-critic-read-guard. This strict read-guard rule limits multimodal access to only the necessary baseline and current PNG pairs, ensuring deterministic evaluation while reading and writing exclusively to index.json.

Does this visual regression gating approach work without external dependencies?

Yes, this visual regression gating approach works without external dependencies. It operates autonomously by reading design-qc inputs like index.json and plan.md, enforcing deterministic outputs, and relying entirely on internal read-guards to restrict multimodal reads.

What are the limitations of using index.json for semantic diff gating?

The limitation of using index.json for semantic diff gating is that the process reads and writes strictly to index.json, meaning all baseline and current PNG pairs must be mapped across index.json.routes beforehand for the deterministic verdicts to execute successfully.