CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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-organized, action-oriented audit playbook with concrete grep/scanner/CLI commands and clear kill-signal checkpoints. Its main gaps are the incomplete Foundry POC template and reference files that are signaled but absent from the bundle.

Suggestions

Complete the Foundry POC template — replace '// ... buy tokens on Uniswap' and '// Assert token price crashed' placeholders with executable swap/assert calls so the examples are copy-paste ready.

Add an explicit feedback loop for findings: e.g. when a 'Kill if:' criterion fails, state the next action (flag severity, write finding to report, escalate to manual on-chain verification) to raise workflow clarity.

Either ship the referenced web3/*.md files in the bundle or note in SKILL.md that they are external/optional, so the one-level-deep references resolve to real content.

DimensionReasoningScore

Conciseness

Mostly lean — bulleted kill signals, copy-paste grep patterns, and terse 'Kill if:' criteria that assume Claude's competence; the Foundry POC template carries placeholder comments ('// ... buy tokens on Uniswap', '// Assert token price crashed') that could be trimmed or completed. Not a 5 because the POC skeleton pads the token budget with non-executable filler; not a 3 because everything else earns its place.

4 / 5

Actionability

Provides concrete executable grep commands, scanner invocations, and Solana CLI checks that are copy-paste ready, but the Foundry POC template is a partial skeleton with '// ...' placeholders rather than fully executable code. Not a 5 due to those gaps; not a 3 because the majority of guidance is concrete and runnable.

4 / 5

Workflow Clarity

Clear sequence — pre-dive kill signals → bug classes (each with a 'Kill if:' checkpoint) → automated scanner → POC → on-chain checks → references — with validation criteria and an explicit 'Scanner does NOT check' cross-check list. Not a 5 because there is no explicit error-recovery/feedback loop for findings that fail the kill criteria.

4 / 5

Progressive Disclosure

Well-sectioned overview with three clearly signaled one-level-deep reference files at the end, each with a one-line description. Not a 5 because the referenced files (web3/10-meme-coin-bugs.md, web3/11-solana-token-audit.md, web3/12-dex-lp-attacks.md) are not present in the bundle, so navigation cannot be fully verified.

4 / 5

Total

16

/

20

Passed

Description

100%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 is comprehensive, concrete, and explicitly states both capabilities and use-when triggers in third person. It is a strong, low-conflict trigger description with natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities across EVM and Solana — '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', 'token_scanner.py automation' — comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both 'what' (detailed capability list) and 'when' via the concrete 'Use for any token audit, rug pull assessment, meme coin security review, or pre-investment due diligence' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would actually say — 'token audit', 'rug pull assessment', 'meme coin security review', 'pre-investment due diligence' — plus concrete platform/tool names (pump.fun, Raydium, Jupiter, token_scanner.py) as synonyms and specifics.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (meme coin / token security auditing) with distinct triggers; the specificity of Token-2022, SPL authorities, and DEX/LP attacks minimizes overlap with generic code-audit skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shuvonsec/claude-bug-bounty
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.