Update to CipherOwl

{
  "description": "Screen a cryptocurrency address for compliance risk with CipherOwl and explain any findings. Use when someone asks whether an address is risky, sanctioned, or safe to transact with, or why an address was flagged.",
  "included_files": [],
  "name": "screen-address",
  "skill_md_contents": "---\nname: screen-address\ndescription: Screen a cryptocurrency address for compliance risk with CipherOwl and explain any findings. Use when someone asks whether an address is risky, sanctioned, or safe to transact with, or why an address was flagged.\n---\n\n# Screen a cryptocurrency address\n\nPick the CipherOwl tool by what the user asks:\n\n- Whether an address is risky, sanctioned, or safe to transact with: call\n  `screen` with the address. Pass the chain only when the user names it;\n  CipherOwl detects the chain from the address otherwise.\n- Why an address is flagged, or the details behind a finding: call\n  `reason_risk` for the address. It does not need a `screen` call first.\n  Explain each reason: the risk category, whether funds were sent or\n  received, how many hops away the source is, and the value and share of the\n  exposure.\n\nWhen you answer:\n\n- Report what CipherOwl found under the organization's risk configuration.\n  A clean result means CipherOwl found no risk indicators; never promise that\n  an address is safe.\n- After a `screen` result that found risk, offer to explain the reasons,\n  unless the user already asked why or for the details; then call\n  `reason_risk` right away.\n- If a result carries a `plan` note, tell the user what it says, so a limited\n  result is not presented as complete.\n- If a result carries a link to the address on CipherOwl, include it.\n- CipherOwl returns risk signals, not personal identities. Do not try to\n  identify the people behind an address.\n- These tools are read-only. They cannot send, freeze, or report funds.\n"
}