pumpfun
Pump.fun - Complete Solana memecoin launchpad. Discovery, trending, gainers, losers, token data all work without a key. Trading requires SOLANA_PRIVATE_KEY.
78
73%
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/pumpfun/SKILL.mdQuality
Discovery
82%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 is a strong description that clearly identifies a specific platform (Pump.fun), blockchain (Solana), and domain (memecoin launchpad) with concrete capabilities listed. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The distinction between key-required and keyless operations is a useful practical detail.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Pump.fun, Solana memecoins, token launches, or wants to check trending/gaining/losing tokens on Pump.fun.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: discovery, trending, gainers, losers, token data retrieval, and trading. Also specifies the authentication requirement (SOLANA_PRIVATE_KEY) for trading vs. read-only operations. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (discovery, trending, gainers/losers, token data, trading on Pump.fun), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Pump.fun', 'Solana', 'memecoin', 'launchpad', 'trending', 'gainers', 'losers', 'token data', 'trading'. These cover the domain well and match how users naturally talk about this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Pump.fun specifically on Solana for memecoins. The combination of platform name, blockchain, and specific feature set makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference card that excels at providing concrete, actionable command syntax with good examples. However, it lacks workflow guidance for safe trading operations (quote → verify → trade → confirm), contains redundant sections (Features list, Complete Tool List), and misses an opportunity to provide safety guardrails for financial operations involving real funds.
Suggestions
Add a trading workflow section with explicit safety steps: check price/quote → verify token legitimacy → execute trade → confirm transaction, especially since this involves real money
Remove the redundant 'Features' bullet list and 'Complete Tool List' table—both duplicate information already presented in the categorized command sections above
Add error handling guidance: what happens when a trade fails, how to handle insufficient balance, what slippage errors look like, and how to retry
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of command reference tables, but the 'Features' section at the end is entirely redundant—it just restates capabilities already evident from the tool listings. The 'Complete Tool List' table also duplicates information already presented in the categorized sections above it. | 2 / 3 |
Actionability | Commands are concrete and copy-paste ready with specific syntax, options, flags, and realistic examples. Trading examples show actual usage patterns with different option combinations, and configuration shows exact environment variable names. | 3 / 3 |
Workflow Clarity | There is no guidance on workflow sequencing for trading operations—no mention of checking price/quote before buying, no validation steps after trades, no error handling guidance. For financial operations involving real money, the absence of safety checkpoints (e.g., 'always quote before trading', 'verify token before buying') is a significant gap. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections with clear headers, but everything is in a single monolithic file. The redundant Features and Complete Tool List sections add bulk. No references to external files for advanced topics like trading strategies, error handling, or detailed API documentation. | 2 / 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.