Personal Guardian

This skill is an alpha prototype for an autonomous emergency responder. Before installing, consider the following: - Real capability gap: The skill claims phone calls, SMS, social posting, drone requests, and full-device sensor access but does not declare where telephony/SMS/social/drone API keys or platform bindings will come from. Ask the author (or inspect deployment integration) for the exact platform adapters and required credentials. - Permissions and law: Recording and automatic transmission of audio/location can have legal and privacy implications; confirm how user consent is obtained and logged in your jurisdiction. - Test in a sandbox: Run only in an isolated/test environment (disable real network/telephony) to verify behavior. The bundled code mostly simulates channels, but accidental configuration could enable real calls/posts. - Check default contacts/config: Edit or remove hard-coded example phone numbers and disable any auto-call/social/drone flags before use. Require explicit user authorization for auto-calling authorities (auto_call_120_authorized defaults appear in demo code). - Limit autonomy if needed: If your platform allows it, disable autonomous invocation or require explicit user confirmation for L4+/L5 actions until you fully audit integrations. - Additional data that would change assessment: If the author supplies clear integration adapters, documented required credentials, and explicit consent/permission flows (or restricts network calls to safe test endpoints), confidence would increase. Conversely, if runtime hooks to external endpoints or unlisted network calls are added, treat as higher risk.