copy-trading

Automatically copy trades from successful wallets on Polymarket and crypto

Quality

27%

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

Quality

Discovery

40%

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 identifies a clear and distinctive niche—automated copy trading on Polymarket and crypto—but is too terse to be effective for skill selection. It lacks a 'Use when...' clause, provides only a single high-level action, and misses common trigger term variations that users might employ.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to mirror trades, follow successful wallets, or set up automated copy trading on Polymarket or crypto platforms.'

Expand the capability list with specific actions such as 'monitor wallet activity, execute mirror trades, manage position sizing, and track P&L from copied positions.'

Include additional natural trigger terms like 'mirror trading', 'follow traders', 'prediction markets', 'automated trading', and 'wallet tracking'.

Dimension	Reasoning	Score
Specificity	Names the domain (trade copying on Polymarket/crypto) and one action (copy trades), but lacks detail on specific capabilities like monitoring, order execution, portfolio management, or risk controls.	2 / 3
Completeness	Describes what it does (copy trades from successful wallets) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'copy trades', 'wallets', 'Polymarket', and 'crypto' which users might naturally say, but misses variations like 'mirror trading', 'follow traders', 'prediction markets', 'on-chain', or 'automated trading'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'copy trades', 'Polymarket', and 'successful wallets' creates a very specific niche that is unlikely to conflict with other skills. This is a clearly distinct use case.	3 / 3
	Total	8 / 12 Passed

Implementation

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a comprehensive API reference document rather than an actionable skill for Claude. It is excessively long, repeats configuration patterns across multiple sections, and lacks any real workflow with validation steps—critical for a financial trading operation. The referenced library appears fictional, undermining the actionability of otherwise concrete-looking code examples.

Suggestions

Restructure as a concise overview (under 50 lines) with quick-start workflow, moving the full API reference and event handling details to separate referenced files like API_REFERENCE.md and RISK_MANAGEMENT.md.

Add a clear sequential workflow with validation checkpoints: verify credentials → test with paper trading → follow one wallet with small size → verify trade execution → scale up.

Remove duplicate configuration examples (stop-loss/take-profit appears in 3+ places) and consolidate into a single reference section.

Clarify whether 'clodds/trading/copy-trading' is a real package or needs to be built, and add installation/setup prerequisites.

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose at ~200+ lines, with extensive API reference material that could be in a separate file. It repeats concepts across sections (e.g., stop-loss/take-profit configuration appears in multiple places), and includes many code examples that are essentially variations of the same patterns. Much of this is reference documentation, not skill instruction.	1 / 3
Actionability	The code examples appear syntactically complete and use concrete values, but they reference a fictional library ('clodds/trading/copy-trading') with no indication of whether it exists or how to install it. The chat commands also appear to be for a hypothetical system. Without grounding in real tools, the actionability is limited despite the concrete-looking syntax.	2 / 3
Workflow Clarity	There is no clear sequential workflow for setting up and running copy trading. The content is organized as an API reference rather than a step-by-step process. For an operation involving real money and destructive financial actions, there are no validation checkpoints, no error recovery steps, and no verification that trades executed correctly. The 'Best Practices' section is a list of tips, not a workflow.	1 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to external files. The full API reference, risk management details, event handling, and discovery features are all inlined in a single document. The API reference sections should be split into separate files with the SKILL.md providing a concise overview and navigation.	1 / 3
	Total	5 / 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: e71a5f6

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