How do I install the Verify skill?

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

Build, relaunch, and observe the Claudence menu bar app to verify a change end-to-end. It is listed under Coding & Dev Tools on SkillMD.

Is Verify safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. 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?

Mark-in-Motion (@mark-in-motion) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify by mark-in-motion — Agent Skill

Name: Verify
Rating: 4.5 (4 reviews)
Author: Mark-in-Motion

File contents

Verifying Claudence changes

Claudence is a macOS menu bar app (SwiftUI, Xcode project + SwiftPM package in the same repo).

Build

Unit-test/compile loop: swift build and swift test from the repo root (fast, seconds).
Real app bundle: xcodebuild -scheme Claudence -configuration Debug build (single scheme Claudence; output lands in ~/Library/Developer/Xcode/DerivedData/Claudence-*/Build/Products/Debug/Claudence.app).

Relaunch

The user usually has a Debug instance running from DerivedData. To swap in a new build:

pkill -x Claudence; sleep 1; open ~/Library/Developer/Xcode/DerivedData/Claudence-*/Build/Products/Debug/Claudence.app

Keychain session key (com.claudence.session / default) survives relaunch; the app fetches live usage within seconds of launch.

Observe (no accessibility access needed)

The popover can't be opened programmatically (osascript lacks assistive access), but the app persists everything it renders:

Current snapshot: ~/Library/Application Support/Claudence/Snapshots/current_snapshot.json (also last_known_good_snapshot.json; check fetchedAt to confirm a fresh live fetch happened after relaunch)
History: ~/Library/Application Support/Claudence/History/usage_history.json (appended on each live fetch)
Diagnostics/errors: ~/Library/Application Support/Claudence/diagnostics.json
Settings: ~/Library/Application Support/Claudence/settings.json (session key is NOT here, it's in the Keychain)

For UI-only changes, ask the user to click the menu bar icon and screenshot — programmatic capture is blocked without accessibility + screen-recording permissions.

Gotchas

grep --include=*.swift fails under zsh globbing; quote it or use -r ... --include "*.swift".
Reading the keychain item from a script triggers a blocking permission dialog — don't; let the app do the fetch and read its output files instead.

---name: verifydescription: Build, relaunch, and observe the Claudence menu bar app to verify a change end-to-end.---# Verifying Claudence changesClaudence is a macOS menu bar app (SwiftUI, Xcode project + SwiftPM package in the same repo).## Build- Unit-test/compile loop: `swift build` and `swift test` from the repo root (fast, seconds).- Real app bundle: `xcodebuild -scheme Claudence -configuration Debug build` (single scheme `Claudence`; output lands in `~/Library/Developer/Xcode/DerivedData/Claudence-*/Build/Products/Debug/Claudence.app`).## RelaunchThe user usually has a Debug instance running from DerivedData. To swap in a new build:```bashpkill -x Claudence; sleep 1; open ~/Library/Developer/Xcode/DerivedData/Claudence-*/Build/Products/Debug/Claudence.app```Keychain session key (`com.claudence.session` / `default`) survives relaunch; the app fetches live usage within seconds of launch.## Observe (no accessibility access needed)The popover can't be opened programmatically (osascript lacks assistive access), but the app persists everything it renders:- Current snapshot: `~/Library/Application Support/Claudence/Snapshots/current_snapshot.json` (also `last_known_good_snapshot.json`; check `fetchedAt` to confirm a fresh live fetch happened after relaunch)- History: `~/Library/Application Support/Claudence/History/usage_history.json` (appended on each live fetch)- Diagnostics/errors: `~/Library/Application Support/Claudence/diagnostics.json`- Settings: `~/Library/Application Support/Claudence/settings.json` (session key is NOT here, it's in the Keychain)For UI-only changes, ask the user to click the menu bar icon and screenshot — programmatic capture is blocked without accessibility + screen-recording permissions.## Gotchas- `grep --include=*.swift` fails under zsh globbing; quote it or use `-r ... --include "*.swift"`.- Reading the keychain item from a script triggers a blocking permission dialog — don't; let the app do the fetch and read its output files instead.

Frequently asked questions

Verify