Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a clean, well-structured command reference for MarginFi that is concise and easy to scan. Its main weakness is the lack of workflow guidance around risk management—given that liquidation is a real concern, the skill should include explicit steps for checking health factor before/after borrowing and guidance on what to do when health is low. The commands themselves are clear but could benefit from expected output examples.
Suggestions
Add an explicit workflow section showing the safe sequence: check health → borrow → verify health factor is still safe, with a warning threshold (e.g., 'If health < 1.5, consider repaying before borrowing more').
Include example output for key commands like `/marginfi health` and `/marginfi account` so Claude knows what to expect and can interpret results for users.
Add a brief safety note or validation step about checking health factor before and after borrow operations to prevent liquidation risk.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. The one-line description of MarginFi is appropriate context-setting without over-explaining. Every section earns its place with no unnecessary elaboration. | 3 / 3 |
Actionability | Commands are clearly listed with concrete syntax and examples, but these are slash commands rather than executable code. There's no guidance on what happens when things go wrong (e.g., insufficient collateral, health factor too low), and no details on expected outputs or return formats. | 2 / 3 |
Workflow Clarity | The examples section implicitly shows a workflow (deposit → borrow → check health → repay → withdraw), but there's no explicit sequencing, no validation checkpoints, and no guidance on checking health factor before borrowing or what to do if health factor drops dangerously low. For a protocol involving liquidation risk, missing feedback loops and safety checks is a notable gap. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the content is well-organized into logical sections (Commands, Examples, Configuration, See Also) with clear cross-references to related protocols. No unnecessary nesting or monolithic blocks. | 3 / 3 |
Total | 10 / 12 Passed |