Content
65%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, largely executable API reference with real values and good section structure. Its weaknesses are the total absence of progressive disclosure (everything inlined, no reference files) and missing validation workflows for irreversible real-money operations.
Suggestions
Split the per-DEX API reference (Jupiter, Raydium, Orca, Meteora, Pump.fun) into separate reference files linked from a concise SKILL.md overview.
Add a validation-first workflow for fund-moving operations: quote, check balance and price impact, confirm, then execute, mirroring the error classes already documented.
Trim redundant chat-command example invocations (one example per command suffices) and fix the duplicate `const result` declaration in the Pump.fun section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, executable code with no re-explanation of concepts Claude already knows. Minor trimming is possible: chat commands show 3-4 redundant example invocations each, and the Pump.fun section declares `const result` twice. Not anchor 5 because of these small padded spots. | 4 / 5 |
Actionability | Concrete, executable TypeScript with real mint addresses, imports, slippage values, and typed error classes covers the common cases. Not anchor 5 due to minor gaps: non-executable placeholders like `'POOL_ID_HERE'`, `'token_mint_address'`, and the `executeJupiterSwap({ ... })` stub in the error-handling example. | 4 / 5 |
Workflow Clarity | The content is an API reference rather than a sequenced workflow, and operations that irreversibly move real funds (swaps, LP changes) have no validation or confirmation sequence (e.g. quote -> verify -> execute). The destructive/batch-operations cap of 3 applies. | 3 / 5 |
Progressive Disclosure | Section headers make the document navigable, but ~400 lines of per-DEX API reference, token tables, and slippage guidance are all inlined in SKILL.md with no bundle files (no references/, scripts/, or assets/ exist) and no offloading. This matches "content that should be separate is inline"; it is above anchor 2 only because headers provide reasonable structure. | 3 / 5 |
Total | 14 / 20 Passed |