agentsclimarketplace

Toronet sdk

Skill toronet-guidl/toronet-agent-skills/skills/toronet-sdk

A collection of installable AI agent skills for developers building on ToroNet

Install
npx -y skills add toronet-guidl/toronet-agent-skills --skill toronet-sdk

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

  • 2 stars2 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.

What its author says it does

Copied from the file, not written here

Use the ToroSDK TypeScript package for ToroNet workflows. Use when the user wants SDK-based wallet creation or import, password verification, blockchain queries, KYC or fiat flows, virtual wallet operations, bridge features, or SDK-based ToroNet deployment and transaction support.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, as published. Nobody here has run it

toronet-sdk

When to use

Use this skill when the user wants to:

  • initialize and configure ToroSDK
  • create or import ToroNet wallets with the SDK
  • verify wallet passwords or retrieve wallet keys
  • use ToroSDK for blockchain queries
  • use ToroSDK for KYC, fiat deposit, virtual wallet, token, payment, or bridge flows
  • create or verify credentials that will later be used with ToroNet API-based transaction flows
  • use SDK-based ToroNet deployment or network-aware SDK usage

Do not use this skill for plain RPC integrations with ethers.js or wagmi unless the user is explicitly comparing the SDK with those approaches.

Instructions

  1. Treat ToroSDK as the preferred path when the user explicitly wants SDK-based integration or when the task involves ToroNet-specific product flows beyond normal EVM reads.
  2. Identify the SDK workflow first: SDK initialization, wallet or credential flow, blockchain query, admin or project flow, bridge flow, or SDK-based deployment.
  3. Initialize the SDK correctly before describing other SDK operations, and be explicit about network selection: testnet and mainnet are both supported, and if the user does not configure the SDK it defaults to mainnet.
  4. When the user needs credentials for later ToroNet API-based calls, prefer SDK wallet flows such as wallet creation, wallet import, and password verification.
  5. When a workflow requires special credentials, call that out clearly: KYC requires the correct admin credentials, fiat deposit requires project registration and admin credentials, and many admin and payment flows require admin or whitelisted credentials.
  6. Keep normal user-facing examples separate from admin-sensitive examples, and keep backend-sensitive operations out of public frontend examples when secrets or passwords are involved.
  7. If the user asks about deployment through the SDK, explain that ToroSDK supports ToroForge deployment to testnet or mainnet, supports constructor arguments and custom owner addresses, uses the configured SDK network by default, allows per-call override, and requires token-based authorization for mainnet.
  8. Keep the answer focused on SDK usage rather than generic blockchain theory.

Default workflow

  1. Identify the exact SDK job the user wants to do.
  2. Initialize the SDK with the intended network.
  3. Choose the appropriate SDK function group.
  4. Check whether the workflow needs normal user credentials, admin credentials, or project credentials.
  5. Provide a practical example and add only the necessary warnings about secrets, credentials, and network choice.

Checks

  • SDK is installed and the network is set correctly
  • user understands that the default network is mainnet if not configured
  • secrets are not exposed in frontend code
  • admin-only and project-only flows are clearly labeled

See the reference guide for supported SDK capabilities, workflow guidance, and safety notes.

Relevant assets:

  • assets/initialize-sdk.ts
  • assets/wallet-and-credentials.examples.ts

Keep looking

Skills are one crate of 328,083. 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.