copy-trading

Automatically copy trades from successful wallets on Polymarket and crypto

Quality

46%

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/copy-trading/SKILL.md

Quality

Content

51%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 highly actionable with executable code and commands, but it is verbose and repetitive, inlines what should be a separate API reference, and lacks an explicit workflow with validation checkpoints for a destructive batch-trading skill.

Suggestions

Split the bulk TypeScript API reference and chat-command catalog into a separate references file (e.g. REFERENCE.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit end-to-end workflow with validation checkpoints (verify wallet/funds -> follow with small size -> confirm trade_copied events -> monitor stop-loss -> review daily P&L) since this skill places real trades.

Cut redundancy: sizing modes, stop-loss, take-profit, and daily limits are each shown in chat commands, createCopyTradingService defaults, and dedicated sections — keep one canonical example per concept.

Dimension	Reasoning	Score
Conciseness	The body inlines a large, repetitive API reference — Sizing Modes and Risk Controls are demonstrated three times (chat commands, API defaults, dedicated sections) — and re-explains routine concepts like 'Fixed: Always trade same dollar amount', which is padding Claude does not need.	2 / 5
Actionability	It provides copy-paste-ready TypeScript snippets and concrete chat commands covering the common cases (follow/unfollow, sizing modes, stop-loss/take-profit, top-trader discovery, analysis), with specific option names and values throughout.	5 / 5
Workflow Clarity	Sections are thematically ordered and a start/monitor/stop sequence is implied, but there is no explicit ordered workflow with validation checkpoints; for a destructive/batch trading skill the guidelines cap workflow_clarity at 3 when validation/verification steps are absent.	3 / 5
Progressive Disclosure	No bundle files exist, yet ~180 lines of detailed API reference and chat-command tables that clearly belong in a separate reference file are inlined directly in SKILL.md, with no one-level-deep references or navigation pointers to split the content.	2 / 5
	Total	12 / 20 Passed

Description

41%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 specific enough to be distinguishable but is missing any 'Use when...' trigger guidance and undersells the skill's concrete capabilities (sizing, delays, risk limits). Trigger-term coverage is adequate but lacks synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to mirror or copy trades from specific wallets on Polymarket or EVM/Solana chains.'

Enumerate concrete capabilities in the description — configurable sizing, trade delays, stop-loss/take-profit, and daily risk limits — so specificity reaches comprehensive coverage.

Include natural synonyms users actually say ('mirror trades', 'whale wallets', 'follow traders', 'wallet address') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The description names the domain ('copy trades from successful wallets on Polymarket and crypto') and one concrete action ('copy trades'), but does not enumerate the configurable sizing/delay/risk-control capabilities the skill actually offers, so coverage is not comprehensive.	3 / 5
Completeness	It states a clear 'what' but provides no 'when'/'Use when...' trigger guidance at all, which the guidelines explicitly cap at 3 and, with only a weak implicit when, this sits at the low end.	2 / 5
Trigger Term Quality	It surfaces 'copy trades', 'successful wallets', and 'Polymarket', but omits the natural variations a user would say ('mirror trades', 'whale wallets', 'follow traders', 'wallet address') and any file/extension-style tokens, leaving common synonyms missing.	3 / 5
Distinctiveness Conflict Risk	'Copy trades from successful wallets on Polymarket and crypto' carves a fairly specific niche with distinct triggers; the main overlap risk is the broad 'crypto' tail, which keeps it just short of a 5.	4 / 5
	Total	12 / 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/copy-trading/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.