arbitrage

Automated cross-platform arbitrage detection and monitoring

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/arbitrage/SKILL.md

Quality

Content

57%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 dense, actionable API reference with strong code examples, but it behaves as a monolithic spec rather than an overview: no external references, no validation-gated workflow, and notable duplication between chat-command and TypeScript sections.

Suggestions

Move the bulk TypeScript API reference and chat-command catalog into separate reference files (e.g. API.md, COMMANDS.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit monitoring workflow with validation checkpoints (e.g. verify credentials -> start -> confirm isRunning -> check -> validate spreads against fees before alerting).

Trim duplication between the chat-command and TypeScript API sections and remove the educational 'Arbitrage Types Detected' examples unless they add non-obvious domain knowledge.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference-style content with little basic-concept padding, but it is a ~280-line monolithic API reference that duplicates the chat-command and TypeScript API surfaces and could be tightened or split.	3 / 5
Actionability	Concrete, copy-paste-ready TypeScript examples and chat commands cover the common cases, with only minor gaps such as undefined credential variables (apiKey, passphrase) and an assumed 'clodds/arbitrage' import.	4 / 5
Workflow Clarity	Per-feature code snippets give a rough sequence, but there is no end-to-end workflow with validation checkpoints; because arbitrage monitoring is a batch/automated operation lacking verification steps, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	The document is well-sectioned with headers, but the entire API reference is inlined in SKILL.md with no bundle files or external references, so content that should live in a separate reference file is inline.	3 / 5
	Total	13 / 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 is third-person and on-topic but minimal: it gives a clear 'what' with no 'when to use' guidance and only two action verbs. It is distinct as a niche yet thin on trigger terms.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when monitoring prediction-market arbitrage, comparing prices across Polymarket/Kalshi, or scanning for spread opportunities.'

Expand the action list beyond 'detection and monitoring' to cover scanning, comparing markets, linking matches, and alerting.

Include natural synonyms and platform names ('prediction markets', 'price spreads', 'Polymarket', 'Kalshi') so users' phrasings match the skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('cross-platform arbitrage') and two concrete actions ('detection and monitoring'), but offers no broader coverage of what the skill actually does, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It states a clear 'what' (automated arbitrage detection and monitoring) but provides no 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'arbitrage' and 'cross-platform' are relevant keywords a user might say, but common variations ('prediction markets', 'price spread', 'opportunities') and platform names are absent, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	'Cross-platform arbitrage' is a fairly distinct niche unlikely to fire for unrelated skills, though the phrasing is generic enough to allow minor overlap with general market/finance skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/arbitrage/SKILL.md
Commit: 715fd4a

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