Token导航 LogoToken导航

Agent Skill · 效率

use-ts-sdk(USE TS SDK 前端)

use-ts-sdk 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

use-ts-sdk 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 12,331。

总安装 4,186周安装 178GitHub Stars 公开资料未说明下载 1,381核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:use-ts-sdk(USE TS SDK 前端)
来源仓库:https://github.com/iskysun96/use-ts-sdk
安装命令:
openclaw skills install use-ts-sdk
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install use-ts-sdk

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

use-ts-sdk 为 Aptos dApp 协调 TypeScript SDK 集成,路由到客户端、账户等子任务。适合在 OpenClaw 中需要快速接入 Aptos 区块链功能、处理交易或查看状态时使用。

通过 clawhub 安装,运行 openclaw skills install use-ts-sdk 即可使用。使用前请确认权限范围和维护状态,注意可能涉及 SDK 初始化和密钥管理。建议结合原始 README 核验具体用法,确保版本兼容性和网络端点正确配置。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install use-ts-sdk;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

use-ts-sdk 怎么安装?

在终端执行 openclaw skills install use-ts-sdk。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

use-ts-sdk 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

use-ts-sdk 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

use-ts-sdk 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

use-ts-sdk 用的人多吗?

公开数据是累计安装 4,186 次,近一周安装 178 次,下载 1,381 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

use-ts-sdk 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
use-ts-sdk

USE TS SDK 前端 · 本页

4,186—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
use-ts-sdk
description
license
MIT
metadata
author
aptos-labs
version
1.0
category
sdk
tags
["typescript", "sdk", "frontend", "orchestrator", "fullstack"]
priority
high

Use TypeScript SDK (Orchestrator)

Purpose

Orchestrates @aptos-labs/ts-sdk integration for Aptos dApps. For specific tasks, route to the appropriate granular skill. For composite tasks (e.g., "build me a fullstack dApp"), follow the workflow below.

Core Rules

  1. ALWAYS use @aptos-labs/ts-sdk (the current official SDK, NOT the deprecated aptos package)
  2. NEVER hardcode private keys in source code or frontend bundles
  3. NEVER expose private keys in client-side code or logs
  4. NEVER store private keys in environment variables accessible to the browser (use VITE_ prefix only for public

config)

  1. ALWAYS load private keys from environment variables in server-side scripts only, using process.env

Important: Boilerplate Template

If the project was scaffolded with npx create-aptos-dapp (boilerplate template), wallet adapter and SDK setup are already done. Before writing new code, check what already exists:

  • frontend/components/WalletProvider.tsx — wallet adapter setup with auto-connect
  • frontend/constants.ts — NETWORK, MODULE_ADDRESS, APTOS_API_KEY from env vars
  • frontend/entry-functions/ — existing entry function patterns (follow these for new ones)
  • frontend/view-functions/ — existing view function patterns (follow these for new ones)

Do NOT recreate wallet provider, client setup, or constants if they already exist. Instead, follow the existing patterns to add new entry/view functions for your Move contracts.

Skill Routing

Route to the appropriate granular skill based on the task:

TaskSkill
Set up Aptos client / configure networkts-sdk-client
Create accounts/signers (server-side)ts-sdk-account
Parse, format, or derive addressests-sdk-address
Build, sign, submit, simulate transactionsts-sdk-transactions
Read on-chain data (view, balances, resources)ts-sdk-view-and-query
Map Move types to TypeScript typests-sdk-types
Connect wallet in React frontendts-sdk-wallet-adapter

Fullstack dApp Workflow

When building a complete frontend integration:

  1. Set up client → read ts-sdk-client
  2. Create view function wrappers → read ts-sdk-view-and-query
  3. Create entry function payloads → read ts-sdk-transactions
  4. Wire up wallet connection → read ts-sdk-wallet-adapter
  5. Handle types correctly → read ts-sdk-types (as needed)

File Organization Pattern

src/
  lib/
    aptos.ts                    # Singleton Aptos client + MODULE_ADDRESS
  view-functions/
    getCount.ts                 # One file per view function
    getListing.ts
  entry-functions/
    increment.ts                # One file per entry function
    createListing.ts
  hooks/
    useCounter.ts               # React hooks wrapping view functions
    useListing.ts
  components/
    WalletProvider.tsx           # AptosWalletAdapterProvider wrapper
    IncrementButton.tsx          # Components calling entry functions

Error Handling Pattern

