copy-trading
Automatically copy trades from successful wallets on Polymarket and crypto
68
56%
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/copy-trading/SKILL.mdQuality
Discovery
32%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 specific niche (Polymarket copy trading) but is too brief and lacks critical components. It fails to include explicit trigger guidance ('Use when...') and doesn't comprehensively describe the skill's capabilities beyond the basic concept of copying trades.
Suggestions
Add a 'Use when...' clause with trigger terms like 'copy trading', 'follow wallet', 'mirror trades', 'Polymarket automation', or 'prediction market trading'
Expand the capabilities list to include specific actions like 'monitor successful wallets, automatically execute matching trades, track performance, set position limits'
Include natural language variations users might say such as 'follow traders', 'automated betting', or 'wallet tracking'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Polymarket, crypto trading) and one action (copy trades), but lacks comprehensive detail about what specific operations are performed (e.g., monitoring, executing, tracking, setting limits). | 2 / 3 |
Completeness | Describes what it does (copy trades) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Polymarket', 'crypto', 'trades', and 'wallets', but misses common variations users might say like 'copy trading', 'mirror trades', 'follow traders', 'prediction markets', or 'automated trading'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Polymarket' provides some distinctiveness, but 'crypto' is broad and could overlap with other crypto-related skills. The lack of explicit triggers increases conflict risk with general trading or wallet management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%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-written, actionable skill with excellent code examples and comprehensive API coverage. The main weaknesses are the lack of explicit workflow sequencing with validation checkpoints for this risky financial operation, and the monolithic structure that could benefit from progressive disclosure to separate files.
Suggestions
Add a 'Getting Started' workflow section with explicit steps: 1) Verify credentials, 2) Test with paper trading, 3) Start with one wallet and small sizes, 4) Validate trades are copying correctly before scaling up
Add validation checkpoints for risky operations, such as verifying API credentials work before starting copy trading, and confirming followed addresses are valid/active traders
Split the TypeScript API Reference into a separate REFERENCE.md file and link to it from the main skill, keeping only the quick start examples inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands and code without explaining basic concepts Claude already knows. Every section delivers actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, complete with configuration objects, event handlers, and concrete command syntax. All examples include specific values and realistic parameters. | 3 / 3 |
Workflow Clarity | While individual features are well-documented, the overall workflow for setting up and running copy trading lacks explicit sequencing. Missing validation checkpoints for risky operations like verifying API credentials work before starting, or confirming wallet addresses are valid before following. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting the API reference into a separate file. The 200+ lines of TypeScript API details could be referenced rather than inline. | 2 / 3 |
Total | 10 / 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
2a8c94e
- 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.