Trust Wallet open-source libraries — Wallet Core (HD wallets, address derivation, tx signing in Swift/Kotlin/TypeScript/Go for 140+ chains), Web3 Provider (dApp connection for Ethereum/Solana/Cosmos/Bitcoin/Aptos/TON/Tron), deep linking, browser extension integration, WalletConnect, token assets repository, and Barz ERC-4337 smart wallet. Use when working with trustwallet/wallet-core, @trustwallet/wallet-core, trust-web3-provider, Trust Wallet deep links, token logos/metadata from trustwallet/assets, or Barz account abstraction.
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/sdk/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly enumerates the specific Trust Wallet open-source libraries and their capabilities, includes natural trigger terms like package names and repository paths that developers would use, and provides a clear 'Use when' clause. The description is dense but well-organized, covering both the breadth of functionality and the precise contexts for activation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and components: HD wallets, address derivation, tx signing, dApp connection, deep linking, browser extension integration, WalletConnect, token assets repository, and Barz ERC-4337 smart wallet across specific languages and chains. | 3 / 3 |
Completeness | Clearly answers both 'what' (Trust Wallet libraries covering HD wallets, address derivation, tx signing, dApp connection, etc.) and 'when' with an explicit 'Use when...' clause listing specific package names, repositories, and use cases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'trustwallet/wallet-core', '@trustwallet/wallet-core', 'trust-web3-provider', 'Trust Wallet deep links', 'token logos/metadata', 'Barz account abstraction', plus specific chain names and language names that developers would naturally reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Trust Wallet's open-source ecosystem with named repositories (trustwallet/wallet-core, trust-web3-provider, trustwallet/assets, Barz). Unlikely to conflict with generic crypto or wallet skills due to the specific product and repo references. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely concise and well-structured routing document that efficiently directs Claude to the right reference file based on the user's task. However, it provides zero actionable content on its own — no code examples, no commands, no concrete guidance — making it entirely dependent on bundle files that were not provided for evaluation. Without at least a quick-start example or minimal executable snippet, the skill body alone cannot help Claude accomplish any task.
Suggestions
Add at least one concrete quick-start code example (e.g., deriving an address with wallet-core or constructing a deep link) so the skill body is actionable even before reading references.
Include a brief workflow section for common multi-reference tasks (e.g., 'To sign and broadcast a transaction: 1. Use wallet-core for signing, 2. Use web3-provider for broadcasting') to improve workflow clarity.
Add a minimal 'Installation / Setup' section with concrete package names and install commands (e.g., `npm install @trustwallet/wallet-core`) to provide immediate actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — no unnecessary explanations, no descriptions of what Trust Wallet is or how HD wallets work. Every line serves a routing purpose. The table format is efficient. | 3 / 3 |
Actionability | The skill contains zero executable code, commands, or concrete examples. It is purely a routing table to reference files. There is no actionable guidance in the body itself — it entirely delegates to external references. | 1 / 3 |
Workflow Clarity | The routing table provides a clear single-step workflow (identify task → read reference), but there's no guidance on what to do after reading the reference, no validation steps, and no multi-step process for tasks that span multiple references (e.g., signing a transaction AND connecting via WalletConnect). | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: a concise overview with a well-organized table pointing to clearly named, one-level-deep reference files. The 'When to read' column provides clear navigation signals for each reference. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f97ff0c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.