Swiftui Expert Skill
v1.0.0Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS...
⭐ 0· 89·0 current·0 all-time
by@soponcd
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the actual runtime instructions: the skill is an expert guideline for writing, reviewing, and improving SwiftUI code. It requests no binaries, credentials, installs, or system access that would be unrelated to that purpose.
Instruction Scope
The SKILL.md instructs the agent to consult multiple local reference files (e.g., references/state-management.md, references/modern-apis.md, etc.) when reviewing or refactoring code, but the skill package manifest contains only SKILL.md and no 'references/' files. That mismatch is an incoherence (the instructions rely on resources that are not present). The instructions otherwise stay within the scope of code review/advice and do not direct the agent to read system files, environment variables, or transmit data to external endpoints.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requires no environment variables, credentials, or config paths. There are no disproportionate or unrelated secret requirements.
Persistence & Privilege
Flags are default (always: false, user-invocable, agent can invoke autonomously). The skill does not request persistent presence or special privileges.
Assessment
This skill appears to be a straightforward SwiftUI code-review/authoring guide and does not ask for credentials or install software. Two things to check before using: (1) the SKILL.md refers to several local 'references/*.md' documents that are not present in the published manifest — confirm the source repository or package contains those reference files if you expect the full guidance set; (2) when the agent asks you to provide project code for review, avoid pasting sensitive files (API keys, provisioning profiles, private certificates, or large proprietary code) — instead paste minimal reproductions or sanitized snippets. If you need higher assurance, review the upstream repo (homepage) to confirm authenticity and inspect the missing reference files and any additional code before enabling broader use.Like a lobster shell, security has layers — review code before you run it.
latestvk97e00cjdpkddqdt32b4rmz7h183j80a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis