Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Security Analysis
high confidenceThe skill is an instruction-only SwiftUI performance reviewer whose requested inputs and actions align with its stated purpose and it does not ask for unrelated credentials, installs, or system access.
Name/description match SKILL.md: the skill performs code review and guided Instruments profiling for SwiftUI performance. It requests code, symptoms, and traces — all proportional to the stated goal; no unrelated binaries, env vars, or config paths are required.
Runtime instructions stay within scope: request user code, reproduction steps, and Instruments traces/screenshots; advise on profiling and remediation. There are no instructions to read local system files, environment variables, or send data to external endpoints other than asking the user to provide traces/screenshots.
No install spec and no code files — instruction-only skill. Nothing is written to disk or downloaded, minimizing install risk.
The skill requires no environment variables, credentials, or config paths. All requested inputs (code, traces, device/build info) are reasonable for a performance audit.
always is false and there is no request to modify other skills or system-wide settings. disable-model-invocation remains default (allowed), which is normal for skills and not concerning by itself.
Guidance
This skill is internally consistent and appears to do what it says: code review and guidance for Instruments traces. Before installing or using it, note that (a) the skill has no published homepage or known source author — you may want to vet provenance if that matters to you; (b) it will ask you to share source code and profiling traces — sanitize or remove secrets, API keys, entitlements, or proprietary data before sharing; and (c) when asked to run Instruments, follow instructions carefully and only share the specific traces/screenshots needed for diagnosis. If you require stronger guarantees about origin, ask the publisher for a repo/homepage or prefer a skill from a known author/organization.
Latest Release
v1.0.0
More by @steipete
Published by @steipete on ClawHub
