Structs Guild Stack

Deploys the Guild Stack (Docker Compose) for local PostgreSQL access to game state. Use when you need faster queries for combat automation, real-time threat...

This skill is coherent for deploying a local guild node via Docker Compose, but the actual code and containers come from an external GitHub repository. Before running: 1) Inspect the repository (docker-compose.yml, Dockerfiles, and referenced image tags). 2) Verify image sources and prefer pinned, signed, or official images; avoid running images from unknown registries without review. 3) Check for host volume mounts and exposed ports (to avoid sensitive host access). 4) Review .env and do not place private keys or unrelated secrets there unless you understand how they are used. 5) Run the stack in an isolated environment (VM or dedicated host) until you trust the repo. Also note minor packaging inconsistencies (the included _meta.json version differs from the registry version and part of an example SQL in the SKILL.md is truncated), which suggests the bundle was packaged sloppily — another reason to manually review the upstream repo before executing.

Type: OpenClaw Skill Name: structs-guild-stack Version: 1.2.0 The skill instructs the agent to clone a remote repository (https://github.com/playstructs/docker-structs-guild) and execute a Docker Compose stack, which involves high-risk operations like 'docker compose up' and 'docker exec' in SKILL.md. While these actions are aligned with the stated purpose of deploying a 'Guild Stack' for the Structs game, they represent a significant supply chain risk and potential for remote code execution if the external repository or its Docker images are compromised. No explicit evidence of malicious intent, such as credential theft or unauthorized exfiltration, was found in the provided files.