bridge

Cross-chain token transfers using Wormhole and CCTP

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/bridge/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and reasonably concise, with executable commands and code covering the main transfer paths. Its weaknesses are the lack of validation checkpoints in the transfer workflow (capped at 3) and a monolithic single-file structure that inlines a large API reference rather than splitting it into reference files.

Suggestions

Add explicit validation checkpoints to the transfer flow, e.g. 'Check status === "redeemable" and verify destination address before calling redeem', with a fix-and-retry loop on failed attestations.

Move the bulk TypeScript API reference into a separate reference file (e.g. references/api.md) and keep SKILL.md as a concise overview with one-level-deep links.

Complete the code examples by including the missing imports (getWormholeQuote, waitForAttestation) so snippets are directly copy-paste executable.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earns its tokens with code, tables, and flow lists rather than explaining concepts Claude already knows; the only padding is illustrative console.log output lines in examples, which keeps it just above the midpoint but short of a fully lean 5.	4 / 5
Actionability	Concrete chat commands and copy-paste TypeScript examples cover the common cases, but a few symbols (getWormholeQuote, waitForAttestation) are used without being shown in the import statements, leaving minor gaps versus fully executable 5.	4 / 5
Workflow Clarity	Sequenced steps are listed for both Wormhole and CCTP flows, but these irreversible token-transfer operations have no explicit validation/verification checkpoints (e.g. confirm status before redeeming), and the rubric caps workflow clarity at 3 for destructive operations lacking validation.	3 / 5
Progressive Disclosure	The file is well sectioned, but at ~210 lines the full TypeScript API reference, command catalog, fees table, and flows are all inlined in SKILL.md with no bundle files split out, fitting the 'some structure but content that should be separate is inline' anchor rather than the simple-skill exception.	3 / 5
	Total	14 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 is clear about what the skill does and names specific protocols, giving it a recognizable niche. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and leaves natural user phrasings like 'bridge' uncovered.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when bridging tokens or USDC across chains, or when the user mentions Wormhole, CCTP, or cross-chain transfers.'

Include the natural term 'bridge' and the asset name 'USDC' so the description matches how users actually phrase these requests.

Optionally enumerate concrete actions (quote, send, redeem, check status) to raise specificity beyond a single 'transfers' verb.

Dimension	Reasoning	Score
Specificity	Names the domain ('Cross-chain token transfers') and two concrete protocols ('Wormhole and CCTP'), but the only action verb is 'transfers' with no broader set of concrete actions, matching the anchor that lists domain plus 1-2 actions.	3 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' or equivalent trigger guidance, and the rubric explicitly caps completeness at 3 when such a clause is missing.	3 / 5
Trigger Term Quality	Includes relevant terms ('cross-chain', 'token transfers', 'Wormhole', 'CCTP') but these skew technical; common natural phrasings a user would say like 'bridge', 'USDC', or 'send tokens across chains' are missing, so it sits at the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The narrow niche of cross-chain transfers via named protocols (Wormhole, CCTP) is fairly distinct with only minor overlap risk against a generic 'send' or 'swap' skill, fitting the 'mostly distinct' anchor rather than the fully clear-niche 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/bridge/SKILL.md
Commit: 715fd4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.