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.

2.20x

Quality

78%

Does it follow best practices?

Impact

55%

2.20x

Average score across 2 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./opensea-api/SKILL.md

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 explicit, validated workflows and clear reference navigation. Its weaknesses are minor redundancy between task-guide and dedicated CLI/script tables, and some inlined reference material that could be split out.

Suggestions

De-duplicate command tables: keep task-oriented tables in the Task guide and point the dedicated 'OpenSea CLI' and 'Shell Scripts Reference' sections to them, or vice versa, to trim tokens.

Move the dense MCP parameter tables (search_*, get_drop_details, deploy_seadrop_contract, etc.) into a references/mcp-tools.md file referenced one level deep.

Move the full shell-script index table into references/rest-api.md or a references/scripts.md, keeping only the most-used scripts inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but command/parameter tables are duplicated (task-guide tables repeat in the dedicated CLI and shell-script sections) and several inlined API parameter tables could live in references; not a 2 because content is accurate and largely earns its place, not a 4 because of the repetition.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands, shell scripts, SDK snippets, and curl examples cover the common cases throughout; not a 4 because guidance is fully executable with specific examples.	5 / 5
Workflow Clarity	The API-key resolution flow is explicitly numbered with validation checkpoints and edge-case recovery, plus a pre-bulk-operation checklist and error-handling feedback loops for destructive/batch ops (cross-chain mint, deploy); not a 4 because checkpoints and recovery loops are explicit and complete.	5 / 5
Progressive Disclosure	Clear overview with one-level-deep references to real files (references/authentication.md, rest-api.md, stream-api.md) and well-organized sections, but a fair amount of API reference content (MCP parameter tables, full shell-script index) is inlined rather than split out; not a 5 because some content that belongs in references is inline, not a 3 because structure and signaling are good.	4 / 5
	Total	17 / 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 and distinct, with comprehensive concrete capabilities and clear sibling-skill handoffs. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when querying floor prices, collection stats, NFT/token details, drops, events, or searching OpenSea').

Include common synonym phrasings users would actually say (e.g. 'browse NFTs', 'check NFT ownership', 'watchlist/favorites') to broaden trigger coverage.

Keep the sibling-skill handoff; consider moving it after a positive trigger clause so the 'when' is stated affirmatively first.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Get floor prices, collection stats, NFT details, token data, trending collections, drops, events, search, favorites, profile and collection settings") across CLI/SDK/MCP/scripts, giving comprehensive coverage; not a 4 because coverage is broad rather than 'minor gaps'.	5 / 5
Completeness	A clear 'what' is present but there is no explicit 'Use when...' trigger clause — only a negative scope-out handoff — so per the guideline a missing trigger clause caps completeness at 3; not a 4 because the 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Strong natural terms (floor prices, collection stats, drops, events, search, favorites, NFT details) with synonyms, but a few common user phrases (e.g. 'browse NFTs', 'check ownership', 'watchlist') are absent; not a 5 because coverage is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear OpenSea-niche with explicit handoff to sibling skills ("For trading use opensea-marketplace, for token swaps use opensea-swaps"), minimizing wrong-skill triggering; minimal conflict risk.	5 / 5
	Total	17 / 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 (831 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: 70c513e

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