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)
65
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/crypto-hft/SKILL.mdQuality
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 is strong on specificity and distinctiveness, clearly identifying the platform (Polymarket), asset types, and timeframes. However, it critically lacks any 'Use when...' guidance, making it incomplete for skill selection purposes. The trigger term coverage is decent but could include more natural user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to trade on Polymarket, execute crypto binary options, or run automated trading strategies.'
Include common user-facing trigger terms like 'prediction markets', 'crypto trading bot', 'automated trading', or 'place bets on crypto prices' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: trading crypto binary markets on Polymarket with 4 automated strategies, and specifies 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 automated strategies) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'when' is not even implied clearly, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'crypto', 'binary markets', 'Polymarket', 'BTC', 'ETH', 'SOL', 'XRP', and 'automated strategies', but misses common user phrasings like 'prediction markets', 'betting', 'trading bot', or 'crypto trading'. Some terms are natural but coverage of variations is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Polymarket crypto binary markets with specific timeframes and assets. Unlikely to conflict with other skills given the highly specialized domain and platform name. | 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 well-structured and highly actionable skill with clear commands, specific presets, and good use of tables for comparison. Its main weaknesses are some redundancy between sections (natural language examples vs quick start, duration info repeated in multiple places) and the lack of explicit validation workflows for transitioning from dry-run to live trading with real money. The content would benefit from being split across files given its length.
Suggestions
Add an explicit workflow section for going live: 1) Run dry-run, 2) Verify stats look reasonable, 3) Set env vars, 4) Validate credentials with a test command, 5) Start with conservative preset first
Remove the 'Talk to Clodds Naturally' section or merge it into Quick Start - it largely duplicates information and the natural language mapping is something Claude can infer
Move detailed preset tables, exit logic details, and architecture diagram into separate referenced files (e.g., PRESETS.md, EXIT-LOGIC.md) to keep SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly well-organized but includes some redundancy - the 'Talk to Clodds Naturally' section largely duplicates the Quick Start section, the Market Duration Comparison table repeats information already conveyed in the presets section, and the 'Trading Strategy by Duration' bullet list at the bottom restates what's in the table. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready commands for every operation (start, stop, configure, preset management), specific environment variable names for live trading setup, and clear parameter examples with exact values. The strategy table, preset configurations, and exit logic are all specific and actionable. | 3 / 3 |
Workflow Clarity | The progression from dry-run to live trading is implied but not explicitly sequenced as a workflow with validation checkpoints. There's no explicit 'verify your setup works before going live' step, no validation of env vars, and no error recovery guidance. For a system involving real money trading, missing validation/verification steps is a notable gap. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's a monolithic document with a lot of detail inline (exit logic details, full architecture diagram, extensive preset tables) that could be split into referenced files. For a skill of this length (~180 lines), some content like the full preset tables and exit logic details would benefit from being in separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
e71a5f6
- Reviewed
Table of Contents
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.