| name | token-research |
| description | Comprehensive token research for EVM chains (Base, ETH, Arbitrum) and Solana. Use this skill when you want to research crypto tokens, deep-dive projects or monitor tokens. |
This skill is a comprehensive token research for EVM chains (Base, ETH, Arbitrum) and Solana. Two modes: deep_research and shallow_dive.
MANDATORY: Owner alert escalation
Verdict actions:
- SKIP / AVOID → do not interrupt owner; optionally log internally.
- WATCH 🟡 → send owner a private Telegram DM with concise analysis and append to the monthly watchlist. Do not phone-call by default.
- APE 🟢 / BUY 🟢 → urgent: send owner a private Telegram DM, append to watchlist, and immediately call owner. NO EXCEPTIONS.
For APE/BUY calls:
- Prefer AgentOS/agents-infra voice calling when configured:
agentos phone call --id ID --to +... --tts "APE alert: $TICKER at $MCAPk mcap, $VOLk volume. [1-line reason]"
- If AgentOS is installed but not configured, quickly inspect for usable phone IDs/owner number before giving up:
agentos phone --help, ~/.agentos/config.json, ~/.agentos/logs/, and any known local alert scripts. AgentOS v0.7.9 may throw an Ink Raw mode is not supported error in non-interactive terminals; do not loop on that failure.
- If the legacy helper exists, fallback:
~/workspace/scripts/ape-call.sh "APE alert: $TICKER at $MCAPk mcap, $VOLk volume. [1-line reason]"
- Send Telegram DM to your owner with full analysis.
- If no actual phone-call route is discoverable, send an urgent Telegram voice alert as last-resort escalation: generate TTS with the APE/BUY reason and send it as
[[audio_as_voice]] media. State in the final that phone calling was attempted/unavailable and voice-Telegram fallback was sent.
DO NOT: say "if owner were awake", hesitate because it is late, or process APE/BUY alerts without attempting escalation.
MANDATORY: ALWAYS RESEARCH ON X/TWITTER — SKIP PURE MEMES
For EVERY token, before giving a verdict, check X/Twitter:
- Search
$TICKER and project name (Latest + Top)
- Check the project's Twitter account: tweets, bio, what they're building
- Look for a PRODUCT (website, GitHub, app, protocol)
If the product is real, CALL your owner regardless of chart action. Bad charts on real products = buying opportunity, not a skip.
Pure memes = AVOID by default. Be strict: do not label every high-volume meme as WATCH. A pure meme should only become WATCH when it has unusually strong organic traction (not mostly caller/bot posts), clear source virality, and sustained volume/liquidity; otherwise SKIP/AVOID. APE/BUY should be reserved for real products/builders or exceptional meme breakouts with overwhelming organic adoption.
Z-specific scoring corrections / pitfalls
- Bundle risk is a first-class filter. Before WATCH/APE, check launch quality: bundled buys, suspicious connected early wallets, dev/top-holder concentration, sniper control, weak/real liquidity, and whether early buy flow looks organic. High bundle/manipulation risk usually means SKIP even when chart/volume looks good.
- Generic cult/name memes are SKIP. A token whose thesis is only “cult,” name aesthetics, an X Community, a meme site, or an NFT-generator-style page is not WATCH. Example pattern:
$soldier / soldiercult.com → SKIP unless there is a genuinely interesting product, viral source moment, or unusual organic traction behind it.
- Do not auto-reject X Community links, but research why they exist. X Communities can be bullish when they formed around a real viral moment and active holders are waiting for a dev/project claim. Check community activity/source virality/volume before deciding. Community-only + generic meme/cult = SKIP.
- Low mcap is not a reason to skip. Research every token in a batch, including tiny caps; early low-cap entries can be the best opportunities.
- Product presence alone is not enough. Generic AI-wrapper slop, low-effort/vibecoded apps, poor UX/branding, boring products, or undifferentiated “we have a site/app” launches are SKIP even if technically a product exists. Example pattern:
$FATCATS-style low-quality/vibecoded product → SKIP, not WATCH/APE.
- For product-token launches, token utility/users/traction are not hard filters. If the product is genuinely cool, novel, polished, or degen-shareable, it can be WATCH/APE even before users and even if token utility is weak/pointless. Score product quality/novelty/wow factor first; then use social/holders/chart as sizing/risk inputs.
- When evaluating product quality, actually open/render the app when possible. HTML metadata is not enough. Use a browser or headless screenshot + vision analysis to distinguish real interactive product (e.g. playable-looking game UI, wallet flows, token-gated mechanics) from generic landing/vibecoded slop.
Reports & Watchlist
Integration reference: see references/onchain-alerts-hermes-integration.md for wiring onchain scanner alerts into Hermes with SKIP/WATCH/APE/BUY action routing.
Reports: reports/YYYY-MM-DD/[report-name].md
Watchlist: watchlists/YYYY-MM/watchlist.md
User-facing result discipline
- If the user asked for token research, deliver the verdict in chat after the research is complete. Appending to a watchlist is not enough.
- Give the action label first (
SKIP, WATCH, APE, BUY), then the core metrics, catalyst, social proof, and risks.
- If another setup/debug task is also active, do not let it bury the research answer; send the token verdict before continuing infrastructure work.
Watchlist Rules
- After any research, if token has real product/team or unique narrative → append to watchlist
- Tiers: Tier 1 (strongest), Tier 2 (good signal, higher risk), Tier 3 (speculative)
- Each entry: token, chain, CA, entry MC, current MC, catalyst, status (🟢🟡🔴)
- APPEND only — never overwrite. Update status when new data comes in.
- Before writing a watchlist entry, read the exact monthly file path (
watchlists/YYYY-MM/watchlist.md) if it exists. Do not rely only on search_files/glob discovery: if the file is missing, create the directory/file only after checking the exact path; if a sibling-write warning appears, immediately read the file and re-append without clobbering.
- When appending/patching watchlists from
read_file output, remember the tool displays line-number prefixes (e.g. 34|) that are not file content. Do not copy those prefixes into old_string/new_string; patch only the raw markdown table row, then re-read the tail to verify no line-number artifacts were inserted.
- When a token is based on a viral meme/narrative, scan the existing monthly watchlist for sibling/competing CAs on the same meme (e.g. another ticker/name already listed). Competing CAs reduce conviction and should be included in the risk notes; usually this keeps a pure meme at WATCH instead of APE/BUY unless one CA has overwhelming organic adoption.
- If the monthly watchlist file does not exist, create it at
watchlists/YYYY-MM/watchlist.md with a simple markdown table, then append the WATCH/APE/BUY entry.
- For WATCH DMs, include: verdict, token, chain, contract, DexScreener URL, key metrics, X/community findings, risks, and why watchlist-worthy. Explicitly do not call for WATCH.
Prerequisites
source ~/.openclaw/secrets/twitterapi.env
APIs
| API | Base URL | Auth | Use |
|---|
| DexScreener | https://api.dexscreener.com | None | Price, liquidity, volume, pairs |
| GoPlus | https://api.gopluslabs.io | None | Security audit, honeypot, ownership |
| Basescan | https://api.basescan.org/api | Optional | Holders, contract info |
| Etherscan | https://api.etherscan.org/api | Optional | Holders, contract info |
| TwitterAPI | https://api.twitterapi.io | $TWITTERAPI_KEY | Social research, sentiment |
Chain IDs: Ethereum: 1 — Base: 8453 — BSC: 56 — Solana: solana
API/tooling pitfalls
Viral-source meme evaluation
- Do not treat a high-follower source tweet as project endorsement. For memes spawned by public figures, government accounts, KOLs, or news moments, verify whether the source account posted the token/CA or merely used a word/image that became the meme. If no CA/token mention exists, label it as viral narrative only, not team/dev confirmation.
- Check ticker collisions. Generic tickers like
$CARDS can belong to established projects and pollute Top search results. Separate CA-specific/latest tweets from legacy ticker discourse before scoring social proof.
- Pure meme can still be WATCH when volume is exceptional. If there is no product/team but the source moment is verifiably viral and early volume/liquidity are unusually high, classify WATCH rather than SKIP; reserve APE/BUY for real product/team confirmation or extreme conviction.
- Case reference:
references/viral-source-meme-evaluation.md captures the CARDS/Iran-consulate pattern and how to score it.
- Case reference:
references/kospi6900-viral-source-pattern.md captures the KOSPI6900/Jukan pattern: viral finance meme + exceptional early volume, but no CA endorsement and multiple competing CAs → WATCH, not APE/BUY.
- Case reference:
references/bitgans-ai-art-product-token-evaluation.md captures the bitGAN pattern: older real AI-art/NFT project footprint + exact-CA project profile + concrete token/product mechanics → WATCH when founder/team endorsement and broader organic X proof remain unverified.
- Case reference:
references/roman-ai-founder-product-pattern.md captures the ROMAN pattern: founder/source account explicitly posts the exact CA + real live product/install surfaces + acceptable token safety at microcap → can justify APE/BUY even when TwitterAPI Latest/Top is 402-blocked, as long as risks are explicit.
- Case reference:
references/oneira-ai-product-builder-pattern.md captures the Oneira pattern: an alert may look like an X-Community-only meme, but if Pump/X fallbacks reveal a real product account plus a verified builder profile carrying the exact CA, microcap + strong early flow can justify APE despite TwitterAPI 402; use Jina-rendered X/fxtwitter pages when direct X/fxtwitter requests hang.
- Case reference:
references/detour-elizaos-builder-product-pattern.md captures the DTOUR pattern: a real, public, downloadable/buildable elizaOS-style agent product plus a verified builder profile carrying the exact CA can justify APE at microcap even when the project mascot X is tiny and TwitterAPI Latest/Top is 402-blocked; verify via site, GitHub/API/raw README, Pump/Dex metadata, and builder-owned X fallbacks.
- Case reference:
references/denali-charity-viral-source-pattern.md captures the DENALI pattern: wholesome official-source/charity meme + exceptional early flow → WATCH, not APE/BUY, when the official source did not mention the CA/token and charity proof is unverified.
DEEP RESEARCH
Phase 1: Token Fundamentals + Launch Quality
curl -s "https://api.dexscreener.com/latest/dex/tokens/CHAIN/TOKEN_ADDRESS"
curl -s "https://api.gopluslabs.io/api/v1/token_security/CHAIN_ID?contract_addresses=TOKEN_ADDRESS"
Before promoting to WATCH/APE, inspect bundle/launch quality signals: dev/top-holder concentration, suspicious early wallets, sniper-controlled supply, weak LP/provider distribution, LP lock, and whether buy flow looks organic or coordinated. Treat bundle risk as a major verdict input, not a minor footnote.
Phase 2: X/Twitter Research (PRIMARY / most important phase)
X is the main research surface for token thesis. Dex/chart/security stats are secondary context, not the thesis. Before assigning WATCH/APE, extract real-info from X: what the project is building, how long the account/team has been building, founder/team credibility, exact CA/token endorsement from official accounts, organic discussion quality, and whether the idea is genuinely unique. Do not substitute random stats for thesis.
curl -s "https://api.twitterapi.io/twitter/tweet/advanced_search?query=\$TICKER&queryType=Latest" -H "X-API-Key: $TWITTERAPI_KEY"
curl -s "https://api.twitterapi.io/twitter/tweet/advanced_search?query=TOKEN_ADDRESS&queryType=Latest" -H "X-API-Key: $TWITTERAPI_KEY"
curl -s "https://api.twitterapi.io/twitter/user/info?userName=PROJECT_HANDLE" -H "X-API-Key: $TWITTERAPI_KEY"
curl -s "https://api.twitterapi.io/twitter/user/last_tweets?userName=PROJECT_HANDLE" -H "X-API-Key: $TWITTERAPI_KEY"
curl -s "https://api.twitterapi.io/twitter/tweet/advanced_search?query=\$TICKER%20min_faves:50&queryType=Top" -H "X-API-Key: $TWITTERAPI_KEY"
curl -s "https://api.twitterapi.io/twitter/user/info?userName=FOUNDER_HANDLE" -H "X-API-Key: $TWITTERAPI_KEY"
⚠️ VERIFY dev claims from THEIR OWN ACCOUNT. Never trust holder/community claims about dev endorsement. Search from:DEV_HANDLE for mentions of the token. If dev hasn't posted about it → flag as unconfirmed.
Phase 3: Web Research
Search for: project website, team/founder background, news/partnerships, Reddit sentiment.
Phase 4: Narrative Assessment
Narrative Score (add to every report):
- 🔥 Strong — Novel concept, viral potential, clear catalyst
- 🟡 Moderate — Decent angle but not unique, or good concept with weak execution
- 🧊 Weak/None — Generic, repetitive, no story → likely dumps to zero
Key questions: Is it novel? Would someone share it unprompted? Is the market tired of this category? Why hold beyond a flip?
Smart money wallet count + narrative quality are better predictors than contract safety.
Phase 5: Risk Synthesis
Combine: narrative quality, smart money interest, contract security, holder concentration, team transparency, social proof (organic vs bots), liquidity depth, buy/sell ratio.
SHALLOW DIVE
Run only: DexScreener + GoPlus + one Twitter search + basic web search.
Batch Research (5+ Tokens)
- Spawn parallel sub-agents for concurrent research
- After filtering, auto deep dive top 1-3 tokens without waiting for user to ask
- Save report to
reports/YYYY-MM-DD/[N]-token-analysis.md
- Auto-add top picks to monthly watchlist
