Orderly Sdk Dex Architecture

v1.0.0

Complete DEX architecture guide including project structure, provider hierarchy, network configuration, TradingView setup, and provider configuration.

0· 207·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill is an architectural guide for an Orderly Network DEX and the SKILL.md content focuses on project structure, provider hierarchy, network/runtime config, and TradingView integration — all consistent with the stated purpose.
Instruction Scope
The instructions reference runtime environment variables (e.g., VITE_ORDERLY_BROKER_ID), localStorage usage, and placement of TradingView library files in public/tradingview/. They do not instruct the agent to read or exfiltrate unrelated files or credentials. Be aware the guide assumes you will wire runtime config and wallet connectors into your app; it uses browser APIs (window, localStorage) which is expected for a frontend app.
Install Mechanism
No install spec or code files are present; this is instruction-only so nothing is downloaded or written by the skill itself at install time (lowest install risk).
Credentials
Skill metadata declares no required env vars, but the guide references VITE_ runtime variables and a brokerId/networkId that you must supply when implementing the app. This is proportionate for a DEX guide, but you should avoid placing secrets or private keys in client-side .env or public runtime config. Wallet connectors will interact with user wallets — do not hard-code private keys.
Persistence & Privilege
The skill is not marked always:true and requests no config paths or persistent privileges. Autonomous invocation is allowed (platform default) but this is an instruction-only guide and does not modify other skills or system settings.
Assessment
This skill is an architecture and scaffolding guide (no code or installers), and appears coherent with its purpose. Consider these before using: 1) The guide expects you to supply runtime vars like VITE_ORDERLY_BROKER_ID and to host TradingView files — avoid storing secrets or private keys in client-side .env or public runtime config. 2) Vet and pin any third-party packages (e.g., @orderly.network packages, TradingView) for license and supply-chain risk. 3) Do not commit .env or private keys to source control; use safe secret management for any server-side credentials. 4) If you implement wallet connectors, ensure users sign transactions client-side — never embed private keys. 5) Because the skill is instruction-only, installing it does not execute code, but you should still audit any code or packages you add to your project based on the guide.

Like a lobster shell, security has layers — review code before you run it.

latestvk97626a1ztb387va5qars6kqq182fgm1

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments