verify-ui-change
Check that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix.
Install / Use
npx skills add reticlehq/reticle --skill verify-ui-changeInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of verify-ui-change
verify-ui-change scores 85/100 on our quality scale, 2522nd of 4,702 Development & Engineering skills we index.
Its SKILL.md is 5.2 KB long, split into 6 sections with 3 code examples: a solid amount of guidance for an agent.
With 1,271 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 10 days ago, so verify-ui-change is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
verify-ui-change compared with similar skills
All 4 of these similar skills score higher than verify-ui-change; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| verify-ui-change (this skill)by reticlehq | 85 | 1.3k | 10d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
Frequently asked questions
- How do I install verify-ui-change?
- Run
npx skills add reticlehq/reticle --skill verify-ui-change. The install tabs above show the steps for each supported agent. - Which AI agents does verify-ui-change work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is verify-ui-change safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is verify-ui-change still maintained?
- The repository was last updated 10 days ago, so verify-ui-change is actively maintained.
Skill content
View source on GitHubname: verify-ui-change description: Check that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix. Use after editing a component, a form, a route, or an API call; when you have said "fixed" but have not opened the app; when the user asks "does it actually work?"; or when a change looks right on screen and you cannot prove it. license: Apache-2.0 metadata: version: 3.6.0 homepage: https://www.reticle.sh repository: https://github.com/reticlehq/reticle
Verify the change in the running app
You edited something a user can see. Nothing is proven until the real app has done it and something other than the DOM agrees.
This uses Reticle, which embeds a dev-only SDK in the user's running app and exposes it as reticle_* MCP tools. No screenshots, no browser download for the verify loop, no dev server of its own.
1. Are the tools here?
reticle_session({ action: "list" })
- A session comes back → go to step 2.
- Tools do not exist → Reticle is not installed. Run
RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then keep going without the tools: fix every⚠it printed, start the project's own dev script in the background if nothing is serving the app, and open it withnpx @reticlehq/server open <the url the dev server is serving>. Only once the app is running and connected, ask for the one thing you cannot do yourself: a client restart, so it picks up the MCP server. Stopping at theinitcommand leaves the user with config files and an uninstrumented page. Full setup is in theinstall-and-verifyskill. - Tools exist, list is empty → read the
whyfield on the response. It distinguishes "no app running" from "an app is running that never dialled this daemon" from "a tab was here and closed", and each has a different fix. If no app is running, start the project's own dev script frompackage.jsonin the background yourself and tell the user in one line that it is running and how to stop it: never a second one, never a guessed command, never kill anything, and the permission prompt is your host's. If one IS running, the app is not the missing piece and the SDK is; do not send the user to start what they already started.
2. Name the consequence BEFORE you act
This is the whole method. An expectation written after you see the result can be talked into agreeing with whatever happened; one written before cannot.
reticle_look({ action: "page", sessionId, mode: "interactive" }) // controls only, with refs
reticle_act_and_wait({ sessionId, ref, action: "click", until: { kind: "allOf", predicates: [
{ kind: "net", method: "POST", urlContains: "/api/...", status: 200 },
{ kind: "element", query: { testid: "..." } },
{ kind: "console", level: "error", absent: true },
]}})
Multi-step journey? Drive it in one call with reticle_act { steps: [...] }, then assert the outcome once. Do not act → snapshot → act → snapshot: it proves the same thing at several times the cost.
Verdicts come from reticle_act_and_wait, reticle_assert, and reticle_act { steps } when a step declares expect. A bare reticle_act, look, navigate and observe move or read the app and prove nothing. A drive that ends without a verdict has no result, however many calls it made.
3. Read the verdict honestly
| verified | means | do |
| --- | --- | --- |
| yes | the consequence you named happened | report it, with the evidence |
| no | it did not happen, or a channel contradicted the UI | a real finding: report it with because |
| unknown | Reticle drove the app and could not tell | not a pass. Say unknown and say why |
On unknown / unsettled, re-assert rather than re-driving: reticle_assert({ predicate, since, timeout_ms: 8000 }) using the since from the act result. Re-driving repeats a side effect that already happened.
Never weaken a check to turn a verdict green. An assertion edited until it passes proves nothing.
4. Check what you did not touch
reticle_run({ tool: "reticle_verify", sessionId, args: { action: "coverage" } }) // { total, exercised, untouched }
If untouched still holds controls your change affects, the drive is unfinished. One call, and it is the cheapest guard against reporting a pass over the half you never opened.
5. Report
State what you drove, what the verdict was, and the evidence: the request and status, the state that changed, the app's own signal. If something failed, reticle_look({ action: "element", sessionId, ref }) on the failing element gives the file:line: put it in the report.
Then reticle_session({ action: "yield", mode: "waiting" }) so the human's panel stops reading "live".
More detail, fetchable one page at a time: curl https://docs.reticle.sh/llms.txt for the index, then the single page you need (https://docs.reticle.sh/tools/act-and-wait.md, https://docs.reticle.sh/predicates.md, https://docs.reticle.sh/troubleshooting.md). If Reticle itself misbehaves, file it with reticle_session { action: "feedback" }: one call, then carry on.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
