How do I install the Verify skill?

Run npx skillmds@latest add ai4s-research/verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Verify skill do?

Verify apps/desktop frontend changes visually without launching the Tauri app or a live model It is listed under Web & Frontend on SkillMD.

Is Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Verify?

ai4s-research (@ai4s-research) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify by ai4s-research — Agent Skill

Name: Verify
Author: ai4s-research

File contents

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:

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.
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.
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".
Clean up: closeTab, kill the vite pid, delete both harness files, confirm git status is clean.

Frequently asked questions

Verify