Agent skill · Content & Marketing

meme-rush

Live launchpad feed + AI hot topics for meme tokens. (1) meme-rush: real-time lifecycle feed on launchpads (Pump.fun, Four.meme) — brand-new launches, currently-finalizing / bonding-curve tokens, and just-migrated-to-DEX tokens; filter by dev behavior, age, market cap. (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".

binancegithub.com/binanceGitHub ↗
claude-codeships scripts
Install
npx skills add binance/binance-skills-hub --skill meme-rush --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 5 KB
Bundled scripts: yes
Version: 2.0
Declared author: binance-web3-team
Path: skills/binance-web3/meme-rush/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 947
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Meme Rush Skill ## Overview Two rank feeds fronted by one CLI: `meme-rush` (launchpad lifecycle tracking) and `topic-rush` (AI hot-topic discovery with associated tokens). The CLI owns URL, method, JSON encoding, timeout, and upstream error mapping — the agent only picks the subcommand and fills the filter JSON. ## When to Use This Skill | User intent | Command | |-------------|---------| | New / finalizing / migrated meme tokens on a launchpad | `meme-rush` | | AI-generated market hot topics and their associated tokens | `topic-rush` | ## Supported Chains | Chain | chainId | Supported on | |-------|---------|--------------| | BSC | `56` | `meme-rush`, `topic-rush` | | Solana | `CT_501` | `meme-rush`, `topic-rush` | | Base | `8453` | `meme-rush` | ## How to Call APIs ```bash node <skill-dir>/scripts/cli.mjs meme-rush '{"chainId":"CT_501","rankType":10,"limit":20}' node <skill-dir>/scripts/cli.mjs topic-rush '{"chainId":"CT_501","rankType":10,"sort":10,"asc":false}' ``` ## Commands | Command | Purpose | Required args | Example | |---------|---------|---------------|---------| | `meme-rush` | Launchpad token lifecycle ranking (new / finalizing / migrated) | `chainId`, `rankType` |

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Supported Chains
  4. How to Call APIs
  5. Commands
  6. Rules
  7. Full CLI Reference
Ships with 2 files
  • references/cli.md
  • scripts/cli.mjs
Commands it runs
node <skill-dir>/scripts/cli.mjs meme-rush '{"chainId":"CT_501","rankType":10,"limit":20}'
node <skill-dir>/scripts/cli.mjs topic-rush '{"chainId":"CT_501","rankType":10,"sort":10,"asc":false}'
More from binance-skills-hub
All skills →
About this skill
What does the meme-rush skill do?

Live launchpad feed + AI hot topics for meme tokens. (1) meme-rush: real-time lifecycle feed on launchpads (Pump.fun, Four.meme) — brand-new launches, currently-finalizing / bonding-curve tokens, and just-migrated-to-DEX tokens; filter by dev behavior, age, market cap. (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".

How do I install it?

Run `npx skills add binance/binance-skills-hub --skill meme-rush --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From binance/binance-skills-hub, a repository with 947 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going