Opencode Acp Control

Control OpenCode directly via the Agent Client Protocol (ACP). Start sessions, send prompts, resume conversations, and manage OpenCode updates.

Before installing or enabling this skill: - Understand what it actually does: it launches your local 'opencode' CLI and speaks JSON-RPC to it, granting the OpenCode process the ability to read and write files in whatever working directory you provide. - Verify you have a trusted 'opencode' binary: the skill does not declare required binaries or provide an install origin. Confirm the CLI is from the official project (check the GitHub repo linked in SKILL.md) and that you trust that binary. - Prefer using the skill only in safe/test directories (not your entire home or production projects), or restrict the cwd you give it. - Ask the author to update the manifest to declare required binaries (e.g., requires.binaries: ["opencode"]) and to provide provenance/installation instructions; also resolve the metadata inconsistencies (ownerId/version). - If you need stricter safety, decline the skill or run it in an isolated environment (container/VM) so the agent and the opencode process cannot access sensitive files. Given the manifest mismatches and the broad filesystem capability, treat this skill with caution until provenance and declared requirements are clarified.

Type: OpenClaw Skill Name: opencode-acp-control-3 Version: 0.1.1 The skill is classified as suspicious primarily due to the inclusion of a high-risk `curl -fsSL https://opencode.dev/install | bash` command within the `SKILL.md` documentation. While presented as a 'manual update suggestion' to the user, this command allows for arbitrary code execution from an external source (`opencode.dev`), posing a significant supply chain vulnerability. Additionally, the skill utilizes `process.list()` which grants broad visibility into running processes, a powerful capability that, while used for a stated purpose (killing OpenCode instances for update), could be misused.