arbitrage

Automated cross-platform arbitrage detection and monitoring

Quality

43%

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 ./src/skills/bundled/arbitrage/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too abstract and lacks the concrete details needed for effective skill selection. It names a domain (arbitrage) but fails to specify what actions the skill performs or when Claude should use it. The absence of explicit trigger guidance and specific capabilities makes it difficult to distinguish from other financial or monitoring skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about price differences across platforms, arbitrage opportunities, or wants to compare prices between marketplaces'

List specific concrete actions the skill performs, such as 'Scans multiple platforms for price discrepancies, calculates profit margins after fees, tracks historical arbitrage opportunities'

Include natural user terms like 'price comparison', 'profit opportunity', 'buy low sell high', or specific platform types (e.g., 'crypto exchanges', 'e-commerce sites')

Dimension	Reasoning	Score
Specificity	The description uses abstract language ('automated', 'detection', 'monitoring') without listing any concrete actions. It doesn't specify what the skill actually does - no verbs describing specific operations like 'scans prices', 'compares listings', or 'alerts on opportunities'.	1 / 3
Completeness	Only partially addresses 'what' at a high level and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and the what is too vague to be useful for skill selection.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords ('arbitrage', 'cross-platform', 'monitoring') that users interested in arbitrage might use, but misses common variations like 'price differences', 'buy low sell high', 'market opportunities', or specific platform names.	2 / 3
Distinctiveness Conflict Risk	'Arbitrage' is a fairly specific domain term that provides some distinctiveness, but 'monitoring' and 'detection' are generic enough to potentially overlap with other monitoring or financial analysis skills.	2 / 3
	Total	6 / 12 Passed

Implementation

64%

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

This skill provides comprehensive, actionable API documentation with excellent code examples that are copy-paste ready. However, it's overly verbose for a skill file—explaining arbitrage concepts Claude already knows and including extensive reference material that would be better in separate files. The lack of explicit workflows with validation steps for financial operations is a notable gap.

Suggestions

Remove the 'Arbitrage Types Detected' section—Claude understands these concepts; instead, just reference them in code comments if needed

Add an explicit workflow section showing the recommended sequence: configure → auto-match → verify matches → start monitoring → handle alerts, with validation checkpoints

Split into SKILL.md (quick start + overview) and separate API_REFERENCE.md and CONFIGURATION.md files for the detailed documentation

Add verification steps before acting on arbitrage opportunities (e.g., 'Always verify liquidity and fees before executing')

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary sections like explaining arbitrage types (cross-platform, internal, inverse) which Claude already understands conceptually. The best practices section is somewhat generic.	2 / 3
Actionability	Provides fully executable TypeScript code with complete examples for all operations. Chat commands are copy-paste ready with clear syntax. Configuration options are concrete with specific values and types.	3 / 3
Workflow Clarity	Commands and API methods are well-documented individually, but lacks explicit workflow sequences for common use cases. No validation checkpoints for verifying matches before acting on arbitrage opportunities, which is important for financial operations.	2 / 3
Progressive Disclosure	Content is organized into logical sections with clear headers, but everything is in one monolithic file. The API reference, arbitrage types explanation, and configuration could be split into separate reference files with the main skill providing a quick-start overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

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.