pumpfun
Pump.fun - Complete Solana memecoin launchpad. Discovery, trending, gainers, losers, token data all work without a key. Trading requires SOLANA_PRIVATE_KEY.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 description excels at specificity and distinctiveness with clear domain terminology (Pump.fun, Solana, memecoin). It lists concrete capabilities and technical requirements. However, it lacks an explicit 'Use when...' clause which would help Claude know exactly when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Pump.fun, Solana memecoins, token launches, or crypto trading on Solana'
Consider adding common user phrasings like 'new token launches', 'crypto pumps', or 'Solana tokens' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Discovery, trending, gainers, losers, token data' and 'Trading'. Also specifies technical requirements (SOLANA_PRIVATE_KEY) which adds clarity. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the feature list. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Pump.fun', 'Solana', 'memecoin', 'launchpad', 'trending', 'gainers', 'losers', 'token data', 'Trading'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'Pump.fun' and 'Solana memecoin launchpad' - highly specific platform and blockchain. Unlikely to conflict with other skills due to distinct domain terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%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 API reference that excels at conciseness and actionability - it's essentially a command cheatsheet that respects Claude's intelligence. However, it lacks workflow guidance for common multi-step operations (discovery to trading) and validation checkpoints for financial transactions. The monolithic structure works but could benefit from progressive disclosure for advanced topics.
Suggestions
Add a 'Common Workflows' section showing multi-step sequences like: 1. /pump trending → 2. /pump stats <mint> → 3. /pump quote → 4. /pump buy, with validation checkpoints between steps
Include validation guidance for trading operations: checking quote results before executing, verifying transaction success, handling common errors
Consider splitting WebSocket monitoring and Creator Tools into separate reference files, keeping SKILL.md as a quick-reference overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - uses command reference format with minimal prose. No unnecessary explanations of what Pump.fun is or how Solana works. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides exact command syntax with concrete examples, specific options with defaults, and copy-paste ready commands. The trading examples show real usage patterns with actual flag combinations. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there's no guidance on multi-step workflows like 'discover -> analyze -> trade' sequences. Missing validation steps for trading operations (e.g., check quote before executing buy, verify transaction success). | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections with tables, but everything is in one file. For 32 tools, some content (like detailed pool descriptions or WebSocket usage) could be split into separate reference files with clear navigation. | 2 / 3 |
Total | 10 / 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
2a8c94e
- 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.