Content
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a lengthy, speculative API reference for a fictional library ('clodds/slippage') with no real-world executability. It is extremely verbose with repetitive console.log patterns, lacks validation/error-handling workflows critical for financial operations, and dumps everything into a single monolithic file. The content describes rather than instructs, offering no actionable guidance Claude could actually use.
Suggestions
Replace the fictional 'clodds/slippage' API with real, executable code or clearly document which actual platforms/libraries this wraps, so the skill becomes actionable.
Drastically reduce verbosity by removing repetitive console.log output examples — show one complete example and summarize the rest in a table or type definition.
Add explicit error handling and validation workflows (e.g., what happens when slippage exceeds threshold, how to verify order execution, rollback procedures) since these are financial operations.
Split the monolithic content into a concise SKILL.md overview with references to separate files for API reference, DEX-specific guidance, and execution strategies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive console.log statements that add no instructional value. The skill is essentially a speculative API reference for a non-existent library ('clodds/slippage'), with massive amounts of repetitive code showing output formatting rather than teaching actionable patterns. Many sections could be collapsed significantly. | 1 / 3 |
Actionability | Despite appearing code-heavy, none of this is executable — 'clodds/slippage' is a fabricated library. The chat commands (/slippage estimate, etc.) reference no real tool or platform. There's no real system a user or Claude could actually run this against, making it entirely non-actionable. | 1 / 3 |
Workflow Clarity | There is a logical progression from estimation → analysis → optimization → protection, and the best practices section mentions 'always estimate first' before trading. However, there are no explicit validation checkpoints, error handling flows, or feedback loops for what are potentially costly financial operations. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with every API method inlined. The entire document is ~250 lines of detailed API reference that should be split into separate files (e.g., a quick-start overview in SKILL.md with references to API_REFERENCE.md, DEX.md, etc.). No external references or navigation structure exists. | 1 / 3 |
Total | 5 / 12 Passed |