opensea

Query NFT and token data, trade NFTs on Seaport, swap ERC20 tokens via DEX aggregator, configure wallet signing providers, and build/register/gate AI agent tools on Base. Covers the full OpenSea developer surface across CLI, MCP server, shell scripts, and SDK. Pick the right sub-skill using the routing table below, then read that sub-skill's SKILL.md for operational detail.

1.08x

Quality

—

Does it follow best practices?

Impact

98%

1.08x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The router body is concise and clearly sequenced, doing its job as an overview pointer. Its weaknesses are that the referenced sub-skill SKILL.md files are missing from the bundle, leaving routing unresolvable and the operational action deferred.

Suggestions

Include the referenced sub-skill SKILL.md files (opensea-api, opensea-marketplace, opensea-swaps, opensea-wallet, opensea-tool-sdk) in the bundle so the routing links resolve.

Add a one-line fallback for when a referenced sub-skill is unavailable (e.g., a direct API endpoint or minimal command) so actionability does not fully depend on missing files.

Collapse the 'Quick decision guide' into the routing table or trim overlap to further tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~22-line router with a routing table and a brief decision guide, assuming Claude's competence and explaining no background concepts, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Concrete routing direction is given ('read its SKILL.md', task→sub-skill table) but there is no executable code/command and the referenced sub-skill files do not exist in the bundle, leaving the operational action deferred and unresolvable — matching 'some concrete guidance but incomplete; missing key details'.	2 / 3
Workflow Clarity	The single routing sequence is explicit and unambiguous ('Pick the sub-skill based on task, then read its SKILL.md') with an explicit checkpoint ('Always read the sub-skill SKILL.md before executing'); for this simple single-purpose router this warrants 3 per the simple-skills scoring note.	3 / 3
Progressive Disclosure	The overview is well-signaled with one-level-deep sub-skill links in a table, but per the guideline to score against the actual bundle structure, the referenced files (opensea-api/SKILL.md, opensea-marketplace/SKILL.md, etc.) are absent, breaking the navigation promise — matching 'references present but not clearly signaled' in effect.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 and well-niched, clearly conveying the OpenSea developer surface and routing model. Its main weaknesses are the absence of an explicit 'Use when...' trigger clause and a reliance on product jargon over natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to query, buy, sell, or swap NFTs/tokens on OpenSea or Base') to lift completeness and trigger clarity.

Soften product jargon with natural user terms (e.g., add 'buy/sell NFTs' alongside 'trade NFTs on Seaport') to improve trigger-term quality.

Trim the second sentence ('Covers the full OpenSea developer surface across CLI, MCP server, shell scripts, and SDK') which adds little actionable signal for a description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action clusters ("Query NFT and token data, trade NFTs on Seaport, swap ERC20 tokens via DEX aggregator, configure wallet signing providers, and build/register/gate AI agent tools"), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause — the when is only implied via 'Pick the right sub-skill using the routing table', which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords exist (NFT, token, trade, swap, ERC20, wallet) but the phrasing leans on product/technical terms (Seaport, DEX aggregator, Base, MCP server) and omits common plain-language variants a user would say like 'buy/sell NFTs', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Tightly scoped to the OpenSea/Base developer surface with distinct sub-skill triggers, making it unlikely to fire for unrelated skills; matches the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: ProjectOpenSea/opensea-skill
Commit: 142f269

Reviewed: 1 day 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.