How to talk to Claude
The golden rule: speak normally. Claude understands the intent behind your sentence and automatically launches the right type of search himself. You don’t need to know the tool names, or write complicated prompts.
The magic phrases
Here are the most useful requests, and what Claude does behind the scenes:
| You write | Claude does |
|---|---|
| (you paste a CA) “analyze this token” | Full due diligence: price, market cap, creator history, bundles, verdict |
| “the dev of this token is funded by an exchange, is it over?” | No! It notes the exact amount, digs through the exchange’s exits with a ultra-fine band, and looks for sibling wallets. It’s the start of the method, never a dead end |
| “find me a rugger to snipe” | Launches automatic discovery and only suggests targets that meet the criteria — if there’s nothing good, it tells you “nothing good,” not a consolation prize |
| “is this wallet copytradable?” | Qualification on the entry geometry : start from Block 0, regularity, cadence — never on the wallet’s PnL |
| “what TP should I set on this wallet?” | Analyzes the wallet’s last 30-50 buys, builds the distribution of runs, and suggests levels with figures to back it up |
| “how is my portfolio doing?” | Balances, open positions, PnL, recent trades — in one response |
| “is it the right time to snipe?” | Checks current landing conditions: buy success rate, congestion, tip level |
| “what did my ruggers do this week?” | The 7-day feed from your trackers |
| “why did this trade lose?” | Takes back the position and your setup, and explains what happened using the method — without rewriting history |
| “add this rugger and configure it” | Qualifies it first, then suggests a config translated from THIS rugger’s playbook, and applies it after your confirmation |
The right habits
Give the CA, not the name. “Analyze PEPE2” isn’t enough — there are a hundred tokens with that name. Always paste the contract address.
Ask it WHY. Claude doesn’t just give a verdict — it can explain every number. If you don’t understand a term or a conclusion, ask “explain it to me like I’m 10 years old.” It’s the best teacher of the method you’ll ever have at hand; it knows the whole course.
Let it finish its research. A real funding analysis can take several steps (it paginates, cross-checks, verifies). It’s normal to see it chain several searches before answering.
Distrust yourself, not him. If Claude tells you “the sample is too small, I can’t validate this TP,” that’s a real answer — not a bug. It’s forbidden to invent numbers. An honest “I don’t know” is better than a bogus figure.
What Claude will sometimes tell you (and that’s a good sign)
- “ This wallet is disposable, don’t track it ” — it refuses to make you follow an address that will never be used again
- “ The sample only covers 12 tokens, I need 20-30 over 72h ” — it refuses to validate stats on too little data
- “ This isn’t a tracker, it’s a hub ” — it distinguishes real targets from shared infrastructure
- “ Nothing passes the criteria today ” — discovery rejects rather than soothes
A copilot that knows how to say no is exactly what you want by your side.
💡 Tip : you can also ask it pure training questions, without analyzing anything: “what’s a bundle?”, “why does the floor protect?”, “explain the exchange method to me.” It knows the whole curriculum.