crypto-hft

Trade crypto binary markets on Polymarket with 4 automated strategies. Support: 5-min BTC, 15-min/1h/4h/daily all assets (BTC, ETH, SOL, XRP)

Quality

57%

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/crypto-hft/SKILL.md

Quality

Discovery

50%

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 excels at specificity with concrete timeframes, assets, and platform details, making it highly distinctive. However, it critically lacks any 'Use when...' guidance, which severely impacts completeness and makes it harder for Claude to know when to select this skill. The trigger terms could also be expanded to include more natural user language.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to trade on Polymarket, automate crypto predictions, or set up binary market strategies'

Include additional natural trigger terms users might say: 'prediction markets', 'automated trading', 'trading bot', 'crypto predictions'

Consider adding context about what 'binary markets' means for users unfamiliar with the term

Dimension	Reasoning	Score
Specificity	Lists concrete actions: 'Trade crypto binary markets', '4 automated strategies', and specifies exact timeframes (5-min, 15-min, 1h, 4h, daily) and supported assets (BTC, ETH, SOL, XRP).	3 / 3
Completeness	Describes what it does (trade crypto binary markets with strategies) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'crypto', 'Polymarket', 'BTC', 'ETH', 'SOL', 'XRP', and 'binary markets', but missing common variations users might say like 'prediction markets', 'trading bot', 'automated trading', or 'crypto trading'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche: Polymarket crypto binary trading with specific timeframes and assets. Unlikely to conflict with other skills due to the unique combination of platform (Polymarket) and specific trading parameters.	3 / 3
	Total	9 / 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 is a functional skill with excellent actionability - commands are concrete and copy-paste ready. However, it's somewhat verbose with redundant preset information across sections, and lacks explicit validation workflows for a system involving financial risk. The monolithic structure could benefit from splitting detailed reference material into separate files.

Suggestions

Add explicit validation checkpoints: 'After starting, run /crypto-hft status to verify connection and dry-run mode before proceeding to live trading'

Consolidate the preset tables into a single comprehensive table or move detailed preset documentation to a separate PRESETS.md file

Add a verification workflow for transitioning from dry-run to live trading with explicit safety checks

Remove the 'Talk to Clodds Naturally' section as it duplicates Quick Start and assumes Claude needs examples of natural language interpretation

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the preset tables repeat similar information across multiple sections, and the 'Talk to Clodds Naturally' section duplicates what's shown in Quick Start. The market duration comparison table is useful but could be more compact.	2 / 3
Actionability	Excellent actionability with copy-paste ready commands throughout, specific environment variable names, concrete preset names, and clear command syntax. Every section provides executable guidance rather than abstract descriptions.	3 / 3
Workflow Clarity	The skill provides clear commands but lacks explicit validation checkpoints. For a trading system with real money at stake, there's no verification workflow (e.g., 'check status after start', 'verify dry-run results before going live'). The exit logic is well-documented but the setup/verification flow is implicit.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is in one file. The detailed preset tables, strategy explanations, and architecture diagram could be split into reference files. No external file references are provided for deeper documentation.	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.