hustle

ZeroEx Hustle: Arbitrage Intelligence & Operations Engine. Manage vaults, payouts, and game automation monitoring.

Quality

45%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xnagato/hustle/SKILL.md

Quality

Discovery

32%

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 specific product/system (ZeroEx Hustle) and lists high-level capabilities, but lacks the explicit trigger guidance needed for Claude to reliably select this skill. The actions described are somewhat vague ('manage', 'monitoring') and there's no 'Use when...' clause to help Claude understand when to apply this skill versus others.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'ZeroEx', 'arbitrage bot', 'vault management', 'payout configuration', or 'game automation status'

Make actions more concrete - instead of 'manage vaults' specify operations like 'create vaults, deposit funds, withdraw profits, check vault balances'

Include natural language variations users might say, such as 'check my arbitrage profits', 'configure bot settings', or 'view payout history'

Dimension	Reasoning	Score
Specificity	Names the domain (ZeroEx Hustle, arbitrage) and lists some actions (manage vaults, payouts, game automation monitoring), but these are not fully concrete - 'manage' and 'monitoring' are somewhat vague without specifying what operations are actually performed.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'vaults', 'payouts', 'arbitrage', and 'game automation', but these are fairly technical. Missing common user variations and natural language triggers users might actually say when needing this skill.	2 / 3
Distinctiveness Conflict Risk	The 'ZeroEx Hustle' branding provides some distinctiveness, and 'arbitrage' narrows the domain. However, terms like 'vaults' and 'payouts' could overlap with other financial or crypto-related skills without clearer differentiation.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

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

This skill provides a reasonable overview of the Hustle operations system with clear structure and some concrete commands. However, it falls short on actionability by describing workflows abstractly rather than providing executable code, and lacks validation checkpoints for operations that could fail (vault access, wallet connectivity).

Suggestions

Add executable code examples for the Initialize Session workflow, showing how to actually load ACTIVE_IDENTITY and verify gunz_wallet connectivity

Include validation steps in workflows - e.g., 'Verify vault access: python3 vault.py --action test' with expected output

Provide concrete examples of available vault keys and their expected formats/values

Add error handling guidance - what to do if vault access fails or wallet is unreachable

Dimension	Reasoning	Score
Conciseness	Reasonably efficient but includes some unnecessary framing ('This skill provides access to...') and the capabilities list is somewhat redundant with the tools section. Could be tightened.	2 / 3
Actionability	Provides some concrete commands (bash examples) but they're incomplete - the vault.py script usage lacks context on what keys exist, and the workflows describe steps abstractly without executable code for loading identity or checking connectivity.	2 / 3
Workflow Clarity	Workflows are listed but lack validation checkpoints. 'Initialize Session' has no verification that steps succeeded. Captcha handling mentions pausing but no concrete error recovery or feedback loop for retry.	2 / 3
Progressive Disclosure	For a skill of this size (~50 lines), the structure is appropriate with clear sections for tools, workflows, and resources. No unnecessary nesting or monolithic content blocks.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 27 days ago

Table of Contents

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.