meme-coin-audit

Meme coin and token security audit — rug pull detection (honeypot, hidden mint, fee manipulation, LP lock bypass), Solana SPL token analysis (freeze authority, mint authority, metadata mutability), Token-2022 extension risks (transfer hooks, permanent delegate), DEX liquidity pool attacks (sandwich amplification, LP drain, bonding curve exploits), pump.fun/Raydium/Jupiter integration risks, token_scanner.py automation, and real exploit examples from 2024-2025. Use for any token audit, rug pull assessment, meme coin security review, or pre-investment due diligence.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/meme-coin-audit/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The skill is highly actionable with copy-paste grep/CLI commands and explicit kill-criteria checkpoints, but the large Foundry POC template contains incomplete placeholders, the end-to-end workflow is implicit rather than numbered, and the referenced deep-dive files do not exist in the bundle.

Suggestions

Complete the Foundry POC template: replace `// ... buy tokens on Uniswap`, `// Add liquidity...`, and `// Assert: received almost nothing` placeholders with actual swap/assertion calls so the code is copy-paste executable.

Add an explicit numbered end-to-end audit workflow (e.g., 1. Run pre-dive kill signals -> 2. Audit each bug class via grep + Kill-if -> 3. Run token_scanner.py -> 4. Verify on-chain authorities) to make the sequence and checkpoints unambiguous.

Either create the referenced `web3/10-meme-coin-bugs.md`, `web3/11-solana-token-audit.md`, and `web3/12-dex-lp-attacks.md` files in a `references/` bundle, or remove the 'FULL REFERENCE FILES' section so the body does not promise deep-dive files that do not exist.

Dimension	Reasoning	Score
Conciseness	The body is dense and action-oriented with little concept fluff, but at ~290 lines it carries an 80-line Foundry POC template plus repeated grep blocks that could be tightened; not every token earns its place.	2 / 3
Actionability	Most of the body is copy-paste ready (grep patterns, `python3 tools/token_scanner.py ...`, `solana account <MINT> --output json`), but the marquee Foundry POC has incomplete placeholders like `// ... buy tokens on Uniswap` and `// Assert: received almost nothing`, leaving key details missing.	2 / 3
Workflow Clarity	Validation checkpoints exist (pre-dive kill signals, per-class 'Kill if' criteria, the numbered Solana quick checks), but the overall end-to-end audit sequence is implicit rather than a numbered procedure and there is no validate-fix-retry feedback loop.	2 / 3
Progressive Disclosure	The 'FULL REFERENCE FILES' section clearly signals one-level-deep references to `web3/10-meme-coin-bugs.md`, `web3/11-solana-token-audit.md`, and `web3/12-dex-lp-attacks.md`, but none of these files exist in the bundle (no references/ dir), so the disclosure is only partially realized and much detail stays inline.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 clearly states both what the skill does and when to use it via an explicit 'Use for...' clause, with concrete capabilities and natural trigger terms in a distinct niche and proper third-person voice.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions: 'rug pull detection (honeypot, hidden mint, fee manipulation, LP lock bypass)', 'Solana SPL token analysis (freeze authority, mint authority, metadata mutability)', and 'Token-2022 extension risks (transfer hooks, permanent delegate)'.	3 / 3
Completeness	It explicitly answers what the skill does (the enumerated audit capabilities) and when to use it via an explicit 'Use for...' trigger clause.	3 / 3
Trigger Term Quality	The 'Use for any token audit, rug pull assessment, meme coin security review, or pre-investment due diligence' clause plus 'meme coin', 'rug pull', and 'token security audit' give good coverage of natural terms a user would say.	3 / 3
Distinctiveness Conflict Risk	It carves a clear, narrow niche (meme coin/token security, Solana SPL, Token-2022, DEX LP attacks) with distinct triggers in third-person voice, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: shuvonsec/claude-bug-bounty
Path: skills/meme-coin-audit/SKILL.md
Commit: 2009594

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.