CtrlK
BlogDocsLog inGet started
Tessl Logo

opensea-wallet

Set up and configure wallet signing providers for OpenSea transactions. Supports Privy, Turnkey, Fireblocks, Bankr, and local private keys. Required for executing trades (opensea-marketplace) and token swaps (opensea-swaps).

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, actionable body with copy-paste commands, an explicit verification feedback loop, and clean one-level-deep reference navigation; detail is appropriately deferred to reference files.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational specifics (provider env vars, auto-detect order, per-tx vs aggregate cap layers) and avoids explaining concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

The Quick start gives copy-paste-ready bash with real env exports and a concrete `opensea swaps execute` invocation, plus explicit `--wallet-provider` commands and an `opensea wallet info` command — fully executable guidance.

3 / 3

Workflow Clarity

A clear set-env-vars-then-sign sequence is paired with an explicit verification step (`opensea wallet info` prints loud warnings when the per-tx layer is missing) and scoped in/out tables; the feedback path points to wallet-setup.md for fixes.

3 / 3

Progressive Disclosure

The body is a well-organized overview with a References section that one-line-signals each real, one-level-deep file (wallet-setup.md, wallet-policies.md, wallet-funding.md), all confirmed present in references/.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific, well-scoped description that names concrete actions and distinguishes itself from sibling skills, but it lacks an explicit 'Use when...' trigger clause and leans on technical provider names over natural user keywords.

Suggestions

Add an explicit 'Use when...' clause with natural user triggers (e.g., 'Use when setting up a wallet to sign OpenSea trades or swaps, or when configuring signing policies').

Round out trigger terms with common user phrasings ('sign transactions', 'connect a wallet', 'approve a trade') rather than only provider brand names.

DimensionReasoningScore

Specificity

Concrete actions ('Set up and configure wallet signing providers') plus an enumerated, comprehensive provider list (Privy, Turnkey, Fireblocks, Bankr, local private keys) and named consumer skills match the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is clear, but the 'when' is only implied via the dependency note ('Required for executing trades ... and token swaps ...'); there is no 'Use when...' clause, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Relevant keywords are present (wallet, signing, OpenSea, trades, swaps, private keys) but framed as technical provider names rather than natural user phrasings, and common variations a user would say are not enumerated.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche (the wallet/signing layer) and explicitly distinguishes itself from the marketplace and swaps skills it enables, making wrong-skill triggering unlikely.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.