opensea-api

Query OpenSea marketplace data via the official CLI, MCP server, or shell scripts. Get floor prices, collection stats, NFT details, token data, trending collections, drops, events, and search across Ethereum, Base, Arbitrum, Polygon, and more. Read-only operations; for trading use opensea-marketplace, for token swaps use opensea-swaps.

1.17x

Quality

—

Does it follow best practices?

Impact

55%

1.17x

Average score across 1 eval scenario

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.

A highly actionable, well-structured skill body with excellent workflow clarity for the critical API-key flow and batch operations. Its weaknesses are redundancy (operations listed across three overlapping sections) and inline-heavy reference material that could be pushed into bundle files.

Suggestions

Consolidate the overlapping operation listings: keep the task-guide table as the primary map and have the CLI command table and Shell Scripts Reference reference it rather than re-enumerating the same operations.

Move the full MCP tool parameter tables and/or the complete shell-script catalogue into a reference file (e.g., references/mcp-tools.md, references/scripts.md) and link to it, improving progressive disclosure.

Tighten the duplicated generic-CLI/auth/pagination guidance between the 'Quick start', 'OpenSea CLI', and 'Shell Scripts Reference' sections to reduce repeated tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the same operations (NFT/token/listing/offer/event/drop) are re-listed three times — task-guide tables, the CLI command table, and the full Shell Scripts Reference — adding redundant tokens that could be consolidated.	2 / 3
Actionability	Provides copy-paste-ready executable commands throughout (opensea CLI invocations, curl examples with headers, a TypeScript SDK snippet), with specific arguments and parameter tables rather than vague direction.	3 / 3
Workflow Clarity	The API key resolution flow is a clearly numbered sequence with explicit validation checkpoints (env → disk → fetch → save) and edge-case handling (401/403, 429), plus a pre-bulk-operation checklist with feedback loops for batch operations.	3 / 3
Progressive Disclosure	References are one level deep and verified to exist (references/rest-api.md, stream-api.md, authentication.md), but large reference material — full MCP parameter tables and the complete shell-script listing — is kept inline in SKILL.md rather than split into separate files.	2 / 3
	Total	10 / 12 Passed

Description

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.

A strong, specific description with good natural trigger terms and excellent distinctiveness via explicit sibling-skill handoffs. Its only gap is the absence of an explicit 'Use when...' clause, leaving the trigger guidance implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when querying read-only OpenSea marketplace data — floor prices, collection stats, NFT/token details, drops, events, or search') to lift completeness to 3.

Consider adding a couple of common user phrasings (e.g., 'NFT floor price', 'what's trending on OpenSea') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Get floor prices, collection stats, NFT details, token data, trending collections, drops, events, and search') and three delivery mechanisms (CLI, MCP server, shell scripts), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers 'what' but 'when' is only implied via the read-only scope statement; there is no explicit 'Use when...' trigger clause, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	Uses natural terms a user would actually say — 'floor prices', 'collection stats', 'NFT details', 'drops', 'events', 'search' — alongside chain names, giving good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	Has a clear read-only niche with explicit handoffs ('for trading use opensea-marketplace, for token swaps use opensea-swaps'), making it unlikely to trigger for the wrong sibling skill.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (706 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 5 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: ProjectOpenSea/opensea-skill
Commit: 142f269

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