Swiftui Performance Audit

v1.0.0

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memor...

0· 71·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the SKILL.md guidance: it focuses on SwiftUI runtime performance, code review, and profiling. No unrelated capabilities, binaries, or credentials are requested.
Instruction Scope
Runtime instructions stay on-topic: collecting view code, state flows, Instruments traces/screenshots, and producing remediation. There are no instructions to read system-wide config, credentials, or unrelated files. It does ask users to share traces/screenshots and device/build info, which is appropriate for profiling.
Install Mechanism
No install spec and no code files — the skill is instruction-only. That minimizes disk writes and execution of downloaded code.
Credentials
The skill declares no environment variables, credentials, or config paths. The guidance legitimately asks for source code and profiling traces only.
Persistence & Privilege
always is false and model invocation is allowed (default). The skill does not request elevated/persistent privileges or to modify other skills or system settings.
Assessment
This skill appears coherent and safe to install. Before sharing data with it: (1) avoid pasting secrets (API keys, private credentials) in code or traces; (2) Instruments traces or screenshots can include device names, paths, or other identifiers—redact if you need privacy; (3) when requesting help, provide minimal repro and the specific files/traces needed rather than entire projects; and (4) note that the skill is instruction-only (it will ask you what to run and what to upload) — review any follow-up requests from the agent before sending files. If you need higher assurance, ask the publisher for an explicit privacy/data-handling statement or host review before sharing sensitive artifacts.

Like a lobster shell, security has layers — review code before you run it.

latestvk977qrzgaqe1td45mp5rt2n59d83jzbq

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🚀 Clawdis

Comments