CtrlK
BlogDocsLog inGet started
Tessl Logo

opensea-swaps

Swap ERC20 tokens across supported chains via OpenSea's cross-chain DEX aggregator. Get quotes with optimal routing, check token balances, and execute swaps. For NFT trading use opensea-marketplace, for querying token data use opensea-api.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./opensea-swaps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 body is highly actionable and well-structured with verified bundle references, but the destructive swap-execution workflow lacks an explicit validation checkpoint, capping workflow clarity.

Suggestions

Insert an explicit validation step before execute, e.g. 'Verify the quote output, slippage, and recipient address before running execute' as a numbered checkpoint in the workflow.

Move the full get_token_swap_quote parameter table into references/token-swaps.md and keep only the required-flag summary inline to lighten the overview.

Add a brief confirm/retry feedback loop (review calldata -> if wrong, re-quote with adjusted slippage) to satisfy the feedback-loop guidance for destructive operations.

DimensionReasoningScore

Conciseness

Lean tables and code blocks with no padding about concepts Claude already knows; a 4 not 5 because a few inline parameter details slightly duplicate the worked example.

4 / 5

Actionability

Copy-paste ready commands and JSON for quoting, executing, and balance-checking plus a parameter table cover the common cases end to end.

5 / 5

Workflow Clarity

A clear quote-then-execute sequence exists, but executing swaps is a destructive onchain operation with no sequenced validation checkpoint, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized sections with one-level-deep, real references (references/token-swaps.md and scripts/opensea-swap.sh both exist); a 4 not 5 because only one bundled reference is surfaced and the inline param table is moderately heavy.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, third-person, and well-differentiated from sibling skills, but it omits an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when swapping ERC20 tokens, getting swap quotes with routing, or checking token balances across chains').

Include a few natural synonyms such as 'trade tokens' or 'token swap' alongside 'swap' to broaden trigger coverage.

List the supported chains or note where to fetch them so the 'across supported chains' phrase is concrete rather than open-ended.

DimensionReasoningScore

Specificity

Names the domain and lists three concrete actions ('Get quotes with optimal routing, check token balances, and execute swaps'); not a 5 because it stops at three actions without broader coverage.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause, so per the rubric's missing-trigger cap completeness is held at 3.

3 / 5

Trigger Term Quality

Contains natural user phrases ('Swap ERC20 tokens', 'Get quotes', 'check token balances', 'execute swaps') plus boundary terms; a 4 not 5 because common synonyms and extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Explicit boundary guidance ('For NFT trading use opensea-marketplace, for querying token data use opensea-api') carves a clear ERC20-swap niche with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ProjectOpenSea/opensea-skill
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.