Orderly One Dex
v1.0.0Create and manage a custom DEX using Orderly One API - deployment, custom domains, graduation, and theming
⭐ 0· 212·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
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (create/manage a white‑label DEX) align with the SKILL.md content: API endpoints, fields for branding/domains/deployment/graduation, and the documented workflow for forking/deploying a repo. The skill does not request unrelated credentials or tools.
Instruction Scope
SKILL.md is a detailed API usage guide (endpoints, required fields, file limits, auth-by-signature flow). It does not instruct the agent to read local files, environment variables, or secrets beyond normal wallet signature flows. Ensure any signature or transaction steps are performed via a wallet UI and not by pasting private keys.
Install Mechanism
No install spec or code files are present; this is instruction-only so nothing is written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths, which is proportional to a documentation/automation guide for a third‑party REST API. Fields in the API (e.g., privyAppId, walletConnectProjectId) are configuration values for the DEX itself, not platform secrets requested by the skill.
Persistence & Privilege
always:false and default invocation settings are appropriate. The skill does not request persistent system presence or make claims about modifying other skills or global agent settings.
Assessment
This is a documentation-only skill describing the Orderly One DEX API and expected workflows. Before using it: (1) verify you trust the Orderly One endpoints (https://dex-api.orderly.network and the testnet URL) and confirm this matches official Orderly docs; (2) never paste private keys into the agent — authentication should be performed by signing messages with your wallet (WalletConnect/Abstract/etc.); (3) be cautious when uploading branding assets or configuring custom domains and fee-splitting — these actions may trigger GitHub repo forks, deploys, or on‑chain transactions; (4) test everything on the testnet environment first; and (5) if you plan to graduate a DEX, review the graduation/fee split terms and who controls the resulting repo/deploy keys.Like a lobster shell, security has layers — review code before you run it.
latestvk974dwygak25mq8wb469k5qysd82dbxe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.