Security audit
Security checks for vulnerabilities and agentic risk
This skill explains planned Printify features and submits waitlist details to Agiexa only after explicit user permission.
This is a preview and waitlist helper. Joining shares your email, role, and any optional link or message with Agiexa. Enter API keys only through the service's connection flow, and review permissions before enabling future commerce tools.
The waitlist endpoint is consistent with the declared purpose, but the supplied code performs the submission immediately. Setting "consent": true in the request does not establish user permission. The hardcoded example data limits the immediate impact, but the code still lacks the consent gate promised by the description.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
openclaw:
requires:
bins:
- curl
homepage: https://agiexa.com/integrations/printify
---
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Apps: Printify, Shopify
- Tools: `PRINTIFY_GET_PRODUCT`, `PRINTIFY_LIST_PRODUCTS`, `PRINTIFY_PUBLISH_PRODUCT`
> Review the Printify products I am considering publishing to my connected sales channel. Retrieve each product's complete details and verify its selected variants, print areas, images, visibility, and sales-channel properties where available. Identify missing design assets, unclear product information, and potential pricing issues using the costs and selling prices provided. Prepare a publication checklist with the exact product ID and the fields proposed for publication. Ask me to approve the product and selected fields before initiating publication. Because publication is asynchronous, report the actual operation result and do not claim the product is live without confirmation.
## Manage Product Updates Safely
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Apps: Printify
- Tools: `PRINTIFY_LIST_WEBHOOKS`, `PRINTIFY_CREATE_WEBHOOK`, `PRINTIFY_SIMULATE_WEBHOOK`, `PRINTIFY_UPDATE_WEBHOOK`, `PRINTIFY_DELETE_WEBHOOK`
> Review the webhook subscriptions configured for my Printify shops. List the available subscriptions and inspect their callback URLs and relevant configuration details where returned. Identify missing or potentially outdated subscriptions based on the events my fulfillment workflow needs to monitor. Prepare a proposed setup plan that explains which subscriptions should be created, updated, tested, or removed and why. Before changing subscriptions or sending simulated events to callback URLs, ask for explicit approval and confirm the exact shop, webhook, and destination involved. Do not claim an event was delivered or processed unless the operation result supports that conclusion, and do not delete existing subscriptions without approval.