Tessl • The management layer for AI agent skills

SkillPublic

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A strong, dense SDK overview: fully executable commands and code, a clearly sequenced lifecycle with validation and error-recovery checkpoints, and well-structured one-level-deep references. The only weakness is mild redundancy in the repeated CLI invocations across Examples C–F and the inlined discovery-API parameter tables.

Dimension	Reasoning	Score
Conciseness	Nearly all content is project-specific (contract addresses, CLI flags, x402/EIP-3009 protocol behavior) with little explanation of concepts Claude already knows, though Examples C–F repeat near-identical CLI blocks and the Tool Discovery parameter tables are reference-heavy — minor trim opportunities, not padding.	4 / 5
Actionability	Guidance is fully executable: copy-paste-ready 'npx @opensea/tool-sdk' commands, complete TypeScript for manifest/handler/adapters/registry client/usage reporting, curl examples, a full CLI command table with flags, and per-response-code remediation actions covering the common cases.	5 / 5
Workflow Clarity	Sections 1–8 are numbered to mirror the create → register → gate → call lifecycle with sub-steps (1a–1d, 2a–2b) and numbered end-to-end examples; validation exists via 'validate', '--dry-run', 'dry-run-gate', 'verify', and 'smoke', and the response-codes table provides explicit error-recovery feedback loops (re-sign on 401, retry with payment on 402, correct verb on 405).	5 / 5
Progressive Disclosure	SKILL.md is a workflow overview that correctly defers gating protocol details to one-level-deep references (x402.md, predicate-gating.md, known-predicates.md — all present in the bundle), each clearly signaled with a description in section 3 and again in the References section, making navigation easy.	5 / 5
	Total	19 / 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.

A highly specific, distinctive description with concrete actions and an explicit disambiguation handoff. Its main weakness is the absence of a positive 'Use when...' trigger clause, leaving the activation conditions only weakly implied and capping completeness.

Suggestions

Add an explicit trigger clause, e.g., 'Use when you need to build, register, or gate an AI-callable tool endpoint, or to call a paid/NFT-gated tool on the OpenSea registry.'

Include a few more natural user phrasings as triggers, such as 'publish an agent tool', 'make my API AI-callable', or 'charge USDC per API call'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Build, register, and gate AI-callable tool endpoints', 'Scaffold HTTPS tools with JSON Schema interfaces', 'register them onchain', and enumerated gating mechanisms ('NFT ownership, subscriptions, trait gating, or x402 pay-per-call (USDC)') plus 'call gated tools' — with comprehensive coverage and no real gaps.	5 / 5
Completeness	The 'what' is clear and specific, but there is no positive 'Use when...' clause — the closing sentence ('For querying OpenSea marketplace data use opensea-api instead') is negative boundary guidance, not explicit trigger guidance for this skill, so per the rubric's cap the 'when' remains only weakly implied by the verbs.	3 / 5
Trigger Term Quality	Good natural keyword coverage for the domain ('register', 'gate access', 'NFT', 'subscriptions', 'USDC', 'pay-per-call', 'Base'), but a few natural phrasings users would say are missing (e.g., 'publish a tool', 'agent tool', 'charge for API calls') and 'ERC-8257' is spec jargon rather than user vocabulary.	4 / 5
Distinctiveness Conflict Risk	A clear niche is staked out via 'OpenSea Tool Registry (ERC-8257) on Base' and the specific gating mechanisms, and the explicit handoff ('For querying OpenSea marketplace data use opensea-api instead') minimizes overlap with sibling OpenSea skills.	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 (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
Path: opensea-tool-sdk/SKILL.md
Revision: 42418c8

Reviewed: 24 days ago

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.

opensea-tool-sdk

Table of Contents

Is this your skill?