Pipe17 Openclaw Skill
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only Pipe17 API helper that uses a Pipe17 API key to read commerce data, with a credential metadata disclosure gap but no evidence of hidden code or destructive behavior.
Use this skill only if you are comfortable allowing the agent to query Pipe17 commerce data with your API key. Prefer a least-privilege/read-only key, avoid exposing the key in shared shells or logs, and verify that the key is scoped to the intended Pipe17 organization.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent can query order, shipping, fulfillment, and inventory information available to the provided Pipe17 API key.
The skill requires a Pipe17 API key and uses it to access Pipe17 resources. This is expected for the stated purpose, but the agent receives whatever Pipe17 account or organization access the key grants.
Create / obtain a Pipe17 API key... export PIPE17_API_KEY="..." ... All requests should include: `X-Pipe17-Key: ${PIPE17_API_KEY}`Use a least-privilege or read-only Pipe17 key if available, scope it to the intended organization or integration, and revoke or rotate it when no longer needed.
A user relying only on registry metadata could miss that using the skill requires giving the agent a Pipe17 API key.
Registry metadata does not advertise a credential requirement, while the SKILL.md setup requires PIPE17_API_KEY. This appears to be under-declaration rather than hidden misuse because the SKILL text itself states the key requirement.
Required env vars: none ... Env var declarations: none ... Primary credential: none
Review the SKILL.md setup instructions before use; the publisher should declare PIPE17_API_KEY as the primary credential in registry metadata.