Verify
Verify apps/desktop frontend changes visually without launching the Tauri app or a live model
Install
npx skills add ai4s-research/open-science --skill verifygit clone --depth 1 https://github.com/ai4s-research/open-science.git /tmp/open-science
mkdir -p ~/.claude/skills
cp -r /tmp/open-science/apps/desktop/.claude/skills/verify ~/.claude/skills/verifyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Verifying desktop frontend changes Full-app runs need an OpenCode session + live model turn. For pure frontend component changes, mount the component in a throwaway vite page instead: 1. Create `apps/desktop/verify-<x>.html` (plain html, `<div id="root">`, `<script type="module" src="/src/verify-<x>.tsx">`) and `apps/desktop/src/verify-<x>.tsx` (ReactDOM.createRoot, import `./index.css` for Tailwind, import the component via `@/`). Vite serves any .html under `apps/desktop/` automatically. 2. `cd apps/desktop && npx vite --port 5199 --strictPort` (background). The npx wrapper may double-spawn and report "port in use" failure while the first instance is fine — check `lsof -iTCP:5199` before retrying. 3. Drive with the browser-control skill (Chrome HTTP API, port 9528): `createWindow` → `waitForSelector` → `readDom` → `screenshotTab` (screenshots land in `~/Downloads/`). Gotchas: `evalScript` is blocked by CSP on the extension — use `readDom`/`scrollTab` instead; `readDom` requires an explicit `"attributes": []` or it errors with "Value is unserializable". 4. Clean up: `closeTab`, kill the vite pid, delete both harness files, confirm `git status` is clean.
Details
- Skill name
verify- Repository
- ai4s-research/open-science
- Path
apps/desktop/.claude/skills/verify/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Verify skill do?
Verify apps/desktop frontend changes visually without launching the Tauri app or a live model
How do I install the Verify skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ai4s-research/open-science --skill verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Verify popular?
It lives in ai4s-research/open-science, which has 2,105 GitHub stars and 231 forks.
Related skills
Computer Use
2.1kai4s-research/open-science
Use when a task needs an app on the user's own screen — a native desktop application (instrument control software, Origin, GraphPad, ImageJ, a reference manager, a spreadsheet), or a desktop browser window that needs window-level control. Read before the first `computer` call. Covers the observe-act-observe loop, why element indexes go stale, which action to prefer for which control, what "unverified" means and why it must never be reported as success, and the recovery for each error code. Not for page-level web automation (use the browser connector) and not for anything that can be done from
Domain Check
2.1kai4s-research/open-science
Use ONLY when the user asks to check, validate, review or audit analysis code for scientific correctness, or when you are the reviewer agent running its checks. Never run it unprompted as part of ordinary analysis work. Covers physics, earth/geo, biology, chemistry, social science and bioprocess/fermentation. Runs a deterministic domain-correctness gate that catches code which runs but is scientifically wrong (unit/dimension mismatch, Euclidean distance on lat/lon without a CRS, 0-based/1-based coordinate and strand errors, impossible SMILES valence, uncorrected multiple comparisons, averaging
Large File
2.1kai4s-research/open-science
Use BEFORE reading any data file that could be large (CSV/TSV, Parquet, HDF5, FITS, NetCDF, NDJSON, genomics FASTQ/FASTA/VCF/BAM, GRIB, ROOT, or big text/simulation logs like VASP OUTCAR). Returns a compact memory pointer — header/schema/shape/sample/key numbers — by introspection and sampling in bounded memory, so you never load a file bigger than the context window into the model. Reference data via the pointer; read specific ranges deterministically.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Frontend Dev Guidelines
2.2kmrgoonie/claudekit-skills
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.
Affinity Diagram
3.4kOwl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.