Agent skill

Build And Run Kaze

by fayazara in fayazara/Kaze

Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), and launch the fresh build.

MITAuto-check passedMobile

Install Build And Run Kaze

skills CLI
$ npx skills add fayazara/Kaze --skill build-and-run-kaze -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fayazara/Kaze build-and-run-kaze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fayazara/Kaze.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/build-and-run-kaze .claude/skills/build-and-run-kaze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
build-and-run-kaze
GitHub stars
192
Token cost
~1k tokens
SKILL.md length
423 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), and launch the fresh build.

  • The user asks to run
  • SKILL.md covers Steps, When to Use and Notes
  • Calls xcodebuild
  • Try out the app

What it does

Build And Run Kaze is an agent skill from fayazara/Kaze. Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), 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'.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile. It works with Xcode and macOS. The repository describes itself as: Local speech to text app - Talk instead of typing. The licence is MIT.

When your agent uses it

  • The user asks to run
  • Try out the app
  • Says things like build and run
  • Restart the app

Example prompts

  • “build and run”
  • “restart the app”
  • “/build-and-run-kaze”

What it can do on your machine

Read from SKILL.md and the folder at commit ee8fb5c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • xcodebuild

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build And Run Kaze loads about 1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 423 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fayazara/Kaze at commit ee8fb5c, republished under its MIT licence (© fayazara). 423 words, ~1,024 tokens.

Download SKILL.mdSave it as .claude/skills/build-and-run-kaze/SKILL.md (or your agent's skills folder).
name
build-and-run-kaze
description
Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), 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 Kaze

This skill builds the Kaze macOS application via xcodebuild, kills any running instance of the app (regardless of which scheme it was launched from), then launches the newly built app.

Steps

  1. Pick a scheme. List the schemes available in the project:
bash
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild \
  -project "/Users/fayazahmed/Developer/fayazara/mac/Kaze/Kaze.xcodeproj" \
  -list 2>/dev/null | sed -n '/Schemes:/,$p' | tail -n +2
  • The app schemes are Kaze Dev (Debug, bundle com.fayazahmed.Kaze.dev, product Kaze Dev.app) and Kaze (Release, bundle com.fayazahmed.Kaze). Ignore package schemes such as argmax-oss-swift-Package.
  • Default to Kaze Dev unless the user names a scheme or asks for a Release build. The Dev build has its own bundle ID, so it keeps separate settings and permissions from an installed release copy.
  1. Resolve build settings for the chosen scheme - don't hardcode the configuration or output path, since it varies per scheme:
bash
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild \
  -project "/Users/fayazahmed/Developer/fayazara/mac/Kaze/Kaze.xcodeproj" \
  -scheme "<SCHEME_NAME>" -showBuildSettings 2>/dev/null \
  | grep -E "^\s*(CONFIGURATION|BUILT_PRODUCTS_DIR|FULL_PRODUCT_NAME|EXECUTABLE_NAME) "

Use CONFIGURATION for the -configuration flag in the build step, and BUILT_PRODUCTS_DIR + FULL_PRODUCT_NAME to construct the .app path for the run step.

  1. Build the project with the resolved scheme/configuration:
bash
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild build \
  -project "/Users/fayazahmed/Developer/fayazara/mac/Kaze/Kaze.xcodeproj" \
  -scheme "<SCHEME_NAME>" \
  -configuration "<CONFIGURATION>" \
  -destination "platform=macOS" \
  2>&1 | grep -E "(BUILD SUCCEEDED|BUILD FAILED|error:)" | head -20

If the output shows BUILD FAILED, stop here, read the error: lines, and help the user fix them. Do not proceed to run a broken build. If the output is empty or unclear, re-run without the grep filter to get full output for diagnosis.

  1. Kill every running instance of the app, across all schemes - not just the one being launched. The two schemes produce different executable names (Kaze, Kaze Dev), and leaving an old instance running is confusing (duplicate menu bar icons, two event taps fighting over the shortcut):
bash
killall Kaze 2>/dev/null
killall "Kaze Dev" 2>/dev/null

(It's fine if these error because that variant wasn't running. If a new scheme is added later with a different EXECUTABLE_NAME, add its killall line here too - check with EXECUTABLE_NAME from step 2.)

  1. Run the freshly built app using the path resolved in step 2:
bash
open "<BUILT_PRODUCTS_DIR>/<FULL_PRODUCT_NAME>"
Show full SKILL.md (132 more words)Show less

When to Use

  • User says "run it", "build and run", "try it out", "relaunch the app"
  • After making code changes, when the user wants to see the change live rather than just verify it compiles (for compile-only checks, use build-kaze instead)

