Content
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is admirably concise and provides a clear command reference, but it critically lacks workflow guidance for financial operations that involve real funds on-chain. There are no validation steps, no sequencing (e.g., must deposit before trading), no error handling, and no details on important parameters like leverage, slippage tolerance, or confirmation flows.
Suggestions
Add a workflow section showing the typical sequence: connect wallet → deposit collateral → open position → monitor → close, with explicit validation at each step (e.g., confirm transaction hash, check balance before proceeding).
Add concrete examples showing expected output for each command (e.g., what a successful long position opening looks like, what error messages mean).
Include critical parameters and constraints: max leverage, minimum collateral, liquidation thresholds, fee structure, and slippage settings.
Add error handling guidance: what to do if a transaction fails, how to check pending transactions, and how to handle partial fills or network issues.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what perpetual futures are, what Solana is, or how leverage works. Every token earns its place. | 3 / 3 |
Actionability | The commands are concrete and specific, but there's no executable code, no examples of expected output, no details on parameters like leverage settings, slippage, or what happens on success/failure. The commands are listed but key details are missing (e.g., what wallet, what RPC endpoint, how authentication works). | 2 / 3 |
Workflow Clarity | There is no workflow sequence at all. For financial operations involving real money on-chain, there should be explicit steps (e.g., deposit collateral first, then open position), validation checkpoints (confirm transaction, check balance), and error handling guidance. Destructive/financial operations with no validation or sequencing is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is short and well-organized with a clear commands section, but for a financial protocol skill there should be references to more detailed docs (e.g., risk parameters, fee structure, liquidation mechanics) even if kept brief. The single flat list is adequate for a simple skill but this domain warrants more structure. | 2 / 3 |
Total | 8 / 12 Passed |