CtrlK
BlogDocsLog inGet started
Tessl Logo

opensea-tool-sdk

Build, register, and gate AI-callable tool endpoints using the OpenSea Tool Registry (ERC-8257) on Base. Scaffold HTTPS tools with JSON Schema interfaces, register them onchain, gate access via NFT ownership, subscriptions, trait gating, or x402 pay-per-call (USDC), and call gated tools. For querying OpenSea marketplace data use opensea-api instead.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 and well-organized, with copy-paste-ready code and clearly sequenced workflows including validation checkpoints. Progressive disclosure is clean — the overview points to three real reference files one level deep — and verbosity is the only minor weakness.

Suggestions

Trim qualifying clauses in 'Important Constraints' (e.g. parenthetical RFC 6454 justification) and collapse verbose CLI table descriptions to flags-only to tighten token efficiency.

The 'Usage Tracking' section's prose (e.g. 'bounded by timeoutMs, default 5s, so it completes even on serverless runtimes that freeze on response flush') could be condensed to a single line noting failures are non-fatal and reported post-handler.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but sections like 'Important Constraints' and the long CLI command table include explanatory prose and qualifying clauses that could be trimmed. No teaching of concepts Claude already knows, which keeps it from scoring lower.

4 / 5

Actionability

Copy-paste-ready bash and TypeScript throughout — `init`, `register` with concrete flags, full `createToolHandler` and `ToolRegistryClient` examples, and end-to-end Examples A–F covering each gate type.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced with checkpoints: the CLI registration lists a numbered 6-step lifecycle, Examples A–F are step-numbered (scaffold → edit → deploy → register → call), and validation/verify commands (`validate`, `verify`, `inspect`, `--dry-run`) provide feedback loops for the onchain operations.

5 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references to the three real bundle files (x402.md, predicate-gating.md, known-predicates.md), each linked from the gating table and the References section; details are split out appropriately rather than inlined.

5 / 5

Total

19

/

20

Passed

Description

100%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, trigger-rich, and explicitly distinguishes this skill from the marketplace-query skill via a scope_out clause, giving it a clear niche with low conflict risk. It concisely answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scaffold HTTPS tools with JSON Schema interfaces', 'register them onchain', 'gate access via NFT ownership, subscriptions, trait gating, or x402 pay-per-call', 'call gated tools' — with comprehensive coverage of the skill's surface.

5 / 5

Completeness

Explicitly answers 'what' (build/register/gate/call tool endpoints) and 'when' via the sibling-skill distinction ('For querying OpenSea marketplace data use opensea-api instead'), giving clear trigger guidance for the right skill.

5 / 5

Trigger Term Quality

Covers natural terms users would say — 'tool endpoints', 'register onchain', 'NFT ownership', 'subscriptions', 'x402 pay-per-call', 'USDC', 'gated tools' — plus identifiers like ERC-8257 and the sibling-skill handoff phrase 'opensea-api'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (AI-callable tool endpoints on the ERC-8257 registry) with an explicit scope_out handoff naming opensea-api, minimizing conflict risk with adjacent OpenSea skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (563 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository
ProjectOpenSea/opensea-skill
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.