solend
Solend — Solana lending and borrowing
52
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/solend/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely terse and reads more like a label than a functional skill description. It names the protocol and general domain but fails to list specific capabilities or provide any guidance on when Claude should select this skill. It would be very difficult for Claude to confidently choose this skill from a large pool of available skills.
Suggestions
Add specific concrete actions such as 'Deposit collateral, borrow tokens, check interest rates, monitor liquidation thresholds, and manage positions on Solend protocol'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Solend, Solana lending/borrowing, supplying assets, or managing DeFi loan positions on Solana'.
Include additional natural trigger terms like 'DeFi', 'collateral', 'interest rate', 'liquidation', 'supply', 'borrow rate', and 'Solana DeFi' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Solana lending and borrowing') without listing any concrete actions. There are no specific capabilities like 'deposit collateral', 'borrow tokens', 'check liquidation risk', etc. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (lending and borrowing) and completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also very weak. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords ('Solend', 'Solana', 'lending', 'borrowing') that users might naturally say, but misses common variations like 'supply', 'collateral', 'interest rates', 'liquidation', 'DeFi', or 'loan'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Solend' specifically is distinctive, but 'Solana lending and borrowing' could overlap with other Solana DeFi lending protocols (e.g., Marginfi, Kamino). The description doesn't clearly delineate its scope from other lending-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured with clear command syntax and cross-references to related protocols. However, it lacks critical workflow guidance for a DeFi lending protocol — there's no sequencing of operations, no health factor monitoring workflow before/after borrowing, and no validation or error handling steps, which is concerning given the financial risk of liquidation.
Suggestions
Add a workflow section showing the recommended sequence: deposit → check health → borrow → monitor health → repay → withdraw, with explicit validation checkpoints (e.g., 'Always run /solend health after borrowing to verify safe health factor')
Include expected output examples for key commands like /solend health and /solend obligation so Claude knows what to interpret
Add safety guardrails: warn about minimum health factor thresholds, what to do if health drops below a threshold, and how to handle failed transactions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. The one-line description of Solend is minimal and useful context for a DeFi protocol. Every section earns its place with no unnecessary explanation of how lending/borrowing works. | 3 / 3 |
Actionability | Commands are clearly listed with syntax, and examples show usage patterns. However, these are slash commands without any underlying executable code, SDK usage, or details on what happens under the hood — there's no guidance on error handling, transaction confirmation, or what output to expect from each command. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow for the multi-step process of depositing, borrowing, monitoring health, and repaying. For a lending protocol where liquidation risk is real, there are no validation checkpoints (e.g., check health after borrowing, verify transaction success) or feedback loops for error recovery. | 1 / 3 |
Progressive Disclosure | Content is well-organized into clear sections (Commands, Examples, Configuration, See Also) with cross-references to related skills. For a skill of this size, the structure is appropriate and navigable. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.