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.

2.06x

Quality

80%

Does it follow best practices?

Impact

91%

2.06x

Average score across 2 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

86%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 router body is concise, well-structured, and cleanly delegates operational detail to one-level-deep sub-skills, matching the intended router design.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation; the router assumes Claude's competence and every line earns its place.	5 / 5
Actionability	Provides a concrete task-to-sub-skill routing table and quick decision guide, giving executable routing direction, though it intentionally contains no code or commands.	4 / 5
Workflow Clarity	Clear sequence (pick sub-skill, read its SKILL.md, then execute) with an explicit guardrail ('Always read the sub-skill SKILL.md before executing'); minor checkpoint gaps are acceptable for a router.	4 / 5
Progressive Disclosure	Clean overview with well-signaled one-level-deep sub-skill references and no nested indirection; content is appropriately split across sub-skills.	5 / 5
	Total	18 / 20 Passed

Description

75%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, action-rich, and well-scoped to a distinct niche, but lacks an explicit 'Use when...' trigger clause, capping completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user wants to query NFT data, trade or sweep NFTs, swap ERC20 tokens, or build AI agent tools on Base').

Include a few more natural synonyms users would say (e.g., 'buy NFTs', 'list NFTs', 'make offers') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (query NFT/token data, trade NFTs on Seaport, swap ERC20 via DEX aggregator, configure wallet signing, build/register/gate AI agent tools) with comprehensive coverage.	5 / 5
Completeness	Has a clear 'what' but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via the body's routing table, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural user terms like 'NFT', 'token', 'trade', 'swap', and 'wallet' are present, but common synonyms and a few natural phrasings users would say are missing.	4 / 5
Distinctiveness Conflict Risk	Clear OpenSea/NFT/Base niche with distinct triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	17 / 20 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: 6 missing	Warning

	Total	14 / 16 Passed

Repository: ProjectOpenSea/opensea-skill
Path: SKILL.md
Commit: 1e2e2e2

Reviewed: 5 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.