Control Raspberry Pi GPIO pins remotely by setting specified pins HIGH or LOW through RPC calls.

This skill appears to do what it says (send RPC commands to a Raspberry Pi) but has several issues you should address before installing or using it: - Verify the target host: SKILL.md references http://pi.local:9000/run but the script hard-codes 192.168.0.14. Confirm which address is correct and avoid accidental control of the wrong device. - Authentication & encryption: The script sends commands over plain HTTP with no auth. Ensure the Pi's RPC server requires authentication (token/HTTPS) or run this only on a tightly controlled private network. - Input validation: The script forwards ACTION and PIN without checking allowed values. Prefer a whitelist (only gpio_on/gpio_off and valid pin ranges) to prevent unexpected commands. - Make the Pi address configurable: Replace the hard-coded PI_IP with a configurable env var or skill setting so the agent cannot accidentally reach other hosts. - Review the remote RPC server: Inspect the Pi-side implementation to confirm it actually limits actions to safe GPIO operations and does not execute arbitrary shell commands. If you cannot confirm the above, treat the skill as risky — especially on networks with multiple devices or where an unauthenticated RPC could be abused. If you want, I can suggest a revised script and a safer SKILL.md that add validation, configuration, and optional authentication.