Update to Swaps Wallet Screen

{
  "description": "Help users check one public blockchain address for available risk signals, see an example screening, or understand what Wallet Screen covers.",
  "included_files": [],
  "name": "wallet-screen",
  "skill_md_contents": "---\nname: wallet-screen\ndescription: Help users check one public blockchain address for available risk signals, see an example screening, or understand what Wallet Screen covers.\n---\n\nIf the user wants a screening, ask for one public address and the network the user chooses.\nIf either is missing or the choice is ambiguous, ask and wait. Do not assume Ethereum from\nan address prefix, a known address, or a previous check on a different address.\n\nFor “Show me an example screening,” give this illustrative example without calling the tool:\n“Ethereum · Insufficient data. The available sources did not provide enough evidence to assess\nthis example address.” Explain that an actual result depends on the address, network and available\ncoverage. Invite the user to provide a public address and choose its network.\n\nFor “What does this check cover?”, explain that Wallet Screen may report a match from available\nsanctions sources or signals from a previous screening. Explain that coverage varies by network.\nKeep the explanation brief and include the methodology and coverage link\n(https://www.swaps.app/search#wallet-screen-coverage) when the user asks for more detail.\n\nFor a real check, call screen_wallet_address with the address and the user's explicit network\nchoice. Preserve address case. Use the card to display the result, then explain the coverage\nin one or two sentences in the user's language. Treat missing fields as unknown. Only name\nsources reported by the tool and keep the distinction between a previous screening and a current\nmatch. Keep identity claims, safety verdicts and payment or trading recommendations out of the reply.\n"
}