Meme token fast-trading assistant with two core capabilities: 1. Meme Rush - Real-time meme token lists from launchpads (Pump.fun, Four.meme, etc.) across new, finalizing, and migrated stages 2. Topic Rush - AI-powered market hot topics with associated tokens ranked by net inflow Use this skill when users ask about new meme tokens, meme launches, bonding curve, migration status, pump.fun tokens, four.meme tokens, fast meme trading, market hot topics, or trending narratives.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 skill description that clearly defines two specific capabilities with named platforms and concrete features, includes an explicit 'Use this skill when...' clause with comprehensive trigger terms, and occupies a very distinct niche in meme token trading. The description is well-structured, concise, and uses appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: real-time meme token lists from named launchpads (Pump.fun, Four.meme), across specific stages (new, finalizing, migrated), and AI-powered market hot topics with tokens ranked by net inflow. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (two core capabilities with specific details) and 'when' (explicit 'Use this skill when...' clause listing multiple trigger scenarios). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'new meme tokens', 'meme launches', 'bonding curve', 'migration status', 'pump.fun tokens', 'four.meme tokens', 'fast meme trading', 'market hot topics', 'trending narratives'. These are terms crypto users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on meme token trading with specific platform names (Pump.fun, Four.meme), specific stages (bonding curve, migration), and specific features (Meme Rush, Topic Rush). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 well-structured API reference skill with strong actionability — complete curl examples, detailed parameter tables, and thorough response documentation. Its main weaknesses are the monolithic structure (all content in one file despite being quite lengthy) and the lack of workflow guidance for error handling, pagination, or multi-step trading workflows. The content could be more concise by trimming the Use Cases section and potentially splitting API details into separate reference files.
Suggestions
Add error handling guidance: what to do when the API returns empty data[], rate limiting, or error responses — this is important for a trading-related skill.
Split the detailed API parameter and response tables into separate reference files (e.g., MEME_RUSH_API.md and TOPIC_RUSH_API.md) and keep SKILL.md as a concise overview with quick-start examples.
Add a brief workflow section showing how to combine the two APIs for common trading scenarios (e.g., discover topic → find associated tokens → check token details via Meme Rush).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is largely reference tables and API documentation, which is appropriate for a skill of this complexity. However, the 'Use Cases' section is somewhat verbose and describes scenarios Claude could infer. The protocol reference table is extensive but necessary. Some trimming could be done on descriptive text. | 2 / 3 |
Actionability | The skill provides fully executable curl commands, complete API URLs, exact parameter names/types/values, and detailed response field documentation. Both APIs have copy-paste ready example requests with all required headers and body parameters. | 3 / 3 |
Workflow Clarity | The skill clearly documents two distinct API endpoints with their parameters and responses, but lacks explicit workflow guidance for multi-step scenarios (e.g., 'first check New tokens, then monitor Finalizing, then track Migrated'). There are no validation checkpoints or error handling guidance for API failures or empty responses. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with extensive inline API reference tables that could benefit from being split into separate reference files. With no bundle files provided, all the detailed parameter tables and response schemas are crammed into one document, making it quite long. However, the internal organization with clear section headers is reasonable. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
68fcfa1
Table of Contents
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.