Watchos Code Review
v1.2.0Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with impo...
⭐ 0· 79·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided checklist and reference files. All referenced topics (lifecycle, complications, WatchConnectivity, performance) are present in the packaged reference docs and are appropriate for a watchOS code-review skill.
Instruction Scope
SKILL.md directs the agent to use the included reference files and to check code for watchOS-specific imports/patterns. There are no instructions to read unrelated system files, access secrets, call external endpoints, or perform actions outside reviewing code and local references.
Install Mechanism
No install spec and no code files beyond markdown references. Nothing is written to disk or downloaded at install time by the skill itself.
Credentials
The skill requires no environment variables, credentials, or config paths. The scope of requested access is proportional to a static, instruction-only review tool.
Persistence & Privilege
always is false and default model invocation is allowed (normal). The skill does not request persistent system presence or modify other skills' configs.
Assessment
This skill is an instruction-only checklist and local reference for watchOS code review and appears internally consistent. Before installing, consider these practical items: (1) the skill author/source is unknown and there's no homepage—if provenance matters to you, verify the content or prefer a known source; (2) the reference guidance should be checked against your target watchOS version and your app's architecture (the docs mention watchOS 9–11 patterns); (3) because it’s a review helper, it will operate on any code you provide to the agent—avoid sending production secrets or private keys into the review prompt. Other than provenance and standard data-handling caution, there are no technical red flags.Like a lobster shell, security has layers — review code before you run it.
latestvk9750trxf92kqs6wskgeg2g5ed83c5px
License
MIT-0
Free to use, modify, and redistribute. No attribution required.