async function submitTransaction(
  aptos: Aptos,
  signer: Account,
  payload: InputGenerateTransactionPayloadData
): Promise<string> {
  try {
    const transaction = await aptos.transaction.build.simple({
      sender: signer.accountAddress,
      data: payload
    });

    const pendingTx = await aptos.signAndSubmitTransaction({
      signer,
      transaction
    });

    const committed = await aptos.waitForTransaction({
      transactionHash: pendingTx.hash
    });

    if (!committed.success) {
      throw new Error(`Transaction failed: ${committed.vm_status}`);
    }

    return pendingTx.hash;
  } catch (error) {
    if (error instanceof Error) {
      if (error.message.includes("RESOURCE_NOT_FOUND")) {
        throw new Error("Resource does not exist at the specified address");
      }
      if (error.message.includes("MODULE_NOT_FOUND")) {
        throw new Error("Contract is not deployed at the specified address");
      }
      if (error.message.includes("ABORTED")) {
        const match = error.message.match(/code: (\d+)/);
        const code = match ? match[1] : "unknown";
        throw new Error(`Contract error (code ${code})`);
      }
    }
    throw error;
  }
}

Edge Cases

ScenarioCheckAction
Resource not founderror.message.includes("RESOURCE_NOT_FOUND")Return default value or null
Module not deployederror.message.includes("MODULE_NOT_FOUND")Show "contract not deployed" message
Function not founderror.message.includes("FUNCTION_NOT_FOUND")Check function name and module address
Move aborterror.message.includes("ABORTED")Parse abort code, map to user-friendly error
Out of gaserror.message.includes("OUT_OF_GAS")Increase maxGasAmount and retry
Sequence number errorerror.message.includes("SEQUENCE_NUMBER")Retry after fetching fresh sequence number
Network timeouterror.message.includes("timeout")Retry with exponential backoff
Account does not existerror.message.includes("ACCOUNT_NOT_FOUND")Fund account or prompt user to create one
Insufficient balanceerror.message.includes("INSUFFICIENT_BALANCE")Show balance and required amount
User rejected in walletWallet-specific rejection errorShow "transaction cancelled" message

Anti-patterns

  1. NEVER use the deprecated aptos npm package — use @aptos-labs/ts-sdk
  2. NEVER skip waitForTransaction after submitting — transaction may not be committed yet
  3. NEVER hardcode module addresses — use environment variables (VITE_MODULE_ADDRESS)
  4. NEVER create multiple Aptos client instances — create one singleton and share it
  5. NEVER use Account.generate() in frontend code for real users — use wallet adapter
  6. NEVER use scriptComposer — removed in v6.0; use separate transactions instead
  7. NEVER use getAccountCoinAmount or getAccountAPTAmount — deprecated; use getBalance()

SDK Version Notes

AIP-80 Private Key Format (v2.0+)

Ed25519 and Secp256k1 private keys now use an AIP-80 prefixed format when serialized with toString():

const key = new Ed25519PrivateKey("0x...");
key.toString(); // Returns AIP-80 prefixed format, NOT raw hex

Fungible Asset Transfers (v1.39+)

await aptos.transferFungibleAssetBetweenStores({
  sender: account,
  fungibleAssetMetadataAddress: metadataAddr,
  senderStoreAddress: fromStore,
  recipientStoreAddress: toStore,
  amount: 1000n
});

Account Abstraction (v1.34+, AIP-104)

// Check if AA is enabled for an account
const isEnabled = await aptos.abstraction.isAccountAbstractionEnabled({
  accountAddress: "0x...",
  authenticationFunction: `${MODULE_ADDRESS}::auth::authenticate`
});

// Enable AA on an account
const enableTxn = await aptos.abstraction.enableAccountAbstractionTransaction({
  accountAddress: account.accountAddress,
  authenticationFunction: `${MODULE_ADDRESS}::auth::authenticate`
});

// Use AbstractedAccount for signing with custom auth logic
import { AbstractedAccount } from "@aptos-labs/ts-sdk";

References

Pattern Documentation:

Official Documentation:

  • TypeScript SDK: https://aptos.dev/build/sdks/ts-sdk
  • API Reference: https://aptos-labs.github.io/aptos-ts-sdk/
  • Wallet Adapter: https://aptos.dev/build/sdks/wallet-adapter/dapp
  • GitHub: https://github.com/aptos-labs/aptos-ts-sdk

Granular Skills:

Related Skills:

  • write-contracts — Write the Move contracts that this SDK interacts with
  • deploy-contracts — Deploy contracts before calling them from TypeScript

平台分布

OpenClaw

72.74%
按下载量换算1,005

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills