Meme rush Skill from Binance

[markusha77]

New Skill Contribution

Skill Info

• Skill ID: meme-rush
• Category: Blockchain
• Description: Fast meme-token market tracking for launch lifecycle and hot-topic narratives, with filters for migration, holders, and net inflow.

Checklist

• SKILL.md has valid YAML frontmatter with all required fields
• Skill ID matches the directory name
• Category is one of: productivity, development, communication, writing, research, other
• Instructions are clear and self-contained
• Instructions are under 4000 tokens
• No external URLs referenced in instructions
• Tested the skill with an AI agent and it produces good results
• Added usage examples in the frontmatter

Testing

Describe how you tested this skill:

Notes

Any additional context or notes for reviewers.

[greptile-apps]

Greptile Summary

This PR adds a new meme-rush skill integrating two Binance Web3 APIs: API 1 (Meme Rush) for launchpad token lifecycle tracking (New → Finalizing → Migrated stages across BSC and Solana), and API 2 (Topic Rush) for AI-powered hot narrative discovery sorted by net inflow and viral momentum. The skill is well-structured with comprehensive filter documentation and usage examples.

Issues found:

• Blocked – Invalid category value: The frontmatter declares category: Blockchain, which is not in the allowed set (productivity, development, communication, writing, research, other). This will likely fail skill validation.
• priceChange formatting undocumented: In the API 1 response table, priceChange lacks the "(pre-formatted %, append % directly)" note that its counterpart priceChange24h in API 2 carries explicitly. Note 2 in the Notes section also omits it, creating an inconsistency an AI agent could misinterpret.
• Note 1 scope is API-1-only but written globally: The shared Notes section states "only chainId and rankType are required" — this conflicts with API 2's sort being documented as required. (A previous thread addresses the sort required/optional contradiction directly; this comment focuses on clarifying the note's scope.)
• Skill not tested: The author left the "Tested the skill with an AI agent and it produces good results" checklist item unchecked, meaning correctness against live APIs has not been verified.

Confidence Score: 2/5

• Not ready to merge — the category field uses an invalid value that will fail schema validation, and the skill is self-reported as untested.
• The skill content itself is thorough and well-documented, but it carries a blocking metadata issue (category: Blockchain is not a valid enum value per the contribution checklist), several documentation inconsistencies that could mislead an AI agent (pre-formatting ambiguity for priceChange, globally-scoped Note 1 that conflicts with API 2 requirements), and the author explicitly did not check the "Tested with AI agent" box.
• skills/meme-rush/SKILL.md — invalid category value and documentation inconsistencies need to be resolved before merging.

Important Files Changed

Filename	Overview
skills/meme-rush/SKILL.md	New skill adding two Binance Web3 API integrations (Meme Rush launchpad tracker + Topic Rush narrative discovery); blocked by invalid category value ("Blockchain" is not an allowed enum), with additional documentation inconsistencies around priceChange formatting and Note 1 scope ambiguity across APIs.

Sequence Diagram

sequenceDiagram
    participant Agent as AI Agent
    participant API1 as Binance API 1<br/>(Meme Rush – POST)
    participant API2 as Binance API 2<br/>(Topic Rush – GET)

    Note over Agent: User asks for meme token tracking

    Agent->>API1: POST /pulse/rank/list<br/>{ chainId, rankType, [filters] }
    API1-->>Agent: { data: { tokens[] } }<br/>Core fields, holder %, dev info, tags, socials

    Note over Agent: User asks for hot narrative topics

    Agent->>API2: GET /social-rush/rank/list<br/>?chainId=&rankType=&sort=&[filters]
    API2-->>Agent: { data[] }<br/>Topic fields + tokenList[] per topic

    Note over Agent: Format response<br/>Append % to pre-formatted fields<br/>Prefix icon URLs with https://bin.bnbstatic.com

Loading

_{Last reviewed commit: "add Meme Rush skill ..."}

[greptile-apps]

sort marked required but Note 1 contradicts this

API 2 lists sort as a Required Parameter alongside chainId and rankType, but Note 1 at line 342 states: "Only chainId and rankType are required; all other parameters are optional filters."

An AI agent following this skill will receive conflicting instructions: should it always send sort, or is it optional? If sort truly has a default server-side behavior when omitted, it should be moved to the Optional Parameters table. If it is genuinely required, Note 1 needs to be updated to reflect that.

Suggested change

	| sort | integer | Sort by: `10`=create time, `20`=net inflow, `30`=viral time |
	> **Sort convention**: When the user does not specify a sort preference, use `sort=10` (create time) for Latest/Rising, and `sort=30` (viral time) for Viral.
	| chainId | string | Chain ID: `56`, `CT_501` |
	| rankType | integer | `10`=Latest, `20`=Rising, `30`=Viral |

And move sort to the Optional table with a default-value note, or correct Note 1 to say "Only chainId and rankType are required for API 1; API 2 additionally requires sort."

[greptile-apps]

tokenAgeMin/Max unit is unspecified

The tokenAgeMin/Max filter is documented as type long but gives no indication of what unit should be used (seconds, milliseconds, minutes?). Compared with migrateTime and createTime in the response section which are explicitly noted as (ms), this omission could cause an AI agent to construct incorrect filter values.

Suggested change

	| tokenAgeMin/Max | long | Token age |
	| tokenAgeMin/Max | long | Token age in milliseconds |

[greptile-apps]

paidOnDexScreener filter missing valid values

Every similar boolean/flag filter in this table explicitly documents its accepted values (e.g., pumpfunLiving: 1=yes, cmcBoost: 1=yes, exclusive: 0=no, 1=yes), but paidOnDexScreener has no value description. An AI agent will have no way to know what value to send to enable or disable this filter.

Suggested change

	| paidOnDexScreener | integer | Paid on DexScreener |
	| paidOnDexScreener | integer | Paid on DexScreener: `1`=yes |

[greptile-apps]

Invalid category value

The frontmatter sets category: Blockchain, but the contribution checklist explicitly lists the allowed values as: productivity, development, communication, writing, research, other. Blockchain is not in this list and will likely cause validation to fail for this skill submission.

Suggested change

	category: Blockchain
	category: other