Content
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 |