How do I install the Build And Run Boop skill?

Run npx skillmds@latest add fayazara/build-and-run-boop 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 Build And Run Boop 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 Build And Run Boop?

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 Build And Run Boop free to use?

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

Who published Build And Run Boop?

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

Build And Run Boop by fayazara — Agent Skill

Name: Build And Run Boop
Author: fayazara

Build And Run Boop

Build the Boop macOS app with xcodebuild, kill any running instance, and launch the fresh build. Use this skill whenever the user asks to run, launch, relaunch, or try out the app, or says things like 'build and run' or 'restart the app'.

fayazara Updated Sep 17, 2026

File contents

Build and Run Boop

Builds Boop via xcodebuild, kills any running instance, then launches the newly built app.

Steps

Resolve build settings — don't hardcode the output path, DerivedData paths change between clean builds:

DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild \
  -project "/Users/fayazahmed/Developer/fayazara/mac/Boop/Boop.xcodeproj" \
  -scheme Boop -showBuildSettings 2>/dev/null \
  | grep -E "^\s*(CONFIGURATION|BUILT_PRODUCTS_DIR|FULL_PRODUCT_NAME|EXECUTABLE_NAME) "

Build:

DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild build \
  -project "/Users/fayazahmed/Developer/fayazara/mac/Boop/Boop.xcodeproj" \
  -scheme Boop \
  -configuration Debug \
  -destination "platform=macOS" \
  2>&1 | grep -E "(BUILD SUCCEEDED|BUILD FAILED|error:)" | head -20

If the output shows BUILD FAILED, stop, read the error: lines, and fix them. Do not run a broken build.

Kill every running instance. Boop is a menu-bar agent with no Dock icon, so stale copies are easy to miss — and each one registers the same global hot key, which makes the app look broken. Always check for more than one:

pgrep -fl "Boop.app/Contents/MacOS/Boop"
killall Boop 2>/dev/null

Run using the path resolved in step 1:

open "<BUILT_PRODUCTS_DIR>/<FULL_PRODUCT_NAME>"

Notes

Boop needs Accessibility permission to read the selection and paste. macOS ties that grant to the binary's signature, so a rebuild can silently revoke it. If the hot key stops doing anything, re-add the app under System Settings → Privacy & Security → Accessibility.
Debug builds skip the Sparkle updater entirely.

---name: build-and-run-boopdescription: Build the Boop macOS app with xcodebuild, kill any running instance, and launch the fresh build. Use this skill whenever the user asks to run, launch, relaunch, or try out the app, or says things like 'build and run' or 'restart the app'.---# Build and Run BoopBuilds Boop via `xcodebuild`, kills any running instance, then launches thenewly built app.## Steps1. **Resolve build settings** — don't hardcode the output path, DerivedData paths change between clean builds:```bashDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild \ -project "/Users/fayazahmed/Developer/fayazara/mac/Boop/Boop.xcodeproj" \ -scheme Boop -showBuildSettings 2>/dev/null \ | grep -E "^\s*(CONFIGURATION|BUILT_PRODUCTS_DIR|FULL_PRODUCT_NAME|EXECUTABLE_NAME) "```2. **Build**:```bashDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild build \ -project "/Users/fayazahmed/Developer/fayazara/mac/Boop/Boop.xcodeproj" \ -scheme Boop \ -configuration Debug \ -destination "platform=macOS" \ 2>&1 | grep -E "(BUILD SUCCEEDED|BUILD FAILED|error:)" | head -20```If the output shows `BUILD FAILED`, stop, read the `error:` lines, and fix them.Do not run a broken build.3. **Kill every running instance.** Boop is a menu-bar agent with no Dock icon, so stale copies are easy to miss — and each one registers the same global hot key, which makes the app look broken. Always check for more than one:```bashpgrep -fl "Boop.app/Contents/MacOS/Boop"killall Boop 2>/dev/null```4. **Run** using the path resolved in step 1:```bashopen "<BUILT_PRODUCTS_DIR>/<FULL_PRODUCT_NAME>"```## Notes- Boop needs **Accessibility** permission to read the selection and paste. macOS ties that grant to the binary's signature, so a rebuild can silently revoke it. If the hot key stops doing anything, re-add the app under System Settings → Privacy & Security → Accessibility.- Debug builds skip the Sparkle updater entirely.

Frequently asked questions