Agent skill

Xcode Build Benchmark

by omarshahine in omarshahine/HomeClaw

Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts.

MITAuto-check passedMobile

Install Xcode Build Benchmark

skills CLI
$ npx skills add omarshahine/HomeClaw --skill xcode-build-benchmark -a claude-code

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

GitHub CLI
$ gh skill install omarshahine/HomeClaw xcode-build-benchmark --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/omarshahine/HomeClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/xcode-build-benchmark .claude/skills/xcode-build-benchmark && 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
xcode-build-benchmark
GitHub stars
176
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
490 words
Files
5 (incl. scripts, references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts.

  • Works in 8 steps: Normalize the build command and note… → Run one warm-up build if needed to… → Run 3 clean builds. → …
  • A developer wants a baseline
  • SKILL.md covers Core Rules, Inputs To Collect, Worktree Considerations and Default Workflow, plus 4 more sections
  • Runs Python scripts from its folder; calls python3 and xcodebuild

What it does

Xcode Build Benchmark is an agent skill from omarshahine/HomeClaw. Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/benchmark-artifacts.md`, `references/benchmarking-workflow.md` and `schemas/build-benchmark.schema.json`).

It sits in Mobile, covering iOS development. It works with Xcode. The repository describes itself as: HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw. The licence is MIT.

When your agent uses it

  • A developer wants a baseline
  • Wants to compare before and after changes
  • Asks to measure build performance
  • Mentions build times

Example prompts

  • “/xcode-build-benchmark”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Normalize the build command and note every flag that affects caching or module reuse.
  2. Run one warm-up build if needed to validate that the command succeeds.
  3. Run 3 clean builds.
  4. If COMPILATION_CACHE_ENABLE_CACHING = YES is detected, run 3 cached clean builds. These measure clean build time with a warm compilation…
  5. Run 3 zero-change builds (build immediately after a successful build with no edits). This measures the fixed overhead floor: dependency…
  6. Optionally run 3 incremental builds with a file touch to measure a real edit-rebuild loop. Use --touch-file path/to/SomeFile.swift to…
  7. Save the raw results and summary into .build-benchmark/.
  8. Report medians and spread, not just the single fastest run.

What it can do on your machine

Read from SKILL.md and the folder at commit cfc83ec. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • 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

Xcode Build Benchmark loads about 1.2k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 490 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from omarshahine/HomeClaw at commit cfc83ec, republished under its MIT licence (© omarshahine). 490 words, ~1,152 tokens.

Download SKILL.mdSave it as .claude/skills/xcode-build-benchmark/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
xcode-build-benchmark
description
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.

Xcode Build Benchmark

Use this skill to produce a repeatable Xcode build baseline before anyone tries to optimize build times.

Core Rules

  • Measure before recommending changes.
  • Capture clean and incremental builds separately.
  • Keep the command, destination, configuration, scheme, and warm-up rules consistent across runs.
  • Write a timestamped JSON artifact to .build-benchmark/.
  • Do not change project files as part of benchmarking.

Inputs To Collect

Confirm or infer:

  • workspace or project path
  • scheme
  • configuration
  • destination
  • whether the user wants simulator or device numbers
  • whether a custom DerivedData path is needed

If the project has both clean-build and incremental-build pain, benchmark both. That is the default.

Worktree Considerations

When benchmarking inside a git worktree, SPM packages with exclude: paths that reference gitignored directories (e.g., __Snapshots__) will cause xcodebuild -resolvePackageDependencies to crash. Create those missing directories before running any builds.

Default Workflow

  1. Normalize the build command and note every flag that affects caching or module reuse.
  2. Run one warm-up build if needed to validate that the command succeeds.
  3. Run 3 clean builds.
  4. If COMPILATION_CACHE_ENABLE_CACHING = YES is detected, run 3 cached clean builds. These measure clean build time with a warm compilation cache -- the realistic scenario for branch switching, pulling changes, or Clean Build Folder. The script handles this automatically by building once to warm the cache, then deleting DerivedData (but not the compilation cache) before each measured run. Pass --no-cached-clean to skip.
  5. Run 3 zero-change builds (build immediately after a successful build with no edits). This measures the fixed overhead floor: dependency computation, project description transfer, build description creation, script phases, codesigning, and validation. A zero-change build that takes more than a few seconds indicates avoidable per-build overhead. Use the default benchmark_builds.py invocation (no --touch-file flag).
  6. Optionally run 3 incremental builds with a file touch to measure a real edit-rebuild loop. Use --touch-file path/to/SomeFile.swift to touch a representative source file before each build.
  7. Save the raw results and summary into .build-benchmark/.
  8. Report medians and spread, not just the single fastest run.
Show full SKILL.md (155 more words)Show less

Preferred Command Path

Use the shared helper when possible:

bash
python3 scripts/benchmark_builds.py \
  --workspace App.xcworkspace \
  --scheme MyApp \
  --configuration Debug \
  --destination "platform=iOS Simulator,name=iPhone 16" \
  --output-dir .build-benchmark

If you cannot use the helper script, run equivalent xcodebuild commands with -showBuildTimingSummary and preserve the raw output.

Required Output

Return:

  • clean build median, min, max
  • cached clean build median, min, max (when COMPILATION_CACHE_ENABLE_CACHING is enabled)
  • zero-change build median, min, max (fixed overhead floor)
  • incremental build median, min, max (if --touch-file was used)
  • biggest timing-summary categories
  • environment details that could affect comparisons
  • path to the saved artifact

If results are noisy, say so and recommend rerunning under calmer conditions.

When To Stop

Stop after measurement if the user only asked for benchmarking. If they want optimization guidance, hand off the artifact to the relevant specialist by reading its SKILL.md and applying its workflow to the same project context:

Additional Resources

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

Files

SKILL.md and 4 other files (scripts, references) in .claude/skills/xcode-build-benchmark of omarshahine/HomeClaw.

  • SKILL.md
  • references/benchmark-artifacts.md
  • references/benchmarking-workflow.md
  • schemas/build-benchmark.schema.json
  • scripts/benchmark_builds.py

Open the folder on GitHubat commit cfc83ec

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in omarshahine/HomeClaw, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Xcode Build Benchmark 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.

Xcode Build Benchmark compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Xcode Build Benchmark this skillomarshahine/HomeClaw1761 repos~1.2kAutomated safety check: PassMIT
macOS Spm App PackagingDimillian/Skills4k5 repos~1.2kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca87k1 repos~584Automated safety check: PassApache-2.0
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT
Update Swiftui APIsAvdLee/SwiftUI-Agent-Skill3.7k—~1.2kAutomated safety check: PassMIT
iOS Simulator Skillconorluddy/ios-simulator-skill1.3k—~5.7kAutomated safety check: PassMIT

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…

    87k 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
  • Update Swiftui APIs

    AvdLee/SwiftUI-Agent-Skill

    Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements.

    3.7k GitHub stars~1.2k tokensUpdated yesterday
    MobileAuto-check passed
  • iOS Simulator Skill

    conorluddy/ios-simulator-skill

    29 production-ready scripts for iOS app testing, building, and automation.

    1.3k GitHub stars~5.7k tokensUpdated yesterday
    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 today
    MobileAuto-check passed

More from omarshahine/HomeClaw

All 13 skills in this repo
  • Spm Build Analysis

    omarshahine/HomeClaw

    Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds.

    176 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Xcode Build Fixer

    omarshahine/HomeClaw

    Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement.

    176 GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • Xcode Build Orchestrator

    omarshahine/HomeClaw

    Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to…

    176 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Xcode Compilation Analyzer

    omarshahine/HomeClaw

    Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan.

    176 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • iOS Ettrace Performance

    omarshahine/HomeClaw

    Capture and interpret ETTrace profiles for iOS simulator apps, including symbolicated launch and runtime flamegraphs.

    176 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • iOS Memgraph Leaks

    omarshahine/HomeClaw

    Capture, inspect, compare, and root-cause iOS memory graph leaks using Apple's leaks and memgraph tools.

    176 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

Works with

Categories

Questions about Xcode Build Benchmark

What does Xcode Build Benchmark do?

Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts. Xcode Build Benchmark is an agent skill from omarshahine/HomeClaw.build-benchmark/ artifacts.

When should I use Xcode Build Benchmark?

Xcode Build Benchmark fits situations like: A developer wants a baseline; wants to compare before and after changes; asks to measure build performance; mentions build times.

How do I install Xcode Build Benchmark in Claude Code?

Run `npx skills add omarshahine/HomeClaw --skill xcode-build-benchmark -a claude-code`. Or copy the skill folder (.claude/skills/xcode-build-benchmark in omarshahine/HomeClaw) into .claude/skills/xcode-build-benchmark in your project. Claude Code loads it when a task matches its description.

How do I install Xcode Build Benchmark in Codex?

Run `npx skills add omarshahine/HomeClaw --skill xcode-build-benchmark -a codex`. Or copy the skill folder (.claude/skills/xcode-build-benchmark in omarshahine/HomeClaw) into .agents/skills/xcode-build-benchmark in your project. Codex loads it when a task matches its description.

Can I use Xcode Build Benchmark 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 omarshahine/HomeClaw --skill xcode-build-benchmark -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xcode-build-benchmark, .gemini/skills/xcode-build-benchmark, .github/skills/xcode-build-benchmark and .opencode/skills/xcode-build-benchmark in your project.

What does Xcode Build Benchmark need to run?

Going by SKILL.md and its folder, Xcode Build Benchmark needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and xcodebuild). Our summary lists: Python 3.

Does Xcode Build Benchmark 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 Xcode Build Benchmark 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Xcode Build Benchmark use?

Xcode Build Benchmark 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 Xcode Build Benchmark use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Xcode Build Benchmark?

Skills that share tags, products or a category with Xcode Build Benchmark: macOS Spm App Packaging (Dimillian/Skills, 4k stars), Orca iOS Simulator Control (stablyai/orca, 87k stars), Apple Crash Log .NET Symbolication (dotnet/skills, 5.6k stars) and Update Swiftui APIs (AvdLee/SwiftUI-Agent-Skill, 3.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Xcode Build Benchmark?

omarshahine (a GitHub user) maintains it in omarshahine/HomeClaw, which has 176 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 3, 2026.

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