Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with concrete, executable code examples and clear chat commands. However, it suffers from being a monolithic reference document rather than a well-structured skill file—the full API reference should be split into separate files with SKILL.md serving as an overview. The workflow for trade execution (a financially consequential operation) lacks explicit validation checkpoints and error recovery flows.
Suggestions
Split the detailed TypeScript API reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links to detailed docs.
Add an explicit trade execution workflow with validation checkpoints: estimate slippage → validate parameters → place order → confirm fill → handle partial fills/rejections.
Reduce repetitive buy/sell pattern examples—show one complete example and note that sell variants follow the same pattern with the obvious method name change.
Add error handling guidance for common failure modes (insufficient balance, API timeouts, rejected maker orders) as part of the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly comprehensive but overly verbose for a skill file. The extensive API reference with numerous console.log examples and repetitive patterns (buy/sell variants shown separately when the pattern is obvious) inflates token count. Much of this would be better in a separate REFERENCE.md. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code examples with complete import paths, configuration objects, and concrete method calls. Chat commands are copy-paste ready with clear parameter syntax. Every operation has a concrete, runnable example. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow for the multi-step process of estimating slippage → placing order → verifying fill → handling failures. The protected order example shows a basic check, but there's no comprehensive error recovery flow or validation checklist for trade execution, which is a destructive/financial operation. | 2 / 3 |
Progressive Disclosure | The entire API reference, all order types, fee structures, and best practices are crammed into a single monolithic file. This content would benefit greatly from splitting the detailed TypeScript API reference into a separate file, keeping SKILL.md as a concise overview with links to detailed docs. | 1 / 3 |
Total | 8 / 12 Passed |