ShipStation Orders

Monitor ShipStation orders, detect issues, and send alerts. For e-commerce businesses using ShipStation for order fulfillment across multiple platforms (Amaz...

This skill appears to do exactly what it says: poll ShipStation and flag order issues. Before installing: (1) Only provide ShipStation API key/secret — do not reuse high-privilege keys from other services. (2) Keep the .env file out of version control (SKILL.md advises adding it to .gitignore). (3) Expect local state files (state.json, shipping-state.json) to be created in the skill directory; they contain processed order IDs but not credentials. (4) Ensure your Node runtime is recent enough (Node 18+) because the scripts use global fetch. (5) If you plan to allow autonomous agent invocation, remember the agent may run these scripts on schedule; review scheduling/notification integration to avoid accidental disclosure. If any of the above is unacceptable, do not install or run the scripts until you make configuration changes (separate credentials, run in isolated environment, or review code).

Type: OpenClaw Skill Name: shipstation-orders Version: 1.1.0 The OpenClaw skill 'shipstation-orders' is designed to monitor ShipStation orders for new activity and issues. It legitimately requires ShipStation API credentials (key and secret) which are read from a local `.env` file or environment variables and used to communicate with the official ShipStation API (`https://ssapi.shipstation.com`). The skill manages its state using local `state.json` and `shipping-state.json` files. All instructions in `SKILL.md` and `README.md` are benign, guiding the AI agent to execute the scripts and process their output as intended for order monitoring and alerting. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the agent. The custom `loadEnv` function is a minor robustness flaw but not a security vulnerability.