How do I install the Verify skill?

Run npx skillmds@latest add joelbqz/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?

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

Verify by joelbqz — Agent Skill

Name: Verify
Author: joelbqz

File contents

Verifying Writer desktop changes

The surface is a macOS Tauri GUI. Drive it through the repo's WebdriverIO + tauri-webdriver harness in apps/desktop/e2e/ (see its README for one-time setup: cargo install tauri-webdriver --locked).

Build

cd apps/desktop/src-tauri
cargo tauri build --features e2e --bundles app --ignore-version-mismatches \
  --config '{"identifier":"com.writer-computer.e2e","bundle":{"createUpdaterArtifacts":false}}'

Gotchas:

--ignore-version-mismatches is required while the npm @tauri-apps/* packages lag the Rust crates; without it the CLI hard-errors before building.
The bundle lands at src-tauri/target/release/bundle/macos/Writer.app/Contents/MacOS/desktop (binary keeps the crate name). Incremental rebuilds are fast; the first build is slow.
Rebuild after every frontend change too — the app ships the built assets.

Launch state

The e2e app uses its own data dir: ~/Library/Application Support/com.writer-computer.e2e. Fresh dir → welcome screen (workspace opens need a native dialog you cannot drive). To land in a workspace, seed before launch:

printf '["/abs/path/to/workspace-dir"]' > \
  "$HOME/Library/Application Support/com.writer-computer.e2e/recent_workspaces.json"

Startup restores recent_workspaces[0] when it is a directory. Wipe the data dir between runs for deterministic settings.

Drive

cd apps/desktop/e2e
pnpm exec wdio run ./wdio.conf.js --spec ./specs/<your>.spec.js

Wait for button[aria-label="Hide sidebar"] to detect mount+restore. Do NOT wait for .animate-fade-in — that wrapper no longer exists (the smoke spec still references it and fails; known rot).
Key chords through the driver are flaky on WKWebView; dispatch synthetic KeyboardEvents via browser.execute instead (Cmd+P opens the palette; palette items are [cmdk-item][data-value="<command-id>"]).
setValue on empty inputs can throw in the driver's clear step — use addValue.
Real Rust IPC is reachable via window.__TAURI_INTERNALS__.invoke(cmd, args) inside browser.executeAsync (see specs/smoke.spec.js).
Screenshots: browser.saveScreenshot(absPath).
specs/font-picker.spec.js self-skips when no workspace restored; it's a working example of palette → settings → popover driving.

---name: verifydescription: Build, launch, and drive the Writer desktop app to verify a change end-to-end via the WebDriver e2e harness. Use when a change to apps/desktop needs runtime verification (GUI surface).---# Verifying Writer desktop changesThe surface is a macOS Tauri GUI. Drive it through the repo's WebdriverIO +tauri-webdriver harness in `apps/desktop/e2e/` (see its README for one-timesetup: `cargo install tauri-webdriver --locked`).## Build```shcd apps/desktop/src-tauricargo tauri build --features e2e --bundles app --ignore-version-mismatches \ --config '{"identifier":"com.writer-computer.e2e","bundle":{"createUpdaterArtifacts":false}}'```Gotchas:- `--ignore-version-mismatches` is required while the npm `@tauri-apps/*` packages lag the Rust crates; without it the CLI hard-errors before building.- The bundle lands at `src-tauri/target/release/bundle/macos/Writer.app/Contents/MacOS/desktop` (binary keeps the crate name). Incremental rebuilds are fast; the first build is slow.- Rebuild after every frontend change too — the app ships the built assets.## Launch stateThe e2e app uses its own data dir:`~/Library/Application Support/com.writer-computer.e2e`. Fresh dir → welcomescreen (workspace opens need a native dialog you cannot drive). To land in aworkspace, seed before launch:```shprintf '["/abs/path/to/workspace-dir"]' > \ "$HOME/Library/Application Support/com.writer-computer.e2e/recent_workspaces.json"```Startup restores `recent_workspaces[0]` when it is a directory. Wipe the datadir between runs for deterministic settings.## Drive```shcd apps/desktop/e2epnpm exec wdio run ./wdio.conf.js --spec ./specs/<your>.spec.js```- Wait for `button[aria-label="Hide sidebar"]` to detect mount+restore. Do NOT wait for `.animate-fade-in` — that wrapper no longer exists (the smoke spec still references it and fails; known rot).- Key chords through the driver are flaky on WKWebView; dispatch synthetic `KeyboardEvent`s via `browser.execute` instead (Cmd+P opens the palette; palette items are `[cmdk-item][data-value="<command-id>"]`).- `setValue` on empty inputs can throw in the driver's `clear` step — use `addValue`.- Real Rust IPC is reachable via `window.__TAURI_INTERNALS__.invoke(cmd, args)` inside `browser.executeAsync` (see `specs/smoke.spec.js`).- Screenshots: `browser.saveScreenshot(absPath)`.- `specs/font-picker.spec.js` self-skips when no workspace restored; it's a working example of palette → settings → popover driving.

Frequently asked questions

Verify