hustle

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

Quality

35%

Does it follow best practices?

Impact

—

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

Content

37%

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

The skill provides a basic structural outline for hustle/arbitrage operations but lacks the concrete, executable guidance needed for Claude to act independently. Workflows are vague and missing validation checkpoints, which is especially problematic given the financial and credential-sensitive nature of the operations. The tool definitions are the strongest part but still incomplete.

Suggestions

Replace vague workflow steps like 'Check gunz_wallet connectivity' and 'Load ACTIVE_IDENTITY from vault' with exact commands or code snippets that Claude can execute.

Add explicit validation checkpoints to workflows, especially for the Initialize Session flow (e.g., verify vault access succeeded, confirm wallet connection with a specific command, handle failure cases).

Make the captcha handling workflow actionable with concrete code or commands rather than abstract descriptions like 'pause execution' and 'alert the user'.

Either create and reference bundle files for detailed procedures (e.g., VAULT_SETUP.md, PAYOUT_PIPELINE.md) or inline the necessary detail to make the skill self-contained.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary framing ('This skill provides access to the Hustle engine...') and the capabilities list is somewhat redundant with the later sections. Could be tightened.	2 / 3
Actionability	Provides some concrete commands (vault.py invocation, ps aux \| grep), but many steps are vague ('Check gunz_wallet connectivity', 'Load ACTIVE_IDENTITY from vault') without specifying exact commands or code. The captcha handling workflow is abstract with no executable guidance.	2 / 3
Workflow Clarity	The 'Initialize Session' workflow lists steps without concrete commands or validation checkpoints. The captcha handling workflow is vague ('pause execution', 'alert the user') with no feedback loops or error recovery. For operations involving credentials and financial transactions, the lack of validation steps is a significant gap.	1 / 3
Progressive Disclosure	Has reasonable section structure (Capabilities, Tools, Workflows, Resources), but no bundle files exist to reference. The content is neither monolithic nor well-layered — it's a mid-level overview that doesn't clearly point to deeper documentation or separate files for detailed procedures.	2 / 3
	Total	7 / 12 Passed

Description

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 domain (ZeroEx Hustle arbitrage operations) and lists a few high-level capabilities, but lacks concrete action details and entirely omits explicit trigger guidance ('Use when...'). The description would benefit significantly from specifying when Claude should select this skill and providing more granular action descriptions.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ZeroEx arbitrage vaults, payout management, game automation status, or monitoring arbitrage operations.'

List more specific concrete actions, e.g., 'Create and configure arbitrage vaults, process and schedule payouts, monitor game automation status and alerts, review arbitrage performance metrics.'

Include natural trigger terms users might say, such as 'arbitrage bot', 'vault balance', 'payout schedule', 'automation status', or 'ZeroEx monitoring'.

Dimension	Reasoning	Score
Specificity	Names the domain (arbitrage/game automation) and lists some actions ('manage vaults, payouts, and game automation monitoring'), but these are fairly high-level and not comprehensively detailed with concrete operations like 'create vault', 'trigger payout', or 'check arbitrage opportunities'.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'vaults', 'payouts', 'arbitrage', and 'game automation monitoring', but misses common user variations and natural phrasing. Terms like 'ZeroEx Hustle' are product-specific jargon that users might or might not use naturally.	2 / 3
Distinctiveness Conflict Risk	The combination of 'ZeroEx Hustle', 'arbitrage', and 'vaults' creates a somewhat distinctive niche, but 'payouts' and 'monitoring' are generic enough to potentially overlap with other financial or automation skills. The product name helps but the operational terms are broad.	2 / 3
	Total	7 / 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: f45fcb5

Reviewed: 29 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.