CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-agent-wallet

Add budget limits, approval workflows, and a policy-gated wallet layer to your autonomous agents. Use when: Enforce daily and per-transaction spend limits on autonomous agents; Create a human-in-the-loop approval queue for high-value AI payments; Maintain an immutable audit log of every payment attempt and decision.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openclaw-agent-wallet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a marketing/README page rather than an actionable skill: it promotes capabilities without a single executable command, example policy file, or sequenced workflow, and the scripts and templates it references are not shipped in the bundle. Its main strengths are clear section structure and an honest limitations section.

Suggestions

Replace the FAQ and marketing sections with concrete, executable guidance: an example policy JSON (daily cap, approval threshold, allow/deny domains), the WALLET_SIGNER_URL configuration format, and the CLI/webhook commands for approving queued transactions.

Add a numbered setup-and-usage workflow (write policy -> configure signer -> run agent -> approve pending transactions) with validation checkpoints such as verifying the audit log records a policy hit before proceeding.

Ship the referenced policy engine, audit logger, and integration templates in scripts/ and references/ (or clearly link to them), so the body's claims are backed by actual bundle files.

DimensionReasoningScore

Conciseness

Several sections are padded or redundant: the 'When to use' section repeats the frontmatter description nearly verbatim, the six-question FAQ mostly restates the feature bullets (e.g., 'Does the skill provide a record of all agent financial activity?' duplicates the audit-log bullet), and marketing copy ('Prompting an AI to "be careful with money" is not a security strategy') plus promotional footer links add tokens without guidance. It is noticeably verbose, though it never explains basic concepts Claude already knows, keeping it above level 1.

2 / 5

Actionability

Concrete guidance is minimal: setup is described only as 'configuring your spend policies in a JSON file and defining your remote signer URL' with no example policy JSON, no CLI or webhook commands for the approval queue, no WALLET_SIGNER_URL format, and the Example section shows a request and result without any command that produces it. Scattered concrete anchors (WALLET_SIGNER_URL, vault/audit.jsonl) keep it above level 1.

2 / 5

Workflow Clarity

The configure-policy -> route-spend -> approve-transaction flow is never sequenced; a rough order is only implied in the FAQ ('configuring your spend policies in a JSON file and defining your remote signer URL'), and there are no validation checkpoints for an operation that gates real payments. Fragments of a sequence are recoverable, so it sits above the incoherent level-1 anchor.

2 / 5

Progressive Disclosure

The body is a single flat file with clear section headers and no nested references, but it exceeds 50 lines with FAQ and marketing content inlined that should be trimmed or split, and the bundle is empty: the body itself states 'Scripts, extension source, and templates from the original package are not in this folder', so the policy engine, audit logger, and integration templates it describes are missing entirely. Structure exists, but organization and the absent supporting files keep it at the middle anchor.

3 / 5

Total

9

/

20

Passed

Description

82%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 strong: it explicitly states what the skill does and when to use it with concrete, natural trigger phrases in a distinct niche. The main deductions are the second-person voice ('your autonomous agents'), which the rubric penalizes, and a few capability gaps relative to the body content.

Suggestions

Rewrite the opening in third-person voice (e.g., 'Adds budget limits, approval workflows, and a policy-gated wallet layer to autonomous agents') to avoid the second-person specificity penalty.

Include the remaining core capabilities (domain allow/deny lists, air-gapped signing via WALLET_SIGNER_URL) to close the coverage gap with the body's feature list.

Add common synonyms such as 'agent spending', 'spending caps', or 'transaction limits' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Enforce daily and per-transaction spend limits', 'Create a human-in-the-loop approval queue', 'Maintain an immutable audit log'), which fits the level-4 anchor with minor gaps (domain allow/deny lists and air-gapped signing are absent). However, it uses second-person voice ('Add budget limits ... to your autonomous agents'), which the guidelines penalize by reducing the specificity score by 1, yielding 3.

3 / 5

Completeness

It clearly answers 'what' ('Add budget limits, approval workflows, and a policy-gated wallet layer to your autonomous agents') and 'when' with an explicit 'Use when:' clause containing three concrete trigger scenarios, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say: 'spend limits', 'budget', 'approval', 'audit log', 'high-value AI payments', 'autonomous agents'. A few natural variations are missing (e.g., 'spending cap', 'transactions', 'crypto wallet'), so it falls just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (policy-gated wallet layer for autonomous agents) with distinct triggers like 'human-in-the-loop approval queue for high-value AI payments', making conflict with other skills minimal.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/openclaw-agent-wallet/SKILL.md

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.