spm-build-analysis skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
spm-build-analysis is agent-read markdown (skill) from omarshahine/homeclaw: Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices..
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
# SPM Build Analysis Use this skill when package structure, plugins, or dependency configuration are likely contributing to slow Xcode builds. ## Core Rules - Treat package analysis as evidence gathering first, not a mandate to replace dependencies. - Separate package-graph issues from project-setting issues. - Do not rewrite package manifests or dependency sources without explicit approval. ## What To Inspect - `Package.swift` and `Package.resolved` - local packages vs remote packages - package plugin and build-tool usage - binary target footprint - dependency layering, repeated imports, and potential cycles - build logs or timing summaries that show package-related work ## Verification Before Recommending Before including any local package in a recommendation, verify that it is actually part of the project's dependency graph. A `Vendor/` directory may contain packages that are not linked to any target. - Check `project.pbxproj` for `XCLocalSwiftPackageReference` entries that reference the package path. - Check `XCSwiftPackageProductDependency` entries to confirm the package's product is linked to at least one target. …
Read the whole file at its exact version.
How to install
mdr add omarshahine/homeclaw/spm-build-analysis@git:20260510.35d37d5mdr add omarshahine/homeclaw/spm-build-analysis@sha256:4ac9f10fac0ead18Pin 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_zbjpb4hd56v4qods)
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 (6117 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_zbjpb4hd56v4qods GET https://markdownregistry.com/api/v1/resolve?ref=omarshahine/homeclaw/spm-build-analysis GET https://markdownregistry.com/api/v1/blob/4ac9f10fac0ead182a0caa86f5e36eb11436db327f6b47c08c655ea5eb1afa48
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