trust-wallet-api
Trust Wallet API for crypto data — token search, prices, trending tokens, swap quotes, market data, security checks, address validation, asset info, and coin status across 100+ blockchains. Use whenever the user asks about crypto prices, token info, swap rates, market cap, trending coins, token risk, honeypot detection, address validation, or wants to call the Trust Wallet / tws.trustwallet.com API directly. Covers HMAC-SHA256 authentication, supported chains, and all REST endpoints.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 a strong, well-crafted skill description that excels across all dimensions. It lists numerous specific capabilities, includes a comprehensive 'Use when' clause with natural trigger terms users would actually say, and is clearly distinguishable from other skills through its Trust Wallet API focus. The description is information-dense without being padded, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: token search, prices, trending tokens, swap quotes, market data, security checks, address validation, asset info, coin status, HMAC-SHA256 authentication, supported chains, and REST endpoints. | 3 / 3 |
Completeness | Clearly answers both what (token search, prices, trending tokens, swap quotes, etc.) and when ('Use whenever the user asks about crypto prices, token info, swap rates, market cap, trending coins, token risk, honeypot detection, address validation, or wants to call the Trust Wallet API directly'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'crypto prices', 'token info', 'swap rates', 'market cap', 'trending coins', 'token risk', 'honeypot detection', 'address validation', 'Trust Wallet', and the specific API domain 'tws.trustwallet.com'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Trust Wallet API specifically, with domain-specific triggers like 'tws.trustwallet.com', 'HMAC-SHA256 authentication', 'honeypot detection', and '100+ blockchains' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured routing/overview skill that excels at conciseness and progressive disclosure. Its main weakness is that the body itself contains no actionable content — no example API calls, no code snippets, no concrete request/response patterns. It functions purely as a table of contents for the reference files, which means its value depends entirely on the quality of those referenced documents.
Suggestions
Add one minimal concrete example (e.g., a curl command or code snippet showing a basic authenticated API call) so the skill body itself is actionable without requiring a reference file read.
Include a brief workflow sequence for common tasks (e.g., '1. Authenticate per setup.md → 2. Resolve asset ID → 3. Call endpoint → 4. Check response status') to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — no unnecessary explanations of what REST APIs are, what HMAC-SHA256 is, or what crypto tokens are. Every line serves a routing or orientation purpose. The table is dense and functional. | 3 / 3 |
Actionability | The skill itself contains no executable code, commands, or concrete examples — it's purely a routing document. While it effectively directs to reference files, the body alone doesn't give Claude anything copy-paste ready or directly executable. The actionability depends entirely on the referenced files. | 2 / 3 |
Workflow Clarity | There's a clear directive to read setup.md first and a well-structured routing table, but no explicit multi-step workflow with validation checkpoints. For an API skill that involves authentication + request construction, a brief workflow (authenticate → identify chain/asset → call endpoint → validate response) would improve clarity. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure: a concise overview with a well-organized table pointing to five clearly-labeled, one-level-deep reference files. The 'When to read' column provides clear navigation signals for when each reference is relevant. | 3 / 3 |
Total | 10 / 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.
- Repository
- trustwallet/tw-agent-skills
- Commit
6f8671f
- Reviewed
Table of Contents
Is this your skill?
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.