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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/crypto-hft/SKILL.md

Quality

Content

76%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.

Highly actionable command reference with clean section structure, held back by an implicit rather than explicit dry-run→live validation workflow. The 'Talk to Clodds Naturally' section is partly redundant with Quick Start.

Suggestions

Add an explicit go-live workflow with a validation checkpoint, e.g. '1. Run in --dry-run, 2. Review /crypto-hft status PnL, 3. Only when results are sound, set env vars and start without --dry-run.'

Trim or merge the 'Talk to Clodds Naturally' examples into Quick Start to remove redundancy.

Consider moving the full preset and exit-logic detail tables into a reference file linked from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense, mostly reference material with no padding explaining concepts Claude already knows, but the 'Talk to Clodds Naturally' section overlaps the Quick Start/Commands examples and could be trimmed.	4 / 5
Actionability	Copy-paste-ready slash commands, env-var exports, config flags, and preset names cover the common cases fully and executably.	5 / 5
Workflow Clarity	Quick Start lists commands and defaults to dry-run, but the move-to-live path lacks an explicit validate-then-proceed feedback loop; for a real-money (destructive) skill, missing validation checkpoints caps this at 3.	3 / 5
Progressive Disclosure	Well-organized into clear headed sections (Quick Start, Commands, Strategies, Presets, Exit Logic, Architecture) with no nested references; minor gap is that large preset/exit-detail tables that could live in separate files are inlined.	4 / 5
	Total	16 / 20 Passed

Description

70%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.

A specific, well-targeted description with strong trigger terms and clear distinctiveness, weakened only by the absence of an explicit 'when to use' clause. Adding a 'Use when...' sentence would lift completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to automate Polymarket crypto binary-market trading or mentions 5-min/15-min/1h/4h/daily crypto markets.'

Name the four strategies (momentum, mean_reversion, penny_clipper, expiry_fade) to move specificity toward comprehensive coverage.

Add common natural phrases such as 'crypto trading' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("crypto binary markets on Polymarket") plus several concrete specifics — "4 automated strategies" and explicit durations (5-min, 15-min, 1h, 4h, daily) and assets (BTC, ETH, SOL, XRP); the individual strategy names are not listed, leaving a minor coverage gap.	4 / 5
Completeness	The 'what' is clear (trade crypto binary markets with 4 strategies across durations/assets) but there is no explicit 'Use when...' trigger clause, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Strong natural keywords include "Polymarket", "crypto binary markets", "automated strategies", and the full set of duration/asset terms; a few common user phrases (e.g. "crypto trading") are absent, so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Trade crypto binary markets on Polymarket" carves a clear niche with distinct platform/duration triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/crypto-hft/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.