kamino

Kamino Finance — Solana lending, borrowing, and liquidity vaults

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/kamino/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a brief title-like phrase that identifies the platform and domain but lacks the depth needed for effective skill selection. It names Kamino Finance and core DeFi activities but omits a 'Use when...' clause and specific concrete actions, making it insufficient for Claude to reliably choose this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Kamino Finance, Solana lending/borrowing, liquidity vaults, or DeFi yield strategies on Solana.'

List specific concrete actions such as 'deposit collateral, borrow assets, manage liquidity vault positions, check APY rates, withdraw funds'.

Include additional natural trigger terms users might say: 'DeFi', 'yield', 'APY', 'collateral', 'Solana loans', 'kToken', 'KLEND'.

Dimension	Reasoning	Score
Specificity	Names the domain (Kamino Finance, Solana) and some actions (lending, borrowing, liquidity vaults), but doesn't list specific concrete actions like 'deposit collateral', 'check borrow rates', 'manage vault positions', etc.	2 / 3
Completeness	Provides a brief 'what' (lending, borrowing, liquidity vaults on Solana) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also quite thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Kamino', 'Solana', 'lending', 'borrowing', and 'liquidity vaults' that users might say, but misses common variations like 'DeFi', 'yield', 'APY', 'collateral', 'loan', 'supply', or 'Kamino Finance SDK'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Kamino Finance' and 'Solana' provides some distinctiveness, but 'lending, borrowing, and liquidity vaults' could overlap with other DeFi or Solana protocol skills. Adding more specific triggers would reduce conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

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 well-structured, concise command reference for Kamino Finance interactions. Its main weakness is the lack of workflow guidance for multi-step DeFi operations where order and validation matter (e.g., deposit-borrow-monitor health cycles), and the commands lack context about what tool or framework implements them. The content reads more like a command cheat sheet than an actionable skill with safety guardrails for financial operations.

Suggestions

Add a brief workflow section showing common multi-step sequences (e.g., 'Deposit collateral → Check health → Borrow → Monitor health') with explicit validation checkpoints like checking health factor before and after borrowing.

Include guidance on safety thresholds — e.g., 'Do not borrow if health factor would drop below 1.5' or 'Always run /kamino health after borrowing to verify liquidation distance.'

Clarify what tool or framework these slash commands belong to, so Claude knows when and how to invoke them.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. The one-line description of Kamino is justified context (protocol-specific knowledge Claude wouldn't inherently have). Every section is tightly structured with no unnecessary explanation of concepts like lending, borrowing, or Solana basics.	3 / 3
Actionability	The commands are clearly listed with syntax and parameters, and examples show concrete usage. However, these are slash commands for a specific tool/plugin with no indication of what SDK, API, or tool implements them — there's no executable code, no error handling guidance, and no explanation of what happens under the hood or how to programmatically interact with Kamino.	2 / 3
Workflow Clarity	Individual commands are clear, but there's no guidance on multi-step workflows like 'deposit then borrow' sequences, no mention of checking health factor before/after borrowing, and no validation checkpoints for risky operations like borrowing near liquidation thresholds. For a lending protocol where liquidation is a real risk, missing feedback loops (check health -> borrow -> re-check health) is a significant gap.	2 / 3
Progressive Disclosure	For a skill of this size and scope, the organization is appropriate. Content is well-sectioned (Commands split by category, Examples, Configuration, See Also with cross-references to related skills). No need for external files given the content volume.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: 11 days ago

Table of Contents

Discovery Implementation Validation

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.