opensea-api

Query OpenSea marketplace data via the official CLI, SDK, MCP server, or shell scripts. Get floor prices, collection stats, NFT details, token data, trending collections, drops, events, search, favorites, profile and collection settings, and other wallet-scoped operations. For trading use opensea-marketplace, for token swaps use opensea-swaps.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

81%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 with concrete commands and well-sequenced, validated workflows for key resolution, bulk operations, and minting. Its main weakness is conciseness: command references are duplicated across sections and detailed parameter tables are inlined rather than deferred to existing reference files.

Suggestions

De-duplicate command references: keep the Task guide as the canonical CLI-plus-alternative mapping and have the 'OpenSea CLI' and 'Shell Scripts Reference' sections point to it or to reference files instead of re-listing commands.

Move the detailed /api/v2/tools and MCP tool parameter tables into references/rest-api.md (or a dedicated reference), keeping only a few key examples inline in SKILL.md.

Trim the repeated install and auth snippets in the 'OpenSea CLI' section since they already appear in Quick start and API key resolution.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no basic-concept over-explanation, but command listings are duplicated across the Task guide, the dedicated CLI section, and the Shell Scripts Reference, and detailed endpoint parameter tables are inlined rather than deferred to reference files.	3 / 5
Actionability	Abundant copy-paste-ready CLI commands, curl examples with headers, SDK code, and shell-script invocations with concrete arguments cover the common cases.	5 / 5
Workflow Clarity	The API-key resolution flow is a numbered, ordered sequence with save-before-use validation, and the pre-bulk-operation checklist plus cross-chain mint receipt polling provide explicit validation steps and error feedback loops.	5 / 5
Progressive Disclosure	Three reference files (authentication.md, rest-api.md, stream-api.md) are clearly signaled and one level deep, but substantial reference-grade content (full script tables, MCP and tool parameter tables) remains inlined in SKILL.md.	4 / 5
	Total	17 / 20 Passed

Description

82%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, rich in natural trigger terms, and sharply distinguished from sibling skills via explicit handoffs. Its main gap is the absence of an explicit 'Use when...' trigger clause, which leaves activation conditions only weakly implied.

Suggestions

Add an explicit 'Use when...' clause naming concrete activation phrases (e.g., 'Use when querying OpenSea floor prices, collection stats, NFT or token data, drops, events, or marketplace listings/offers').

Lead with the trigger condition before the capability list so the 'when' is as prominent as the 'what'.

Replace the generic 'and other wallet-scoped operations' tail with one or two specific examples so the capability list ends on concrete terms.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (floor prices, collection stats, NFT details, token data, drops, events, search, favorites, profile and collection settings) across four interfaces (CLI, SDK, MCP, shell scripts), giving comprehensive coverage.	5 / 5
Completeness	Clearly states what the skill does, but provides no 'Use when...' trigger clause; the only usage guidance is a scope-out handoff to sibling skills, so 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Includes natural user-facing terms such as 'floor prices', 'NFT details', 'trending collections', 'drops', 'events', 'search', and 'favorites' that a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Explicitly carves a read/query niche and redirects trading to opensea-marketplace and swaps to opensea-swaps, yielding a clear niche with minimal conflict risk.	5 / 5
	Total	18 / 20 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 (791 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
Path: opensea-api/SKILL.md
Commit: 1e2e2e2

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