How do I install the Verify skill?

Run npx skillmds@latest add fabro-sh/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.

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?

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

Verify by fabro-sh — Agent Skill

Name: Verify
Author: fabro-sh

File contents

Verifying Quarry end-to-end

Build + launch

cd ui && bun run build          # rebuild the browser bundle (server serves ui/dist)
cd .. && cargo run -q -p quarry -- server init --root <scratch-dir>/.quarry
cargo run -q -p quarry -- server start --root <scratch-dir>/.quarry --addr 127.0.0.1:<port>

Use a fresh scratch dir + fresh port. Check lsof -nP -iTCP:<port> -sTCP:LISTEN first — stale quarry servers from earlier sessions linger (5273 and 7831 are commonly taken) and will silently serve you their own state.
Confirm you're talking to your build: curl -s http://127.0.0.1:<port>/tmp | grep -o 'assets/index[^"]*' and match the hash against ui/dist/assets/. (/ serves the static marketing page, not the SPA — use a SPA route like /tmp.)

Drive the UI (browser-use)

There is no gate on first load. A name prompt ("What's your name?", with a "Skip for now" option) appears only on the first "Add agent" click when no author is stored.
Create a document: visit /tmp/new (auto-creates a welcome doc), use the empty-state "New document" button on /tmp, or ⌘K → "Create document". The URL becomes /tmp/<secret> — same shape as production tmp links.
To type into the editor you must click into the document body first (e.g. coordinates mid-page); keyboard input without that focus lands nowhere and fails silently.
browser-use eval does not await async IIFEs — kick off promises in one eval, read results in a second.

Gotchas

The production CSP (crates/quarry-server/src/lib.rs) is strict: no data: fonts, no third-party origins. performance.getEntriesByType('resource') filtered by !u.startsWith(location.origin) catches violations; [...document.fonts].filter(f => f.status === 'error') catches blocked fonts.
Vite dev server (:5173) does not send the CSP — CSP bugs only reproduce against the real server.

---name: verifydescription: Build, launch, and drive the Quarry server + embedded browser UI for end-to-end verification of a change.---# Verifying Quarry end-to-end## Build + launch```shcd ui && bun run build # rebuild the browser bundle (server serves ui/dist)cd .. && cargo run -q -p quarry -- server init --root <scratch-dir>/.quarrycargo run -q -p quarry -- server start --root <scratch-dir>/.quarry --addr 127.0.0.1:<port>```- Use a fresh scratch dir + fresh port. **Check `lsof -nP -iTCP:<port> -sTCP:LISTEN` first** — stale quarry servers from earlier sessions linger (5273 and 7831 are commonly taken) and will silently serve you their own state.- Confirm you're talking to your build: `curl -s http://127.0.0.1:<port>/tmp | grep -o 'assets/index[^"]*'` and match the hash against `ui/dist/assets/`. (`/` serves the static marketing page, not the SPA — use a SPA route like `/tmp`.)## Drive the UI (browser-use)1. There is no gate on first load. A name prompt ("What's your name?", with a "Skip for now" option) appears only on the first "Add agent" click when no author is stored.2. Create a document: visit `/tmp/new` (auto-creates a welcome doc), use the empty-state "New document" button on `/tmp`, or `⌘K` → "Create document". The URL becomes `/tmp/<secret>` — same shape as production tmp links.3. To type into the editor you must **click into the document body first** (e.g. coordinates mid-page); keyboard input without that focus lands nowhere and fails silently.4. `browser-use eval` does not await async IIFEs — kick off promises in one eval, read results in a second.## Gotchas- The production CSP (`crates/quarry-server/src/lib.rs`) is strict: no `data:` fonts, no third-party origins. `performance.getEntriesByType('resource')` filtered by `!u.startsWith(location.origin)` catches violations; `[...document.fonts].filter(f => f.status === 'error')` catches blocked fonts.- Vite dev server (:5173) does not send the CSP — CSP bugs only reproduce against the real server.

Frequently asked questions

Verify