percolator

On-chain Solana perpetual futures

Quality

37%

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/percolator/SKILL.md

Quality

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 severely underdeveloped - it identifies a domain (Solana perpetual futures) but fails to describe any concrete capabilities or provide usage triggers. Claude would struggle to know when to select this skill or what actions it enables. The description reads more like a topic label than a functional skill description.

Suggestions

Add specific actions the skill performs (e.g., 'Execute trades, manage positions, calculate funding rates, analyze liquidation risks for Solana perpetual futures')

Add a 'Use when...' clause with trigger terms like 'perps', 'perpetuals', 'SOL futures', 'funding rate', 'leverage trading', 'liquidation'

Include specific protocol names if applicable (e.g., 'Drift', 'Mango Markets') to improve distinctiveness and trigger matching

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - it only names a domain ('Solana perpetual futures') without describing what the skill actually does (e.g., 'trade', 'analyze', 'monitor positions').	1 / 3
Completeness	Missing both 'what' (no actions described) and 'when' (no 'Use when...' clause or trigger guidance). The description only identifies a topic area without explaining capabilities or usage triggers.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Solana', 'perpetual futures', 'on-chain') that users might say, but missing common variations like 'perps', 'SOL', 'derivatives', 'trading', or specific protocol names.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Solana' and 'perpetual futures' provides some specificity, but without actions it could overlap with general Solana skills or general trading skills. The niche is identifiable but boundaries are unclear.	2 / 3
	Total	6 / 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.

The skill is admirably concise and provides a clear command reference, but lacks the workflow guidance and concrete examples needed for safe execution of financial operations. Critical information like deposit-before-trade requirements, error handling, and position validation are missing.

Suggestions

Add a basic workflow showing the typical sequence: deposit collateral → check status → open position → monitor → close

Include example outputs for key commands like `/percolator status` and `/percolator positions` so Claude knows what to expect

Add validation guidance: how to verify a deposit succeeded before trading, how to confirm position opened correctly

Specify important parameters: leverage levels, minimum/maximum sizes, USDC decimal handling

Dimension	Reasoning	Score
Conciseness	Extremely lean - no unnecessary explanations of what perpetual futures are or how Solana works. Every line serves a purpose and assumes Claude's competence.	3 / 3
Actionability	Commands are clearly listed with brief descriptions, but lacks concrete examples of usage, expected outputs, or parameter details (e.g., what leverage is used, minimum sizes, USDC decimals).	2 / 3
Workflow Clarity	No workflow guidance for multi-step processes like opening a position (deposit first? check balance?). Missing validation steps for financial operations which are inherently risky.	1 / 3
Progressive Disclosure	Simple structure appropriate for a brief skill, but could benefit from signposting to additional resources for error handling, position management workflows, or API details if they exist.	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.