Structsd Install
v1.2.0Installs the structsd binary from source. Covers Go, Ignite CLI, and building structsd for Linux and macOS. Use when structsd is not found, when setting up a...
⭐ 0· 402·0 current·0 all-time
by@abstrct
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill name/description (install structsd) aligns with the instructions: installing Go, Ignite CLI, cloning the structsd repo, and building. Nothing in the SKILL.md asks for unrelated credentials or system access beyond what an installer would need. Minor metadata mismatch: _meta.json reports version 1.0.1 while registry metadata lists 1.2.0; this is an inconsistency in packaging but not necessarily malicious.
Instruction Scope
Instructions stay within install/upgrade scope (download Go, extract to /usr/local, add ~/go/bin to PATH, install Ignite, git clone, build). They modify user shell init files and write to /usr/local, which is expected for tool installation but requires sudo/privilege. No instructions attempt to read unrelated files or export other credentials.
Install Mechanism
There is no packaged install spec (instruction-only). Downloads: Go tarballs are from the official go.dev host (expected). The Ignite install uses a curl ... | bash pattern (curl https://get.ignite.com/cli! | bash), which executes a remote script without local review — this is a high-risk installation pattern even if the site is legitimate. Building from a GitHub repo (git clone then ignite chain build) is expected. Recommend inspecting the remote install script or using a vetted package manager/release instead of piping to bash.
Credentials
The skill declares no required env vars or credentials and the instructions don't read or transmit secrets. PATH modification is appropriate for making the built binary available.
Persistence & Privilege
always:false and the skill does not request persistent platform privileges. The only persistent changes are user-level PATH edits (~/.profile or ~/.zshrc) and writing Go to /usr/local, which are normal for an installer. The skill does not modify other skills or system-wide agent config.
Assessment
This skill appears to do what it says (install structsd), but before running the instructions: 1) Inspect the remote installer script at https://get.ignite.com/cli to ensure it is trustworthy — piping curl to bash runs arbitrary code on your machine. 2) Prefer package-manager installs or verified release artifacts where possible, and verify checksums for downloaded tarballs. 3) Be aware the process uses sudo to write to /usr/local and edits your shell init files to add ~/go/bin to PATH. 4) Verify the git repository (https://github.com/playstructs/structsd) is the expected upstream. If you are unsure, run the steps in an isolated environment (container or VM) or ask for a packaged installer that does not execute unreviewed remote scripts.Like a lobster shell, security has layers — review code before you run it.
latestvk97d4zbwnad12bws1ag81z1f0h83xdtb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.