iPhone
v1.0.0Run iPhone mission playbooks for battery, storage, privacy, connectivity, and daily automation with live operator-style guidance.
⭐ 0· 295·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name and description match the actual contents: step-by-step, operator-style playbooks for iPhone battery, storage, privacy, connectivity and routines. It does not request unrelated binaries, cloud credentials, or system-level access.
Instruction Scope
Runtime instructions are limited to guiding the user with exact UI paths and storing mission context under ~/iphone/. This is appropriate for a guided operator skill, but enabling memory will persist device/state details locally (model, iOS version, incident notes). Users should avoid saving sensitive secrets there and review the memory files before enabling if concerned.
Install Mechanism
There is no install spec and no code files—this is instruction-only. That minimizes disk writes and supply-chain risk.
Credentials
The skill declares no required environment variables, no credentials, and no config paths beyond its own ~/iphone/ memory directory. The requested local data (device model, iOS version, problem description) is proportionate to the troubleshooting purpose.
Persistence & Privilege
always is false and the skill does not request permanent elevated privileges or modify other skills. Its only persistence is optional local memory under ~/iphone/, which is reasonable for recalling playbooks and outcomes.
Assessment
This skill is instruction-only and appears coherent for live-guided iPhone troubleshooting. Before enabling memory or running missions: (1) Review the ~/iphone/ memory files and avoid storing passwords, 2FA codes, or full payment details there; (2) Be mindful that any device identifiers (model, iOS version, incident logs) will be saved locally—delete or redact if sensitive; (3) The skill may recommend actions that change settings—confirm destructive steps explicitly; (4) Because the source is 'unknown', prefer using the skill interactively rather than enabling any auto-activate behavior, and avoid installing related skills unless you trust their provenance.Like a lobster shell, security has layers — review code before you run it.
latestvk97e65qgjnq44mv6ettntb54x582105q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis
OSLinux · macOS · Windows
