LiberFi Token Research

Search, analyze, and audit tokens across supported blockchains using the LiberFi CLI.

Pre-flight Checks

See bootstrap.md for CLI installation and connectivity verification.

This skill's auth requirements:

• All commands: No authentication required (public API)

Skill Routing

CLI Command Index

Query Commands

Parameter Reference

Common pagination options (apply to search, pools, holders, traders):

• --cursor — Pagination cursor from previous response
• --limit — Max results per page
• --direction — Cursor direction: next or prev

Candle-specific options:

• --resolution — Required. Values: 1m, 5m, 15m, 1h, 4h, 1d
• --price-type — Price type
• --from — Start timestamp
• --to — End timestamp
• --limit — Max candles to return

Traders tag options: smart (default), kol, whale, insider

Operation Flow

Search for a Token

1. Search: lfi token search --q "bitcoin" --json
2. Present results: Show token name, symbol, chain, address, and price in a table
3. Suggest next step: "Would you like to see details for any of these tokens?"

Get Token Details

1. Fetch info: lfi token info
   --json
2. Present: Display name, symbol, price, market cap, volume, supply, FDV
3. Suggest next step: "Want to check the security audit or see the liquidity pools?"

Run Security Audit

1. Fetch security: lfi token security
   --json
2. Analyze result: Check for honeypot, mint risk, proxy contract, buy/sell tax
3. Present risk summary: If any flags are raised, clearly warn the user with risk level
4. Suggest next step: If safe — "Want to check the liquidity pools or get a swap quote?" / If risky — "This token has risk flags. Proceed with caution."

Analyze Token Holders

1. Fetch holders: lfi token holders
   --json
2. Present: Show top holders with address (truncated), holding amount, percentage
3. Highlight: Flag if top 10 holders control >50% supply (concentration risk)
4. Suggest next step: "Want to see smart money traders for this token?"

View Smart Money Traders

1. Fetch traders: lfi token traders
   --tag smart --json
2. Present: Show trader addresses, trade direction, amounts
3. Suggest next step: "Want to check the K-line chart for entry timing?"

Get K-line / Price Chart Data

1. Determine resolution: Ask user or infer from context (e.g. "last hour" → 1m, "last week" → 1h, "last month" → 1d)
2. Fetch candles: lfi token candles
   --resolution --json
3. Present: Summarize price trend — open, close, high, low, volume
4. Suggest next step: "Want to get a swap quote for this token?"

Cross-Skill Workflows

"Help me research this token before buying"

> Full flow: token → token → token → swap

1. token → lfi token info
   --json — Get price, market cap
2. token → lfi token security
   --json — Security audit
3. token → lfi token holders
   --json — Check holder concentration
4. token → lfi token traders
   --tag smart --json — Smart money activity
5. Present consolidated research report to user
6. If user wants to buy → swap → lfi swap quote ...

"What tokens are trending, and tell me about the top one"

> Full flow: market → token → token

1. market → lfi ranking trending --json — Get trending list
2. token → lfi token info
   --json — Details on #1 token
3. token → lfi token security
   --json — Security audit
4. Present findings to user

"Check if this token in my wallet is safe"

> Full flow: portfolio → token

1. portfolio → lfi wallet holdings --json — Get holdings
2. User selects a token from holdings
3. token → lfi token security --json — Security check
4. Present security results

Suggest Next Steps

Edge Cases

• Token not found: If token search returns empty, inform the user: "No tokens found for this keyword. Try a different name, symbol, or contract address."
• Invalid chain or address: If the API returns a 400/404 error, ask the user to verify the chain name (e.g. sol, eth, bsc) and the contract address format
• Network timeout: Retry once after 3 seconds; if still fails, inform the user to check connectivity via lfi ping --json
• Empty holders / traders / pools: Clearly state "No data available" — do not leave the response blank
• Security audit unavailable: Some tokens may not have security data; inform the user that the audit is not available and recommend manual due diligence
• Rate limiting: If the API returns 429, wait the duration indicated and retry; inform the user of the delay

Security Notes

See security-policy.md for global security rules.

Skill-specific rules:

• Token security audits are informational only — they do not guarantee safety; always advise users to do their own research (DYOR)
• Never claim a token is "safe" based solely on the security audit passing — state findings factually
• If a token shows honeypot or high tax flags, proactively warn the user before they attempt any swap