CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meme-rush

Live launchpad feed + AI hot topics for meme tokens. (1) meme-rush: real-time lifecycle feed on launchpads across Solana, BSC and Base (Pump.fun, Four.meme, Flap, ...) — brand-new launches, currently-finalizing / bonding-curve tokens, and just-migrated-to-DEX tokens; filter by dev behavior, age, market cap, and launchpad sub-type (e.g. Open Four Agent ID exclusive launches — anyone can launch; on the bonding curve only Agent ID holders can buy). (2) topic-rush: AI-detected hot market narratives with the associated tokens ranked by inflow. Use for: "new pump.fun launches", "what just migrated", "currently bonding", "hot narratives", "what topic is pumping right now", "live launchpad feed", "AI hot topics", "Agent ID exclusive launches", "Agent ID exclusive bonding curve", "Open Four".

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A dense, well-structured body: ready-to-run commands, a preset for the highlighted use case, and a Rules section packed with genuinely non-obvious API semantics, with detail correctly deferred to references/cli.md. The main deductions are minor duplication between the preset/commands/examples sections and one cross-skill reference path that does not resolve within this bundle.

Suggestions

Drop the preset parameter-table rows that restate values already shown in the ready-to-run commands, and remove the Commands table's example column that duplicates the "How to Call APIs" invocations.

Rewrite the buy hand-off as "the `binance-agentic-wallet` skill's `references/agent-id-exclusive-token-launches.md`" (or a skill-qualified path) so it cannot be read as a file in this bundle's references/ directory, where it does not exist.

Trim the inline optional-filters enumeration in the Commands section to the most commonly used filters and keep only the full list in references/cli.md, which already documents each field's type and semantics.

DimensionReasoningScore

Conciseness

Nearly every rule encodes non-observable API behavior Claude cannot know ("Unknown or misspelled filters are silently ignored", "`tokenAge` is in minutes", "Percentage fields are pre-formatted") with no padding about known concepts. Not 5 because the preset parameter table restates values already visible in the ready-to-run commands, and the Commands table's example column duplicates "How to Call APIs".

4 / 5

Actionability

Fully executable copy-paste CLI invocations with complete JSON payloads for both subcommands and all three lifecycle stages ("node <skill-dir>/scripts/cli.mjs meme-rush '{...}'"), plus explicit required-args, the sort default, and filter enumerations. Not 4 because the examples cover the common cases with no gaps requiring invention.

5 / 5

Workflow Clarity

A single-action skill (pick subcommand, fill filter JSON, run CLI, interpret rows) made unambiguous by the intent-to-command table, the rankType/sort enums with "Default to `sort=10`", and result-interpretation rules such as "An empty list means no such token exists right now — not an error" and "show `null` as 'unknown'". No destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Bulk parameter and return-field detail lives one level deep in references/cli.md with well-signaled pointers to named sections ("Filters that look valid but are silently ignored", "How `null` behaves", "Protocol Reference"), all of which resolve. Not 5 because "references/agent-id-exclusive-token-launches.md" is a dangling path in this bundle (it belongs to the binance-agentic-wallet skill), and the long inline optional-filters list partially duplicates cli.md.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: it states both subcommands' capabilities concretely, names the platforms and chains, and closes with an explicit trigger list of natural user phrases. The only weakness is a few missing colloquial synonyms (e.g. "memecoin", "trending") in the trigger list.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities across both subcommands — "real-time lifecycle feed on launchpads across Solana, BSC and Base", "filter by dev behavior, age, market cap, and launchpad sub-type", "AI-detected hot market narratives with the associated tokens ranked by inflow" — covering all lifecycle stages and sub-types with no material gaps.

5 / 5

Completeness

Both questions are explicitly answered: a detailed two-part "what" (meme-rush lifecycle feed, topic-rush AI narratives) and an explicit "Use for:" clause with concrete trigger phrases. Not 4 because the when-clause is fully explicit with quoted triggers rather than merely present or generic.

5 / 5

Trigger Term Quality

The "Use for" list contains natural user phrasings — "new pump.fun launches", "what just migrated", "currently bonding", "what topic is pumping right now" — plus platform-specific triggers like "Open Four" and "Agent ID exclusive bonding curve". Not 5 because common variants such as "new memecoins", "trending tokens", or chain-named phrases ("new Solana tokens") are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is tightly defined by named launchpads (Pump.fun, Four.meme, Flap, Open Four) and chains, with distinctive triggers like "Agent ID exclusive launches" and "Open Four" that no generic skill would claim. Only "AI hot topics" is even mildly generic, so conflict risk is minimal.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

binance/binance-skills-hub

Path

skills/binance-web3/meme-rush/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.