kamino

Kamino Finance — Solana lending, borrowing, and liquidity vaults

Quality

42%

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 identifies the platform and general domain but lacks the depth needed for reliable skill selection. It provides no explicit trigger guidance ('Use when...') and misses common user terminology. The description reads more like a tagline than actionable selection criteria.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when user asks about Kamino, Solana DeFi, yield farming, or liquidity provision'

Expand trigger terms to include natural user language: 'DeFi', 'yield', 'APY', 'collateral', 'deposit', 'withdraw', 'loan'

List specific concrete actions: 'deposit collateral, borrow assets, manage vault positions, check interest rates, view portfolio'

Dimension	Reasoning	Score
Specificity	Names the domain (Kamino Finance, Solana) and some actions (lending, borrowing, liquidity vaults), but doesn't list comprehensive concrete actions like 'deposit collateral', 'withdraw funds', 'check APY rates', etc.	2 / 3
Completeness	Only addresses 'what' at a high level (lending, borrowing, vaults) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Kamino', 'Solana', 'lending', 'borrowing', 'liquidity vaults', but missing common variations users might say like 'DeFi', 'yield', 'APY', 'collateral', 'loan', or 'deposit'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Kamino Finance' and 'Solana' provides some distinctiveness, but 'lending, borrowing, and liquidity vaults' could overlap with other DeFi or finance-related skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

52%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is extremely concise and well-organized as a command reference, but lacks critical workflow guidance for DeFi operations that carry liquidation risk. The commands are listed clearly but without context on sequencing (e.g., must deposit before borrowing) or validation steps (e.g., always check health after borrowing). For a lending protocol where mistakes can result in liquidation, this is a significant gap.

Suggestions

Add a 'Workflow' section showing the safe sequence for lending operations: deposit collateral → check health → borrow → monitor health → repay → withdraw, with explicit validation checkpoints

Include health factor thresholds and what they mean (e.g., 'Health < 1.0 = liquidation risk, always verify health > 1.5 before withdrawing collateral')

Clarify what these commands actually are - are they slash commands for a bot, CLI tools, or SDK method references? Add one executable code example showing actual implementation

Add a warning section about liquidation risks and the importance of checking health factor before and after position changes

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what lending protocols are or how Solana works. Every line is a command reference or essential configuration.	3 / 3
Actionability	Commands are clearly listed with parameters, but they're CLI-style references rather than executable code. Missing actual implementation details - how do these commands work? Are they shell commands, SDK calls, or something else?	2 / 3
Workflow Clarity	No workflow guidance for multi-step DeFi operations. Lending/borrowing involves critical sequences (deposit collateral BEFORE borrowing, check health BEFORE withdrawing) with liquidation risk, but no validation checkpoints or sequencing is provided.	1 / 3
Progressive Disclosure	Good organization with clear sections (Lending, Liquidity Vaults, Info). References to related skills are helpful. However, for a protocol with liquidation risk and complex vault mechanics, there should be links to detailed guides on health management and vault strategies.	2 / 3
	Total	8 / 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: 2a8c94e

Reviewed: 29 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.