Orderly Sdk Page Components
v1.0.0Use pre-built page components from Orderly SDK to quickly assemble complete DEX pages (TradingPage, Portfolio, Markets, Leaderboard, etc.)
⭐ 0· 213·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
The name/description match the SKILL.md content: it documents using Orderly SDK page components and lists the specific @orderly.network packages required. One note: the skill metadata has no source/homepage listed (source: unknown), which reduces external traceability even though the instructions themselves are coherent.
Instruction Scope
SKILL.md contains usage examples, prop interfaces, and setup steps (React Router, providers, and downloading the TradingView charting library). It does not instruct the agent to read unrelated files, access secrets, or transmit data to unexpected endpoints.
Install Mechanism
There is no install spec and no code files — this is instruction-only, so nothing is written to disk by the skill itself.
Credentials
The skill does not request environment variables, credentials, or config paths. The documented dependencies (@orderly.network/* packages and external TradingView library) are proportional to the described purpose.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request elevated platform persistence or modify other skills' configs.
Assessment
This skill appears to be a documentation/integration guide rather than executable code — it is internally consistent with its stated purpose. However, before using it: 1) verify the @orderly.network packages you install are the official packages on the npm registry (or your organization’s approved registry) and check their publishers and versions; 2) download the TradingView charting library only from TradingView's official site and host it in your app as documented; 3) inspect your project’s package.json and any installed packages for unexpected dependencies or postinstall scripts; 4) because the skill metadata has no source/homepage, prefer installing packages from known sources or mirror them through your org’s vetted registries; and 5) run usual supply-chain checks (license, maintainers, recent activity) before deploying to production.Like a lobster shell, security has layers — review code before you run it.
latestvk970rkew71wd7k4hwt3kmgyb1182ecby
License
MIT-0
Free to use, modify, and redistribute. No attribution required.