Apple Icloud Suite

This skill appears to implement real iCloud functionality, but there are several red flags you should consider before installing: - Credentials: The code and docs ask for your Apple ID main password (for Find My/photos) and an app-specific password (for CalDAV), plus a third-party AMAP API key. These are highly sensitive — the main password gives broad access and is not limited like an app-specific password. - Metadata mismatch: The registry metadata lists no required env vars, but the scripts clearly require and/or prompt for ICLOUD_USERNAME, ICLOUD_PASSWORD, ICLOUD_APP_PASSWORD, ICLOUD_CHINA and AMAP_API_KEY. That inconsistency is suspicious and makes auditing/trust harder. - Persistence & location privacy: The status_wall component is designed to run as a background daemon that polls device location frequently (every 15 minutes or 1 minute in commute mode) and writes local cache/config files. If you enable this, your device location will be continuously read and processed — only enable if you fully trust the code and understand where credentials/session files are stored (~/.pyicloud/, ~/.status_wall.*). - Provenance: Source/homepage are unknown and some internal metadata (ownerId and version in _meta.json) mismatch registry-level fields; consider this a trust risk. Prefer skills with clear authorship and published sources. Recommendations: - Do not provide your Apple main password to an unclear/unknown skill; prefer app-specific passwords where possible. - Review the script files yourself (or have a trusted developer do so) before running. The code is present in the package, which helps auditing. - If you only need calendar access, use an app-specific password and the CalDAV scripts; avoid enabling status_wall unless you understand and accept continuous location polling and have secured the machine where the daemon runs. - If unsure, run the scripts locally in an isolated environment (offline or on a disposable machine), or decline installation until the publisher/source can be verified.