CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pump-swarm

Coordinated multi-wallet trading on Pump.fun

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/pump-swarm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable command reference with concrete examples throughout. Its main gaps are moderate cross-section redundancy and the absence of explicit validate/feedback loops in the batch trading workflows.

Suggestions

Consolidate the 'Execution Modes' table and 'Execution Modes Deep Dive' into one section, and de-duplicate the multi-DEX examples that appear in both 'Examples' and 'Multi-DEX Examples'.

Add an explicit validate→fix→retry loop to the Buy/Sell flows (e.g. 'If a wallet tx fails, report the per-wallet error and retry via the automatic --parallel fallback') since these are batch financial operations.

DimensionReasoningScore

Conciseness

Mostly efficient reference material (command tables, option tables), but execution modes are covered twice (summary table plus 'Execution Modes Deep Dive') and multi-DEX buy/sell examples are repeated across 'Examples' and 'Multi-DEX Examples', so it could be tightened — matching 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Provides fully executable slash commands with concrete syntax, option tables with defaults (e.g. slippage default 500 = 5%), and copy-paste-ready examples covering buy, sell, presets, multi-DEX, and position checks — matching 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Buy and Sell flows are clearly sequenced (6 numbered steps each) with pre-checks (balance check, position fetch), but these are batch/financial operations without explicit error-recovery feedback loops in the step list, so the batch-operations cap holds at 3 ('steps listed but validation gaps; checkpoints missing or implicit').

3 / 5

Progressive Disclosure

Well-organized into clear sections (Quick Start, Commands, Execution Modes, How It Works, Presets, Troubleshooting) with no nested references, though at ~290 lines some deep-dive content (presets, multi-DEX) could be split into separate files — matching 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description targets a clear, specific niche but is terse: it states what the skill does with no 'when to use' guidance and only generic action terms. Adding an explicit trigger clause with concrete buy/sell phrasings would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when coordinating buys or sells across multiple Pump.fun wallets, or when the user mentions swarm trading, memecoins, Jito bundles, or multi-wallet execution.'

Include natural action keywords and synonyms (buy, sell, tokens, memecoins) so users' actual phrasings match the description.

DimensionReasoningScore

Specificity

Names the domain ('Pump.fun', 'multi-wallet') plus the concrete action 'trading' and the 'Coordinated' framing, but 'trading' is generic and no buy/sell or execution-mode specifics are listed, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Has a clear 'what' ('Coordinated multi-wallet trading on Pump.fun') but no 'Use when...' clause or explicit trigger guidance, which per the guidelines caps completeness at 3 ('clear what, when missing or only weakly implied').

3 / 5

Trigger Term Quality

Includes natural terms a user might say ('trading', 'Pump.fun', 'multi-wallet') but omits common variations and synonyms (buy, sell, tokens, memecoins, swarm, Jito bundles), matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The Pump.fun + multi-wallet niche is mostly distinct with minimal conflict risk, though it could overlap slightly with a generic Solana trading skill, fitting 'mostly distinct; minor overlap risk with closely related skills' rather than the fully-disjoint anchor 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/pump-swarm/SKILL.md

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.