New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify UI Change

by reticlehq in reticlehq/reticle

Check that a change to a web app actually works in the running app before calling it done.

Apache-2.0Auto-check passed

Install Verify UI Change

skills CLI
$ npx skills add reticlehq/reticle --skill verify-ui-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install reticlehq/reticle verify-ui-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify-ui-change .claude/skills/verify-ui-change && rm -rf skills-src

Use ~/.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/

Facts

Skill name
verify-ui-change
GitHub stars
1.2k
Token cost
~1.3k tokens
SKILL.md length
633 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Check that a change to a web app actually works in the running app before calling it done.

  • Works in 5 steps: Are the tools here? → Name the consequence BEFORE you act → Read the verdict honestly → …
  • Asks does it actually work?
  • SKILL.md covers 1. Are the tools here?, 2. Name the consequence BEFORE…, 3. Read the verdict honestly and 4. Check what you did not touch, plus 1 more section
  • Calls npx and curl; reaches docs.reticle.sh

What it does

Verify UI Change is an agent skill from reticlehq/reticle. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications. The licence is Apache-2.0.

When your agent uses it

  • Asks does it actually work?
  • A change looks right on screen and you cannot prove it

Example prompts

  • “but have not opened the app; when the user asks”
  • “/verify-ui-change”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Are the tools here?
  2. Name the consequence BEFORE you act
  3. Read the verdict honestly
  4. Check what you did not touch
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 178e5c0. 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

    Shell commands in SKILL.md call:

    • npx
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.reticle.sh

    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

Verify UI Change loads about 1.3k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 633 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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

The full file from reticlehq/reticle at commit 178e5c0, republished under its Apache-2.0 licence (© reticlehq). 633 words, ~1,338 tokens.

Download SKILL.mdSave it as .claude/skills/verify-ui-change/SKILL.md (or your agent's skills folder).
name
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.7.0
metadata.homepage
https://www.reticle.sh
metadata.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 with npx @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 the init command leaves the user with config files and an uninstrumented page. Full setup is in the install-and-verify skill.
  • Tools exist, list is empty → read the why field 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 from package.json in 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.

Show full SKILL.md (230 more words)Show less

3. Read the verdict honestly

verifiedmeansdo
yesthe consequence you named happenedreport it, with the evidence
noit did not happen, or a channel contradicted the UIa real finding: report it with because
unknownReticle drove the app and could not tellnot 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.

© reticlehq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/verify-ui-change of reticlehq/reticle.

Open the folder on GitHubat commit 178e5c0

Compare with similar skills

Verify UI Change 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.

Verify UI Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify UI Change this skillreticlehq/reticle1.2k—~1.3kAutomated safety check: PassApache-2.0
ActualizeNeoLabHQ/context-engineering-kit1.8k—~932Automated safety check: PassGPL-3.0
Is This Actually Goodmohitagw15856/pm-claude-skills1.4k—~884Automated safety check: PassMIT
Actual Budgetsundial-org/awesome-openclaw-skills663—~1.6kAutomated safety check: PassNone
Budget Cash Flowsickn33/agentic-awesome-skills47k1 repos~4.1kAutomated safety check: PassMIT
Skill Compliance Checkeraffaan-m/ECC276k1 repos~623Automated safety check: PassMIT

Similar skills

  • Actualize

    NeoLabHQ/context-engineering-kit

    Reconcile the project's FPF state with recent repository changes

    1.8k GitHub stars~932 tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

  • Is This Actually Good

    mohitagw15856/pm-claude-skills

    Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment.

    1.4k GitHub stars~884 tokensUpdated yesterday
    Auto-check passed

  • Actual Budget

    sundial-org/awesome-openclaw-skills

    Query and manage personal finances via the official Actual Budget Node.js API.

    663 GitHub stars~1.6k tokensUpdated 7 mo ago
    Business, Finance & HRAuto-check passed

  • Budget Cash Flow

    sickn33/agentic-awesome-skills

    Budget against actual by department, category and period, with budget and actual amounts, variance, percentage used and linked expenses.

    47k GitHub starsUsed in 1 repo~4.1k tokens
    Business, Finance & HRAuto-check passed

  • Skill Compliance Checker

    affaan-m/ECC

    Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    276k GitHub starsUsed in 1 repo~623 tokens
    Agent WorkflowsAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated today
    Research & ScienceAuto-check: notes

More from reticlehq/reticle

All 19 skills in this repo

  • Agentic TDD

    reticlehq/reticle

    Applies red-green TDD to behavior unit tests cannot reach, by stating the expected outcome against the running app with Reticle before writing the feature.

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Whole-App Health Sweep

    reticlehq/reticle

    Sweeps a running web app by clicking every reachable control, then reports dead buttons, console errors, failed requests and mismatches between API data and the screen.

    1.2k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Broken UI Debugger

    reticlehq/reticle

    Finds why a running web app misbehaves when the console is empty and the code looks fine, by reading the click, request, store and console together.

    1.2k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Desktop App Driving with Reticle

    reticlehq/reticle

    Drives and verifies Electron or Tauri desktop apps through Reticle, which sees the renderer and the IPC calls that a browser-based testing tool cannot observe.

    1.2k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • False Green Test Detection

    reticlehq/reticle

    Finds out why a passing test suite sits on top of a broken app by comparing what the running app does with what the tests claim, using Reticle.

    1.2k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Fix What I Pointed At

    reticlehq/reticle

    Picks up bugs a person flagged by pointing at elements in the running app, each mark carrying the element, their note and the source file and line, then fixes and verifies them.

    1.2k GitHub stars~878 tokensUpdated yesterday
    Auto-check passed

Questions about Verify UI Change

What does Verify UI Change do?

Check that a change to a web app actually works in the running app before calling it done. Verify UI Change is an agent skill from reticlehq/reticle. Check that a change to a web app actually works in the running app before calling it done.

When should I use Verify UI Change?

Verify UI Change fits situations like: asks does it actually work?; A change looks right on screen and you cannot prove it.

How do I install Verify UI Change in Claude Code?

Run `npx skills add reticlehq/reticle --skill verify-ui-change -a claude-code`. Or copy the skill folder (skills/verify-ui-change in reticlehq/reticle) into .claude/skills/verify-ui-change in your project. Claude Code loads it when a task matches its description.

How do I install Verify UI Change in Codex?

Run `npx skills add reticlehq/reticle --skill verify-ui-change -a codex`. Or copy the skill folder (skills/verify-ui-change in reticlehq/reticle) into .agents/skills/verify-ui-change in your project. Codex loads it when a task matches its description.

Can I use Verify UI Change 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 reticlehq/reticle --skill verify-ui-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-ui-change, .gemini/skills/verify-ui-change, .github/skills/verify-ui-change and .opencode/skills/verify-ui-change in your project.

What does Verify UI Change need to run?

Going by SKILL.md and its folder, Verify UI Change needs the command-line tools its instructions call (npx and curl). Our summary lists: Node.js.

Does Verify UI Change access the network?

SKILL.md names 1 domain. In commands or code: docs.reticle.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Verify UI Change 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 Verify UI Change use?

Verify UI Change is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify UI Change use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Verify UI Change?

Skills that share tags, products or a category with Verify UI Change: Actualize (NeoLabHQ/context-engineering-kit, 1.8k stars), Is This Actually Good (mohitagw15856/pm-claude-skills, 1.4k stars), Actual Budget (sundial-org/awesome-openclaw-skills, 663 stars) and Budget Cash Flow (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify UI Change?

reticlehq (a GitHub organization) maintains it in reticlehq/reticle, which has 1,199 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 9, 2026.

Source: reticlehq/reticle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.