Update to Lukka Digital Assets Intel

{
  "description": "Wallet analysis with AML risk, balance, assets, and transaction preview",
  "included_files": [],
  "name": "wallet-scan",
  "skill_md_contents": "---\nname: wallet-scan\ndescription: \"Wallet analysis with AML risk, balance, assets, and transaction preview\"\n---\n\n## OpenAI connection notes\n\nTool identifiers below are raw operation names. The host may add a namespace;\nuse the matching advertised Global MCP tool. Resolve `<resolved-package-root>`\nto this plugin's installed directory before using paths. Workflow names identify\npackaged skills; they are not literal Claude slash commands.\n\nOriginal procedure tool scope: `AML___generateAmlEnhancedReport`, `AML___generateAmlScoringReport`, `AML___generateAmlSimplifiedReport`, `AML___generateAmlStandardReport`, `UDA___get_address_assets`, `UDA___get_address_balance`, `UDA___get_address_transactions`.\n\n# wallet-scan workflow\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool details.\n\n## Usage\n\nwallet-scan workflow <user input>\n\nParse <user input> for address and blockchain symbol. Remember: Lukka-UDA uses lowercase (`eth`, `btc`), Lukka-AML uses uppercase (`ETH`, `BTC`).\n\n> **UDA vs AML chain coverage differ.** UDA address/tx endpoints (steps 1-3) serve: btc, bch, ltc, doge, dash, eth, avax, xrp, xlm, near, dot (+ vet balance-only). `sol`, `trx`, `matic`, `ada` return \"Unsupported crypto symbol\" on UDA even though AML (step 4) DOES score them. On a chain where AML scores but UDA address/tx endpoints do not serve (e.g. sol, trx), skip steps 1-3, note \"on-chain data for {chain} is provided via the AML report\", and run the AML scoring/standard/enhanced report only. See `skills/lukka-data-routing/references/uda.md` for the full per-endpoint matrix.\n\n## Flow (context-safe sequence)\n\n1. **Balance**: `UDA___get_address_balance({ blockchain: \"{lc}\", address: \"{address}\" })` \n2. **Assets**: `UDA___get_address_assets({ blockchain: \"{lc}\", address: \"{address}\" })` \n3. **Transaction preview** (always cap at 100 to stay within context):\n   `UDA___get_address_transactions({ blockchain: \"{lc}\", address: \"{address}\", verbose: \"1\", limit: 100, get_newest: \"1\" })` \n4. **Light AML (default)**: `AML___generateAmlScoringReport({ address: \"{address}\", address_type: \"{UC}\" })` \n   - **Parameter is `address_type`** (e.g. `\"ETH\"`, `\"BTC\"`), NOT `blockchain`. Same for `generateAmlStandardReport` / `Enhanced`.\n   - Returns C-Score (0-100) + risk_level (LOW/MEDIUM/HIGH) + top factors. Fits in context.\n   - To reuse an existing report: `--reuse-report {report_id}` skips re-scoring\n\n## On request: deeper analysis\n\n### Full transaction scan (>100 txs)\n\nBefore calling with large limit, deploy the processor so the raw response never enters context. See `large-data-processing` skill.\n\n```\ncp \"<resolved-package-root>/skills/large-data-processing/references/process_transactions.py\" /tmp/\n# Call MCP with limit:1000, save raw JSON to /tmp/txs.json\npython3 /tmp/process_transactions.py /tmp/txs.json --stats --top-senders 10 --dust-threshold 0.0001\n# Then selectively decode flagged hashes via Get_transaction_for_txhash\n```\n\n### Full AML report (325 KB+ - mandatory processor pipe)\n\n```\ncp \"<resolved-package-root>/skills/large-data-processing/references/process_aml_report.py\" /tmp/\n# Call AML___generateAmlStandardReport, save raw to /tmp/aml_report.json\npython3 /tmp/process_aml_report.py /tmp/aml_report.json\n```\n\nFor maximum depth: `AML___generateAmlEnhancedReport` (500 KB+) - same processor workflow.\n\n### Counterparty exposure (on demand)\n\n> **Note**: for counterparty exposure data, use `generateAmlStandardReport` (with processor pipe).\n\n> **Report tier availability**: Use SCORING for a light check on any chain. For a full or deep report use STANDARD/ENHANCED on these 30 chains: `ADA, AVAX, BCH, BSV, BTC, CC, DASH, DOGE, DOT, DOT_AH, ETC, ETH, FIL, ICP, IOTA_MAINNET, IOTAEVM, LTC, MATIC, NEAR, NEO, RSK, SOL, TRX, VET, XDAI, XLM, XRP, XTZ, ZEC, ZKS`. SIMPLIFIED covers the additional 80 chains: `ALGO, APT, ARBITRUM, ATOM, AZERO, BASE, BNB, BSC, CANTO, CELO, CHZ, CKB, COTI, CRO, CRONOS, DCR, DGB, DOGECHAIN, ECS, EGLD, EOS, ETHW, EVMOS, FET, FLOW, FTM, FUSE, GLMR, GRAM, HASH, HBAR, HT, IMX, IOTA, IOTX, KAVA, KCS, KDA, KLAY, KSM, LINEA, LSK, LUNA, LUNC, MINA, MNT, MOVR, NEO3, ONE, ONT, OP, PALM, PLS, QTUM, REEF, RON, ROOT, RUNE, SDN, SEI, SMR, STX, SUI, TAO, THETA, TLOS, TON, VIC, WAN, WAVES, WAX, XDC, XEC, XEM, XNO, XVG, XYM, ZEN, ZIL, ZKEVM`.\n> **Do NOT call `generateAmlStandardReport` or `generateAmlEnhancedReport` without the processor** - responses exceed context window.\n\n### Smart contract interaction detection\n\nWhen UDA `get_address_transactions` returns `value=0` for a transaction with `input != '0x'`, this indicates a smart contract interaction (token transfer/swap). For decoded token amounts, follow up with `Get_transaction_for_txhash` using the tx_hash.\n\n## Output\n\n### Wallet Scan: {address}\n\n**Compliance (AML Scoring)**\n- Risk Level: {risk_level} (LOW/MEDIUM/HIGH from `cscore_section.risk_level`)\n- C-Score: {cscore}/100 (from `cscore_section.cscore`)\n- Top Risk Factors: {list from `factors`}\n\n**Holdings**\n- Native Balance: {amount} {symbol}\n- Tokens: {count} contracts (by order of last interaction)\n\n| # | Token Contract | Last Seen |\n|---|---------------|-----------|\n\n> USD values are not resolved by default (requires N*3 calls per token). Use `--full-enrichment` to resolve balances and prices for each token.\n\n**Activity Preview** (last 100 txs)\n- Total shown: {count}\n- Date range: {first} to {last}\n- Peak day: {date} ({count} txs)\n\n**Heuristic Flags** (model analysis of AML factors + tx preview - not authoritative)\n- {pattern description, e.g. \"5 dust transactions from addresses matching mixer pattern\"}\n- Based on: AML risk factors + transaction preview pattern matching\n- Disclaimer: heuristic only - for authoritative flagging use Standard/Enhanced AML report\n\n**Next steps** (offer to user):\n- `--full-enrichment`: resolve USD values per token (high call volume)\n- Full transaction scan (deploy processor)\n- Standard or Enhanced AML report (deploy processor)\n- Tx flow graph\n"
}