xcode-build-benchmark skillA
xcode-build-benchmark is agent-read markdown (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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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. …
Read the whole file at its exact version.
How to install
mdr add omarshahine/homeclaw/xcode-build-benchmark@git:20260510.35d37d5mdr add omarshahine/homeclaw/xcode-build-benchmark@sha256:91b85f1b9b734412Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_nfyhw2owml4zbwpj)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4608 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
omarshahine/homeclaw · 173 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nfyhw2owml4zbwpj GET https://markdownregistry.com/api/v1/resolve?ref=omarshahine/homeclaw/xcode-build-benchmark GET https://markdownregistry.com/api/v1/blob/91b85f1b9b7344123178d23896f5cc7e0c6bcfdbb05aa670c0ba1411ba72a3bd
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from omarshahine/homeclaw
Every file in omarshahine/homeclaw