Coordinated multi-wallet trading on Pump.fun
63
49%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/pump-swarm/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 severely underdeveloped, providing only a high-level topic without concrete actions or usage triggers. It fails to explain what specific operations the skill performs (buying, selling, sniping, bundling?) and gives Claude no guidance on when to select this skill. The Pump.fun reference provides minimal distinctiveness but is insufficient for reliable skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Execute coordinated buy/sell orders across multiple wallets, bundle transactions for token launches, manage wallet portfolios'
Add an explicit 'Use when...' clause with trigger terms like 'Pump.fun', 'memecoin launch', 'bundled buy', 'multi-wallet', 'Solana token', 'snipe tokens'
Include common user phrases and variations such as 'pump and dump', 'token sniping', 'coordinated buys', or 'wallet coordination' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('coordinated multi-wallet trading') without listing any concrete actions. It doesn't specify what operations are performed - no verbs like 'execute trades', 'manage wallets', 'monitor prices', etc. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (trading on Pump.fun) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('multi-wallet', 'trading', 'Pump.fun') that users might mention, but misses common variations like 'memecoin', 'token launch', 'buy/sell', 'Solana', or 'bundled transactions'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Pump.fun' provides some distinctiveness as a specific platform, but 'multi-wallet trading' is generic enough to potentially overlap with other crypto trading or wallet management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with excellent concrete examples and clear workflow documentation. The main weakness is verbosity - content is repeated across sections (execution modes, multi-DEX examples) and the file could benefit from splitting detailed reference material into separate files. Safety features and validation steps are well-documented.
Suggestions
Consolidate the execution modes content - remove the 'Execution Modes Deep Dive' section or merge it with the initial table to eliminate redundancy
Move detailed preset documentation and Multi-DEX deep dive to separate reference files (e.g., PRESETS.md, MULTI_DEX.md) with brief summaries in the main skill
Remove duplicate examples (multi-DEX examples appear in both 'Examples' and 'Multi-DEX Examples' sections)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (execution modes explained twice, examples repeated across sections). The Multi-DEX section repeats information already covered in the options table. Could be tightened by consolidating duplicate content. | 2 / 3 |
Actionability | Excellent concrete guidance with copy-paste ready commands, specific examples for every feature, clear option tables, and executable bash commands. Every command shows exact syntax with realistic parameters. | 3 / 3 |
Workflow Clarity | Clear buy/sell flows with explicit steps, validation checkpoints (balance check, position check before sell), and safety features documented. The 'refresh before sell' requirement is clearly stated with examples showing the correct sequence. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in one monolithic file. The 'Execution Modes Deep Dive' section and extensive preset documentation could be split into separate reference files for better 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 | |
2a8c94e
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.