Review Local UI Screenshots
xiaocang/easydict_win32
Review Easydict UI automation screenshot artifacts already present in local artifacts/ui-screenshots, screenshots, or a user-provided artifact directory.
Visual regression testing — capture before/after screenshots of UI changes and compare.
Install Dev Visual Verdict
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdict --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .claude/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .claude/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdictType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdict --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .agents/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .agents/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdict --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .cursor/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .cursor/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/evolution-foundation/evo-nexus.git --path .claude/skills/dev-visual-verdict--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdict --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .gemini/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .gemini/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdictInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .github/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .github/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install evolution-foundation/evo-nexus dev-visual-verdict --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/dev-visual-verdict .opencode/skills/dev-visual-verdict && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dev-visual-verdict" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-visual-verdict into .opencode/skills/dev-visual-verdict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-visual-verdict", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dev-visual-verdict- GitHub stars
- 544
- Token cost
- ~490 tokens
- SKILL.md length
- 147 words
- Files
- 1
- Skills in repo
- 117
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Visual regression testing — capture before/after screenshots of UI changes and compare.
- Works in 6 steps: Identify scope — which components could… → Capture baseline — screenshot current… → Apply change — let @bolt-executor make… → …
- A UI change might have unintended visual impact across components
- SKILL.md covers Use When, Do Not Use When, Workflow and Output, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dev Visual Verdict is an agent skill from evolution-foundation/evo-nexus. Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Visual regression testing. The repository describes itself as: The open source operating system for AI-powered businesses.
When your agent uses it
- A UI change might have unintended visual impact across components
- Tasks that involve Visual regression testing
Example prompts
- “/dev-visual-verdict”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify scope — which components could be affected
- Capture baseline — screenshot current state of each affected component
- Apply change — let @bolt-executor make the modification
- Capture after — screenshot post-change state
- Compare — flag any visual differences (pixel-level or layout-level)
- Verdict — IDENTICAL / EXPECTED CHANGES / UNEXPECTED REGRESSION
What it can do on your machine
Read from SKILL.md and the folder at commit 7f5dd76. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dev Visual Verdict loads about 490 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 147 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 147 words (~490 tokens).
“Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.”
- name
- dev-visual-verdict
Files
Just SKILL.md in .claude/skills/dev-visual-verdict of evolution-foundation/evo-nexus.
Open the folder on GitHubat commit 7f5dd76
Compare with similar skills
Dev Visual Verdict next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dev Visual Verdict this skillevolution-foundation/evo-nexus | 544 | — | ~490 | Automated safety check: Pass | Custom licence | |
| Review Local UI Screenshotsxiaocang/easydict_win32 | 101 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Handsontable Visual Test Demoshandsontable/handsontable | 22k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Kc Screenshotimran31415/kube-coder | 388 | — | ~870 | Automated safety check: Notes | MIT | |
| Visual QAliangdabiao/Godogen | 127 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Meticulous FixFlintSH/Flare | 135 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Handsontable Visual Test Demos
handsontable/handsontable
Explains how to add or change the demo pages that Handsontable's visual regression suite photographs, including per-feature routes in the js demo and the shared grid.
Kc Screenshot
imran31415/kube-coder
Capture desktop + mobile, dark + light screenshots of the kube-coder dashboard SPA for visual QA of a UI change.
Visual QA
liangdabiao/Godogen
Visual quality assurance — analyze game screenshots for defects, compare against reference, check motion in frame sequences.
Meticulous Fix
FlintSH/Flare
Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given.
Visual QA For Web And Terminal UIs
code-yeongyu/oh-my-openagent
Checks a built UI against a human-interface checklist and any reference image, pairing day and night screenshots at two screen widths.
More from evolution-foundation/evo-nexus
All 117 skills in this repoAI Image Creator
evolution-foundation/evo-nexus
Generates PNG images through OpenRouter models, with transparent backgrounds and reference-image edits, and describes existing images with multimodal vision.
MongoDB Query Client
evolution-foundation/evo-nexus
Runs read-only MongoDB finds, aggregations and collection listings against databases named in your .env, choosing the connection by label or index.
MySQL and MariaDB Query Tool
evolution-foundation/evo-nexus
Queries MySQL or MariaDB databases declared in .env by label, read-only by default unless a connection explicitly allows writes.
Postgres Query Client
evolution-foundation/evo-nexus
Runs read-only SQL queries and schema exploration against PostgreSQL databases declared in .env, chosen by label or index, with writes blocked unless a connection allows them.
Redis Inspector
evolution-foundation/evo-nexus
Reads keys and server state from Redis instances configured in .env through a read-only Python client, choosing connections by label or index.
Int Bling
evolution-foundation/evo-nexus
Bling ERP integration via API v3. An agent skill from evolution-foundation/evo-nexus.
Related
Categories
Questions about Dev Visual Verdict
What does Dev Visual Verdict do?
Visual regression testing — capture before/after screenshots of UI changes and compare. Dev Visual Verdict is an agent skill from evolution-foundation/evo-nexus. Visual regression testing — capture before/after screenshots of UI changes and compare.
When should I use Dev Visual Verdict?
Dev Visual Verdict fits situations like: A UI change might have unintended visual impact across components; tasks that involve Visual regression testing.
How do I install Dev Visual Verdict in Claude Code?
Run `npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a claude-code`. Or copy the skill folder (.claude/skills/dev-visual-verdict in evolution-foundation/evo-nexus) into .claude/skills/dev-visual-verdict in your project. Claude Code loads it when a task matches its description.
How do I install Dev Visual Verdict in Codex?
Run `npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a codex`. Or copy the skill folder (.claude/skills/dev-visual-verdict in evolution-foundation/evo-nexus) into .agents/skills/dev-visual-verdict in your project. Codex loads it when a task matches its description.
Can I use Dev Visual Verdict in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add evolution-foundation/evo-nexus --skill dev-visual-verdict -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-visual-verdict, .gemini/skills/dev-visual-verdict, .github/skills/dev-visual-verdict and .opencode/skills/dev-visual-verdict in your project.
What does Dev Visual Verdict need to run?
SKILL.md names no scripts, command-line tools or credentials: Dev Visual Verdict is instructions for the agent only.
Does Dev Visual Verdict access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dev Visual Verdict safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dev Visual Verdict use?
Dev Visual Verdict has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Dev Visual Verdict use?
About 490 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dev Visual Verdict?
Skills that share tags, products or a category with Dev Visual Verdict: Review Local UI Screenshots (xiaocang/easydict_win32, 101 stars), Handsontable Visual Test Demos (handsontable/handsontable, 22k stars), Kc Screenshot (imran31415/kube-coder, 388 stars) and Visual QA (liangdabiao/Godogen, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dev Visual Verdict?
evolution-foundation (a GitHub organization) maintains it in evolution-foundation/evo-nexus, which has 544 GitHub stars. The repository holds 117 skills in this directory. The repository was last updated on May 13, 2026.
Source: evolution-foundation/evo-nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.