BRICKS CLI

This skill appears to be what it claims (a BRICKS CLI) but contains several risky operational steps. Before installing or following the rules: - Verify the npm packages (@fugood/bricks-cli and acpx): check the publisher, star history, source repository, and inspect the package code if possible. No homepage is provided in the skill metadata — that increases risk. - Avoid using acpx --approve-all or any auto-approve flag. Auto-approve allows headless execution of arbitrary bash commands in your project directory. - Do not persistently write ~/.acpx/config.json on shared machines unless you understand and accept the risk; persistent config lets any process using acpx start sessions that access your project files. - Keep ACP disabled in BRICKS Project Desktop except when actively bridging; remove persistent config when done. Rotate passcodes/tokens used for device access. - Run installs and initial tests in an isolated environment (VM/container) or on a non-production machine before trusting them on your workstation or network. - Restrict LAN scans to trusted networks and confirm device workspace IDs to avoid interacting with devices from other workspaces. If you need stronger assurance, request the upstream package source or a link to the project's repo and review its code, or prefer a CLI distributed from a known, verifiable homepage or GitHub org.