percolator
On-chain Solana perpetual futures
49
37%
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/percolator/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—it identifies a narrow domain but fails to describe any concrete actions the skill performs or when it should be selected. It reads more like a topic label than a functional skill description, making it inadequate for Claude to reliably choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Opens and closes perpetual futures positions, queries funding rates, calculates PnL, and manages margin on Solana DEX protocols.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about perps, perpetual futures, leverage trading, funding rates, or on-chain derivatives on Solana.'
Include common user-facing synonyms and variations such as 'perps', 'perp trading', 'leverage', 'liquidation', and any specific protocol names (e.g., 'Drift', 'Mango Markets') to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Solana perpetual futures') but lists no concrete actions—no verbs describing what the skill actually does (e.g., open positions, calculate funding rates, query markets). | 1 / 3 |
Completeness | The description only vaguely hints at a domain ('what') without specifying concrete capabilities, and completely lacks any 'when' guidance or explicit trigger clause. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Solana', 'perpetual futures', and 'on-chain' that a user might mention, but misses common variations such as 'perps', 'perp trading', 'leverage', 'DEX', or specific protocol names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Solana' and 'perpetual futures' is fairly niche, which helps distinguish it, but the lack of specific actions means it could overlap with general Solana or DeFi trading skills. | 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 it critically lacks workflow guidance for financial operations that involve real funds on-chain. There are no validation steps, no sequencing (e.g., must deposit before trading), no error handling, and no details on important parameters like leverage, slippage tolerance, or confirmation flows.
Suggestions
Add a workflow section showing the typical sequence: connect wallet → deposit collateral → open position → monitor → close, with explicit validation at each step (e.g., confirm transaction hash, check balance before proceeding).
Add concrete examples showing expected output for each command (e.g., what a successful long position opening looks like, what error messages mean).
Include critical parameters and constraints: max leverage, minimum collateral, liquidation thresholds, fee structure, and slippage settings.
Add error handling guidance: what to do if a transaction fails, how to check pending transactions, and how to handle partial fills or network issues.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what perpetual futures are, what Solana is, or how leverage works. Every token earns its place. | 3 / 3 |
Actionability | The commands are concrete and specific, but there's no executable code, no examples of expected output, no details on parameters like leverage settings, slippage, or what happens on success/failure. The commands are listed but key details are missing (e.g., what wallet, what RPC endpoint, how authentication works). | 2 / 3 |
Workflow Clarity | There is no workflow sequence at all. For financial operations involving real money on-chain, there should be explicit steps (e.g., deposit collateral first, then open position), validation checkpoints (confirm transaction, check balance), and error handling guidance. Destructive/financial operations with no validation or sequencing is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is short and well-organized with a clear commands section, but for a financial protocol skill there should be references to more detailed docs (e.g., risk parameters, fee structure, liquidation mechanics) even if kept brief. The single flat list is adequate for a simple skill but this domain warrants more structure. | 2 / 3 |
Total | 8 / 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.