Global installation relies on unpinned remote npx tooling and repository content
Source references: 1The README tells the user to run npx and globally install a Skill named from a remote repository, without pinning the npm tool version, repository commit, or a content checksum. npx may download and execute the package it resolves.
If the resolved npm package or repository differs from the reviewed version or its supply chain is compromised, code could run with the user's permissions and persistently alter the global Skill directory, affecting later agent sessions. The evidence does not show that either source is currently compromised.
The README explicitly recommends a global npx installation. The command pins neither the npx package version nor a repository commit or checksum, so the resolved installer and repository contents can change over time and write into the global skill environment. This does not show that a supply-chain attack occurred, but it supports a plausible risk. Users can request pinned versions and commit hashes, verify contents, and review in an isolated or non-global environment first.
## Install```bashnpx skills add google-labs-code/stitch-skills --skill enhance-prompt --global```