Orderly Sdk Debugging
v1.0.0Debug and troubleshoot common issues with the Orderly SDK including errors, WebSocket issues, authentication problems, and trading failures.
⭐ 0· 495·1 current·1 all-time
byMario Reder@tarnadas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md content: the document contains debugging guidance, code snippets, and troubleshooting steps for the Orderly SDK and related browser/build issues. No unrelated capabilities or external services are requested.
Instruction Scope
The instructions stay within SDK debugging scope: build fixes, WebSocket/account/order error handling, and example code. They do log account state in examples (address, userId, accountId, key presence) but do not instruct reading arbitrary system files, sending data to unexpected endpoints, or exfiltrating secrets.
Install Mechanism
No install spec or code files are present. The only actionable instruction is an example to install a common dev dependency (vite-plugin-node-polyfills) which is proportional to the described browser polyfill problem.
Credentials
The skill declares no required environment variables, credentials, or config paths. Example snippets access SDK state (account, key store) which is expected for debugging; there are no requests for unrelated credentials.
Persistence & Privilege
Skill is not always-enabled and does not request persistent privileges or modify other skills or system settings. It is user-invocable and can be used on demand.
Assessment
This is an instruction-only debugging guide for the Orderly SDK and is internally coherent. Before using: (1) don't paste or share private keys or seed phrases when following examples — use test accounts or testnets; (2) when running npm install commands, prefer verifying package sources and versions; (3) be aware example logs may print identifiers (address, userId, accountId); avoid sending those to untrusted endpoints. If you need the skill to run platform-side code, review any code you execute locally for sensitive operations first.Like a lobster shell, security has layers — review code before you run it.
latestvk975d4dx3f98s5t84xxp55qmf182erde
License
MIT-0
Free to use, modify, and redistribute. No attribution required.