Content
68%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.
The content is highly actionable with concrete commands and executable TypeScript covering all main operations, and it is well-structured, but it suffers from command duplication across sections and — critically for an on-chain financial skill — lacks validation checkpoints in its workflows, capping workflow clarity at 3.
Suggestions
Add explicit validation/confirmation checkpoints to the CLMM workflow, e.g. quote before swap, verify position state before adding/removing, and confirm the position is fully drained before closing.
Consolidate the Commands and Examples sections to remove duplicated syntax, and consider moving the bulk of the TypeScript API reference into a separate reference file linked from SKILL.md.
Trim redundant tool-name tables that restate the slash commands, keeping only what is not already shown.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly concrete and free of general-knowledge padding, but it duplicates command syntax across the Commands and Examples sections and repeats much of it again in the Tools Available tables, and the TypeScript API section runs seven long examples that could be tightened, matching the 'mostly efficient but could be tightened' anchor. | 3 / 5 |
Actionability | Provides copy-paste-ready slash commands with exact syntax and fully executable TypeScript code using realistic mints, lamport amounts, and slippage values covering swaps, CLMM create/add/remove/harvest, and AMM add/remove — the common cases are all covered. | 5 / 5 |
Workflow Clarity | The CLMM Position Management section lists a sequence (choose pool, set range, deposit; then add/remove/harvest/close), but these are destructive on-chain financial operations with no validation or confirmation checkpoints, so per the rubric cap workflow clarity cannot exceed 3. | 3 / 5 |
Progressive Disclosure | The single self-contained file is well-organized with clear section headers (Commands, Examples, Pool Types, Tools, TypeScript API, Env Vars, Position Management) and no nested references, but at ~190 lines with no external bundle files the long TypeScript API section could arguably live in a separate reference, leaving it at good-but-not-ideal structure. | 4 / 5 |
Total | 15 / 20 Passed |