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.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Failed to scan
The risk profile of this skill
Quality
Discovery
82%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 excels at specificity and distinctiveness, listing concrete actions across a well-defined domain (OpenSea/NFT/token ecosystem) with strong trigger terms. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. The mention of sub-skills and routing table is useful context but doesn't substitute for explicit trigger guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about NFTs, token swaps, OpenSea, Seaport, or building AI agent tools on Base.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: query NFT/token data, trade NFTs on Seaport, swap ERC20 tokens via DEX aggregator, configure wallet signing providers, build/register/gate AI agent tools on Base. Very detailed and actionable. | 3 / 3 |
Completeness | The 'what' is thoroughly covered with specific capabilities, but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. The description implies when through the actions listed but never states it explicitly, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: NFT, token, Seaport, ERC20, DEX, swap, wallet, OpenSea, CLI, MCP server, SDK, Base. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific references to OpenSea, Seaport, Base, DEX aggregator, and the full OpenSea developer surface. Very unlikely to conflict with other skills given the narrow and well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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-crafted router skill that excels at conciseness and progressive disclosure. It efficiently directs Claude to the right sub-skill with a clear routing table and quick decision guide. The only limitation is inherent to its router nature—it provides no executable guidance itself, relying entirely on sub-skills for operational detail, which slightly limits actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line serves a purpose—routing table, quick decision guide, and ecosystem pointer. No unnecessary explanation of what OpenSea is or how NFTs work. Assumes Claude's competence entirely. | 3 / 3 |
Actionability | The routing table provides clear direction on which sub-skill to use, but the skill itself contains no executable code, commands, or concrete operational guidance. This is by design as a router, but actionability is inherently limited—Claude must follow references to get actual instructions. | 2 / 3 |
Workflow Clarity | For a routing skill, the workflow is unambiguous: identify the task category, pick the sub-skill, read its SKILL.md before executing. The note about reading the wallet sub-skill before any write operation adds a useful sequencing hint. As a simple single-purpose skill, this is clear and complete. | 3 / 3 |
Progressive Disclosure | Textbook progressive disclosure. The router is a concise overview with well-signaled one-level-deep references to five sub-skills, each clearly labeled by task domain. The ecosystem pointer adds a clean secondary reference. No nested chains or monolithic content. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- ProjectOpenSea/opensea-skill
- Commit
10f23f8
- 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.