Manage Statamic content through a tool execution gateway (composer require stokoe/ai-gateway).
Security Analysis
high confidenceThe skill is internally consistent: it only needs a local sites.json (or env override) and curl/jq to call per-site AI gateway endpoints, which matches its stated purpose of managing Statamic sites via an execution gateway.
Name/description (Statamic AI Gateway) align with the declared requirements: curl/jq and a sites registry containing base_url and token. Requested artifacts (sites.json and AI_GATEWAY_SITES_CONFIG) are exactly what you would expect for a gateway that proxies requests to multiple Statamic sites.
SKILL.md explicitly instructs the agent to read the configured sites.json, look up base_url and token, call /capabilities then /capabilities/{tool} before executing, and follow confirmation gates. The instructions do not ask the agent to read unrelated files or credentials; the only secret accessed is the declared sites.json. The guidance is narrow and discovery-first, which limits accidental misuse.
This is instruction-only and has no install spec or downloads, so nothing is written to disk by the skill itself. Required binaries (curl, jq) are standard and reasonable for the documented curl-based workflow.
The skill asks for a single primary environment variable (AI_GATEWAY_SITES_CONFIG) and a local config path (~/.config/ai-gateway/sites.json) that stores site tokens. That is proportional to its purpose, but be aware this central registry stores bearer tokens that grant management access to each configured site; protecting that file and limiting what sites you add are important operational considerations.
always is false and the skill is user-invocable with normal autonomous invocation allowed. There is no attempt to modify other skills or persist beyond the documented sites.json; requested privileges are appropriate for operation.
Guidance
This skill appears to do what it says, but it centralizes per-site bearer tokens in a single local file. Before installing: (1) verify the GitHub homepage/author and that you trust the AI gateway addon running on each site; (2) store sites.json in a protected location and use chmod 600 as recommended; (3) add only sites you control or trust (a malicious site URL/token could be used to extract or modify content); (4) prefer short-lived or scoped tokens if the site supports them and rotate tokens if compromised; (5) keep the agent configured so that any confirmation-gated operations require interactive user approval (do not auto-confirm write operations). If you see any additional install scripts, code files, or requests for unrelated credentials (AWS keys, SSH keys, etc.), stop and re-evaluate — those would change this assessment.
Latest Release
v0.2.0
statamic-ai-gateway v0.2.0 - No changes were detected in this release. - All documentation, configuration, and implementation remain the same as in the previous version.
Popular Skills
Published by @michael-stokoe on ClawHub