agentsclimarketplace
Sign in

Dreamdex docs

Skill lrmn7/dreamdex-docs-agent-skill/skills/dreamdex-docs

Grounded DreamDex documentation for trading, fees, yield, orders, contracts, HTTP and WebSocket APIs, CCXT, wallets, portfolio, and security. Use when answering DreamDex questions or building, integrating, reviewing, or debugging DreamDex dApps and services.From its SKILL.md

Install
npx -y skills add lrmn7/dreamdex-docs-agent-skill --skill dreamdex-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

DreamDex Docs

Answer from the bundled DreamDex references only.

Workflow

  1. Route the question to one grouped summary:
    • references/welcome.md: product, deposit, roadmap.
    • references/trading.md: trading, fees, yield, orders, swaps, operators, stops.
    • references/contracts.md: architecture, functions, events, types, SpotRouter.
    • references/http-api.md: auth, endpoints, trading, vault, wallets, portfolio, CCXT.
    • references/websocket-api.md: connections, subscriptions, messages, errors.
    • references/security.md: risks and audits.
  2. Follow the summary link to one raw page under references/raw-pages/.
  3. Search for the target heading, endpoint, function, event, type, or error; read only that section.
  4. Cite claims as [local-file > section heading].
  5. If unsupported, say exactly: Not found in the local DreamDex references: <missing item>.

Use references/dreamdex-docs-index.md only when the correct topic is unclear. Do not load every summary, the whole index, or multiple raw pages by default.

Grounding rules

  • Never infer endpoints, methods, fields, scopes, auth formats, fees, chain IDs, addresses, order behavior, signatures, events, types, or error codes.
  • Verify exact technical details in a raw page; grouped summaries are routing aids, not specifications.
  • Distinguish documented facts from user assumptions and flag incomplete or conflicting documentation.
  • Treat live markets, addresses, pool parameters, fees, and audit status as time-sensitive when the docs say they are configurable or environment-specific.

Code examples

  • Label snippets Example based on local DreamDex docs.
  • Read the matching file in examples/ only when code is requested, then re-check its cited raw sections.
  • Use placeholders for user values and server-side environment variables for credentials.
  • Never place signing material or privileged credentials in frontend code.
  • Do not sign, broadcast, trade, approve, deposit, withdraw, or execute transactions. If explicitly requested, prepare reviewable code only.
  • Mention documented mainnet/testnet differences. If none are documented, say: No sandbox/testnet information found in the local DreamDex references.

Safety

  • Never request, expose, store, or transmit private keys, seed phrases, recovery phrases, or wallet secrets.
  • Include relevant contract, custody, market, oracle, liquidity, and upgrade warnings for production work.
  • Tell users to verify current official DreamDex documentation before production use.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.