Notes

  • DerivedData paths are specific to this machine/checkout and can change between clean builds - always resolve BUILT_PRODUCTS_DIR via -showBuildSettings (step 2) rather than assuming a fixed path.
  • Kaze is a menu bar app (LSUIElement), so no Dock icon or window appears on launch unless onboarding hasn't been completed. Look for its menu bar icon.
  • The shortcut needs Accessibility permission. A rebuilt app with a new code signature may need to be re-enabled in System Settings > Privacy & Security > Accessibility before the shortcut works again.
  • Logs: log stream --predicate 'subsystem == "com.fayazahmed.Kaze"' --level debug

© fayazara, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/build-and-run-kaze of fayazara/Kaze.

Open the folder on GitHubat commit ee8fb5c

Compare with similar skills

Build And Run Kaze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build And Run Kaze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build And Run Kaze this skillfayazara/Kaze192—~1kAutomated safety check: PassMIT
macOS Spm App PackagingDimillian/Skills4k5 repos~1.2kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca89k1 repos~584Automated safety check: PassApache-2.0
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT
App Store Preflight Skillstruongduy2611/app-store-preflight-skills1.4k—~1.4kAutomated safety check: PassMIT
Build And Run Screendropfayazara/Screendrop2.2k—~1.1kAutomated safety check: PassCC0-1.0

Similar skills

  • macOS Spm App Packaging

    Dimillian/Skills

    Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project.

    4k GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed
  • iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…

    89k GitHub starsUsed in 1 repo~584 tokens
    MobileAuto-check passed
  • Official

    Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.

    5.6k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed
  • App Store Preflight Skills

    truongduy2611/app-store-preflight-skills

    Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission.

    1.4k GitHub stars~1.4k tokensUpdated 4 mo ago
    MobileAuto-check passed
  • Build And Run Screendrop

    fayazara/Screendrop

    Build the Screendrop macOS app with xcodebuild, kill any running instance (of any scheme), and launch the fresh build.

    2.2k GitHub stars~1.1k tokensUpdated 9 days ago
    MobileAuto-check passed
  • Official

    Update dotnet/macios to a new Xcode beta and validate it end-to-end.

    2.9k GitHub stars~1.8k tokensUpdated 2 days ago
    MobileAuto-check passed

More from fayazara/Kaze

  • Release Kaze

    fayazara/Kaze

    Release the Kaze macOS app to GitHub using the kaze-release CLI tool.

    192 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Build Kaze

    fayazara/Kaze

    Build the Kaze macOS app using xcodebuild. An agent skill from fayazara/Kaze.

    192 GitHub stars~446 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Build And Run Kaze

What does Build And Run Kaze do?

Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), and launch the fresh build. Build And Run Kaze is an agent skill from fayazara/Kaze. Build the Kaze macOS app with xcodebuild, kill any running instance (of any scheme), and launch the fresh build.

When should I use Build And Run Kaze?

Build And Run Kaze fits situations like: the user asks to run; try out the app; says things like build and run; restart the app.

How do I install Build And Run Kaze in Claude Code?

Run `npx skills add fayazara/Kaze --skill build-and-run-kaze -a claude-code`. Or copy the skill folder (.agents/skills/build-and-run-kaze in fayazara/Kaze) into .claude/skills/build-and-run-kaze in your project. Claude Code loads it when a task matches its description.

How do I install Build And Run Kaze in Codex?

Run `npx skills add fayazara/Kaze --skill build-and-run-kaze -a codex`. Or copy the skill folder (.agents/skills/build-and-run-kaze in fayazara/Kaze) into .agents/skills/build-and-run-kaze in your project. Codex loads it when a task matches its description.

Can I use Build And Run Kaze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fayazara/Kaze --skill build-and-run-kaze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-and-run-kaze, .gemini/skills/build-and-run-kaze, .github/skills/build-and-run-kaze and .opencode/skills/build-and-run-kaze in your project.

What does Build And Run Kaze need to run?

Going by SKILL.md and its folder, Build And Run Kaze needs the command-line tools its instructions call (xcodebuild).

Does Build And Run Kaze access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Build And Run Kaze safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Build And Run Kaze use?

Build And Run Kaze is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build And Run Kaze use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Build And Run Kaze?

Skills that share tags, products or a category with Build And Run Kaze: macOS Spm App Packaging (Dimillian/Skills, 4k stars), Orca iOS Simulator Control (stablyai/orca, 89k stars), Apple Crash Log .NET Symbolication (dotnet/skills, 5.6k stars) and App Store Preflight Skills (truongduy2611/app-store-preflight-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build And Run Kaze?

fayazara (a GitHub user) maintains it in fayazara/Kaze, which has 192 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

Source: fayazara/Kaze on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.