CtrlK
BlogDocsLog inGet started
Tessl Logo

metamask

Use the MetaMask tools to request and interact with wallet capabilities from the MetaMask capability vendor.

56

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/agentmask/openclaw-plugin-metamask/skills/metamask/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, well-structured, actionable guide that gives Claude exactly the tool inventory, workflow, and error-recovery rules needed to drive the MetaMask OCAP tools. Its only real weakness is the absence of explicit validation checkpoints in the workflow, which keeps workflow clarity at 4 rather than 5.

Suggestions

Add an explicit validation/checkpoint step in the workflow, e.g. after obtaining the vendor verify connection succeeded before requesting a capability.

De-duplicate guidance between Workflow and Rules (e.g. 'ask the user what they want') to trim a few redundant tokens.

Optionally list the most common capability/method pairs returned by request_capability so Claude has a concrete fallback before runtime discovery.

DimensionReasoningScore

Conciseness

The body is lean and task-focused with no padding about concepts Claude already knows; the only over-explanation is minor redundancy where the Rules section restates Workflow steps (e.g. asking the user what they want), keeping it just below a 5.

4 / 5

Actionability

Provides concrete tool names with their parameters and a worked example including literal args like '["0xAddress...", "Hello world", "0x1"]'; it is not a 5 because available method names are deferred to runtime rather than enumerated, leaving a small gap.

4 / 5

Workflow Clarity

A clear numbered sequence (obtain vendor -> request capability -> list -> call) is paired with feedback loops in Rules ('Not connected' -> obtain_vendor, call fails -> list_capabilities); it is not a 5 because there are no explicit validation checkpoints, only error-recovery guidance.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no need for external references, yet is well-organized into clearly labeled sections (Tools, Workflow, Example, Rules), which per the simple-skills note earns a 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 identifies a clear, distinct niche (MetaMask wallet capabilities) but relies on generic verbs and omits any explicit 'Use when...' trigger guidance, capping completeness and trigger quality at the midpoint. Adding concrete capability actions and natural-user trigger phrases would raise it substantially.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user wants to sign messages, read accounts, or interact with their MetaMask wallet via OCAP.'

Replace generic verbs ('request and interact with') with specific concrete actions like 'sign personal messages, list accounts, and invoke wallet methods'.

Include natural user-facing synonyms such as 'MetaMask wallet', 'sign messages', 'accounts', and 'crypto' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('MetaMask', 'wallet capabilities') and 1-2 actions ('request', 'interact with'), but the actions are generic rather than concrete operations like 'sign messages' or 'get accounts', so it sits at the anchor-3 level rather than 4.

3 / 5

Completeness

It clearly states what the skill does ('request and interact with wallet capabilities') but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural terms ('MetaMask', 'wallet') but is missing common variations and synonyms users would say (e.g. 'sign', 'accounts', 'crypto', 'blockchain'), matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The MetaMask-wallet niche is clearly distinct with minimal conflict risk against unrelated skills; it is not a 5 only because the weak trigger guidance leaves some overlap risk with closely related wallet/crypto skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Consensys-Incorporated/ocap-kernel
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.