Cross-chain token transfers using Wormhole and CCTP
70
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/bridge/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a specific technical domain (cross-chain transfers via Wormhole/CCTP) which provides good distinctiveness, but lacks concrete action verbs and completely omits trigger guidance. It reads more like a topic label than a functional skill description that would help Claude choose it appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'bridge tokens', 'transfer between chains', 'Wormhole bridge', 'Circle CCTP', or specific chain names (Ethereum, Solana, etc.)
List specific concrete actions such as 'initiate bridge transfers', 'verify cross-chain messages', 'estimate bridging fees', 'track transfer status'
Include common user phrasings like 'move tokens to another chain', 'bridging', 'cross-chain swap' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cross-chain token transfers) and specific technologies (Wormhole, CCTP), but doesn't list concrete actions like 'bridge tokens', 'verify transfers', or 'estimate fees'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level; completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms 'Wormhole', 'CCTP', 'cross-chain', and 'token transfers', but misses common user variations like 'bridge', 'bridging', 'move tokens between chains', or specific chain names. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of Wormhole and CCTP protocols creates a clear niche that is unlikely to conflict with other skills; these are distinct blockchain bridging technologies. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
79%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 API reference with excellent actionability through complete code examples and clear command syntax. The main weaknesses are the lack of explicit validation checkpoints for financial operations (critical for cross-chain transfers) and the monolithic structure that could benefit from progressive disclosure to separate files.
Suggestions
Add explicit validation steps in the TypeScript examples, such as checking balances before transfer and verifying transaction success before proceeding to redemption
Include error handling examples showing what to do when transfers fail or get stuck in 'attesting' state
Split into separate files: SKILL.md (overview + quick start), API.md (full TypeScript reference), COMMANDS.md (chat commands), with clear navigation links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting information in tables and code blocks without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples with complete import statements, function calls, and realistic parameters. Chat commands are copy-paste ready with clear syntax patterns. | 3 / 3 |
Workflow Clarity | The Transfer Flow section outlines steps but lacks explicit validation checkpoints. For cross-chain transfers involving real funds, there should be explicit verification steps (e.g., 'Verify balance before proceeding', 'Confirm VAA is valid before redeeming') and error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file (~180 lines) that could benefit from splitting API reference, examples, and best practices into separate files. No references to external documentation for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2a8c94e
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.