Orderly Sdk Theming

v1.0.0

Customize the visual appearance of your Orderly DEX with CSS variables, colors, fonts, logos, and TradingView chart styling.

0· 226·0 current·0 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 name/description (Orderly SDK theming) match the SKILL.md content: CSS variables, Tailwind integration, fonts, logos, and TradingView styling. The skill does not request unrelated binaries, credentials, or system access.
Instruction Scope
Runtime instructions are limited to creating/overriding CSS variables, importing styles, configuring fonts and assets, and using the Orderly provider—all within the scope of theming. The document does reference importing '@orderly.network/ui' and external fonts (Google Fonts), which is expected for theming and not out-of-scope. There are no instructions to read unrelated files, environment variables, or to exfiltrate data.
Install Mechanism
No install spec or code files are provided (instruction-only). That minimizes install risk; the skill assumes you already have the Orderly SDK and Tailwind configured rather than downloading arbitrary artifacts.
Credentials
The skill declares no environment variables, credentials, or config paths, which is proportionate for a theming guide. It does reference external resources (Google Fonts and the Orderly package) which are reasonable for UI theming.
Persistence & Privilege
always:false and normal model invocation are used. The skill does not request permanent presence or system-wide config changes. Autonomous invocation is allowed by platform default but the skill's content does not give it additional privileges.
Assessment
This is essentially a how-to for theming the Orderly UI and appears internally consistent and low-risk. Before using it: (1) confirm you install the Orderly SDK and Tailwind from official sources (npm/GitHub) rather than copying arbitrary packages; (2) avoid placing secrets (API keys, private tokens) into visible config fields like brokerId in client-side code; (3) be aware fonts load from Google Fonts (privacy/network requests) and assets (logos) should be hosted from trusted locations; (4) review any TradingView integration details—those sometimes require separate vendor keys/licenses and you should not paste sensitive credentials into example files. If you need higher assurance, ask the skill author/source or compare the snippets against the official Orderly docs/repo.

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

latestvk979wzzwns9yt3h2bre5dadx9n82e6b9

License

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

Comments