[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7212E76XTWJWS0HFCC8SMFX":3,"skill-same:01M7212E76XTWJWS0HFCC8SMFX":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7212E76XTWJWS0HFCC8SMFX","risk-exposure-screening-concepts",null,"Educational map of risk exposure screening-typical risk indicator taxonomies, exposure value and percentage, address-level vs transaction-level engines, and common template families (entity label, multi-hop interaction, blacklist). Use when the user asks how commercial screening tools reason about labeled addresses, tainted flows, or deposit vs withdrawal checks-not for legal sanctions determinations or substituting a vendor’s live rules.","zkos-labs\u002Fbastion","zkos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263369112?v=4","01M720WZH0GD7FAKBP5PSGF4TG","ZKOS Labs","01M720WZHP9JV5NZVQCHA6XJ3M",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frisk-exposure-screening-concepts\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: risk-exposure-screening-concepts\ndescription: Educational map of risk exposure screening-typical risk indicator taxonomies, exposure value and percentage, address-level vs transaction-level engines, and common template families (entity label, multi-hop interaction, blacklist). Use when the user asks how commercial screening tools reason about labeled addresses, tainted flows, or deposit vs withdrawal checks-not for legal sanctions determinations or substituting a vendor’s live rules.\n---\n\n# Risk exposure screening (concepts)\n\n**Educational reference only.** Labels and scores from analytics or compliance tools are **not** legal findings. Verify **primary** sanctions lists and jurisdictional requirements with qualified teams. Pair with **crypto-investigation-compliance** and **blockchain-analytics-operations**.\n\n## Risk Exposure Engine (idea)\n\nA **risk exposure engine** combines a **database of address or entity labels** with **on-chain interaction graphs** to estimate whether a screened **address** or **transaction** is associated with **known risk categories**. Implementation details differ by product; confirm hop counts, thresholds, and asset scope in your provider’s documentation (see **phalcon-compliance-documentation** where relevant).\n\n## Risk indicators (typical taxonomy)\n\nRisk indicators are **categories** assigned to addresses or entities. Names vary by vendor; the table below lists **common** families used in industry documentation.\n\n| Risk indicator | Description |\n|----------------|-------------|\n| Sanctioned | Associated with entities on official sanctions lists (for example OFAC SDN), where applicable. |\n| Terrorism financing | Associated with designated terrorist organizations or financing of terrorism. |\n| Human trafficking | Associated with trafficking-related organizations or flows. |\n| Drug trafficking | Associated with illicit production, transport, or distribution of controlled substances. |\n| Attack | Related to exploit actors, attacker contracts, or associated fund movements. |\n| Scam | Fraudulent schemes: phishing, Ponzi, honeypots, pig-butchering, etc. |\n| Ransomware | Controlled by ransomware operators or used to pay ransom. |\n| Child sexual abuse material (CSAM) facilitation | Facilitating payments for platforms distributing CSAM. |\n| Money laundering | Suspected laundering of illicit proceeds. |\n| Mixing | Mixer or privacy services that obscure trails. |\n| Darknet market | Operators of darknet markets. |\n| Darknet business | Other illicit darknet commerce (for example weapons, identity theft). |\n| Frozen \u002F contract blacklist | Blacklisted by major contracts or issuers (for example stablecoin freezes). |\n| Gambling | Online gambling service addresses. |\n| No-KYC exchange | Virtual asset service providers with weak KYC, per provider policy. |\n| FATF high-risk jurisdiction | Entities tied to jurisdictions on FATF “black” lists (as used by the data provider). |\n| FATF grey-list jurisdiction | Entities tied to FATF grey-list jurisdictions (as used by the data provider). |\n\n## Exposure metrics\n\n| Term | Meaning |\n|------|---------|\n| **Exposure value** | Total USD value (per provider’s pricing source) of assets that **originated from** or **interacted with** a specified risk-labeled source, under the engine’s rules. |\n| **Exposure percentage** | Share of **tainted** value relative to total **inflow** or **outflow** value for the screened address, under the configured window and rules. |\n\nInterpretation is **policy-dependent**-same raw hops can score differently by direction, hop depth, and minimum amounts.\n\n## Address-level screening (common templates)\n\nMany platforms expose three **template** families for **addresses**:\n\n1. **Entity \u002F direct label risk** - The screened address **itself** carries a risk label (for example sanctioned or scam).  \n   *Illustrative:* an address is flagged because it matches an OFAC-listed identifier in the provider’s dataset.\n\n2. **Interaction risk** - Traces **incoming or outgoing** value across **multiple hops**. If any counterparty in the path carries a risk label, the engine may flag exposure **subject to** direction, hop limits, amount thresholds, and decay rules.\n\n3. **Blacklist interaction** - Detects interaction with addresses on a **customer-defined** or **tenant** blacklist (policy-specific).\n\n## Transaction-level screening (common templates)\n\nFor a **single transaction**, engines often provide:\n\n1. **Participant risk** - Whether **addresses participating** in the transaction carry configured risk indicators.  \n   **Deposit vs withdrawal (typical convention):** for a directional screen, **deposit** flows may screen only the **from** side, and **withdrawal** flows only the **to** side-confirm in product docs.\n\n2. **Interaction \u002F flow risk** - Traces fund **provenance** or **destination** of the transaction’s value to detect prior exposure (for example receiving from a phishing-labeled cluster). Deposit\u002Fwithdrawal modes may restrict whether **source** or **destination** tracing applies.\n\n3. **Blacklist interaction** - Whether the transaction touches **blacklisted** addresses per policy.\n\n## Guardrails\n\n- **Do not** treat a commercial **label** as a court finding or automatic **sanctions** violation.  \n- **Do not** assist with **evading** screening, mixers for illicit purpose, or **circumventing** law enforcement processes.  \n- **Separate** on-chain **facts** from **vendor scoring**-document both when reporting.\n\n## See also\n\n- **behavioral-risk-screening-concepts** - volume, velocity, and transit-style **behavior** heuristics (complements label-based exposure).\n\n**Goal:** give investigators a **shared vocabulary** for exposure-style screening without binding any specific **product** behavior or **legal** outcome.\n","# Risk exposure screening (concepts)\n\n**Educational reference only.** Labels and scores from analytics or compliance tools are **not** legal findings. Verify **primary** sanctions lists and jurisdictional requirements with qualified teams. Pair with **crypto-investigation-compliance** and **blockchain-analytics-operations**.\n\n## Risk Exposure Engine (idea)\n\nA **risk exposure engine** combines a **database of address or entity labels** with **on-chain interaction graphs** to estimate whether a screened **address** or **transaction** is associated with **known risk categories**. Implementation details differ by product; confirm hop counts, thresholds, and asset scope in your provider’s documentation (see **phalcon-compliance-documentation** where relevant).\n\n## Risk indicators (typical taxonomy)\n\nRisk indicators are **categories** assigned to addresses or entities. Names vary by vendor; the table below lists **common** families used in industry documentation.\n\n| Risk indicator | Description |\n|----------------|-------------|\n| Sanctioned | Associated with entities on official sanctions lists (for example OFAC SDN), where applicable. |\n| Terrorism financing | Associated with designated terrorist organizations or financing of terrorism. |\n| Human trafficking | Associated with trafficking-related organizations or flows. |\n| Drug trafficking | Associated with illicit production, transport, or distribution of controlled substances. |\n| Attack | Related to exploit actors, attacker contracts, or associated fund movements. |\n| Scam | Fraudulent schemes: phishing, Ponzi, honeypots, pig-butchering, etc. |\n| Ransomware | Controlled by ransomware operators or used to pay ransom. |\n| Child sexual abuse material (CSAM) facilitation | Facilitating payments for platforms distributing CSAM. |\n| Money laundering | Suspected laundering of illicit proceeds. |\n| Mixing | Mixer or privacy services that obscure trails. |\n| Darknet market | Operators of darknet markets. |\n| Darknet business | Other illicit darknet commerce (for example weapons, identity theft). |\n| Frozen \u002F contract blacklist | Blacklisted by major contracts or issuers (for example stablecoin freezes). |\n| Gambling | Online gambling service addresses. |\n| No-KYC exchange | Virtual asset service providers with weak KYC, per provider policy. |\n| FATF high-risk jurisdiction | Entities tied to jurisdictions on FATF “black” lists (as used by the data provider). |\n| FATF grey-list jurisdiction | Entities tied to FATF grey-list jurisdictions (as used by the data provider). |\n\n## Exposure metrics\n\n| Term | Meaning |\n|------|---------|\n| **Exposure value** | Total USD value (per provider’s pricing source) of assets that **originated from** or **interacted with** a specified risk-labeled source, under the engine’s rules. |\n| **Exposure percentage** | Share of **tainted** value relative to total **inflow** or **outflow** value for the screened address, under the configured window and rules. |\n\nInterpretation is **policy-dependent**-same raw hops can score differently by direction, hop depth, and minimum amounts.\n\n## Address-level screening (common templates)\n\nMany platforms expose three **template** families for **addresses**:\n\n1. **Entity \u002F direct label risk** - The screened address **itself** carries a risk label (for example sanctioned or scam).  \n   *Illustrative:* an address is flagged because it matches an OFAC-listed identifier in the provider’s dataset.\n\n2. **Interaction risk** - Traces **incoming or outgoing** value across **multiple hops**. If any counterparty in the path carries a risk label, the engine may flag exposure **subject to** direction, hop limits, amount thresholds, and decay rules.\n\n3. **Blacklist interaction** - Detects interaction with addresses on a **customer-defined** or **tenant** blacklist (policy-specific).\n\n## Transaction-level screening (common templates)\n\nFor a **single transaction**, engines often provide:\n\n1. **Participant risk** - Whether **addresses participating** in the transaction carry configured risk indicators.  \n   **Deposit vs withdrawal (typical convention):** for a directional screen, **deposit** flows may screen only the **from** side, and **withdrawal** flows only the **to** side-confirm in product docs.\n\n2. **Interaction \u002F flow risk** - Traces fund **provenance** or **destination** of the transaction’s value to detect prior exposure (for example receiving from a phishing-labeled cluster). Deposit\u002Fwithdrawal modes may restrict whether **source** or **destination** tracing applies.\n\n3. **Blacklist interaction** - Whether the transaction touches **blacklisted** addresses per policy.\n\n## Guardrails\n\n- **Do not** treat a commercial **label** as a court finding or automatic **sanctions** violation.  \n- **Do not** assist with **evading** screening, mixers for illicit purpose, or **circumventing** law enforcement processes.  \n- **Separate** on-chain **facts** from **vendor scoring**-document both when reporting.\n\n## See also\n\n- **behavioral-risk-screening-concepts** - volume, velocity, and transit-style **behavior** heuristics (complements label-based exposure).\n\n**Goal:** give investigators a **shared vocabulary** for exposure-style screening without binding any specific **product** behavior or **legal** outcome.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Frisk-exposure-screening-concepts",1,"https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion","https:\u002F\u002Fbastionagentique.com\u002F","https:\u002F\u002Fgithub.com\u002Fzkos-labs","https:\u002F\u002Fzkoslabs.org","A research-driven builders' organization advancing programmable trust infrastructure for Ethereum and interoperable open networks.","2026-11-13 21:01:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zkos-labs\u002Fbastion --skill risk-exposure-screening-concepts",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill risk-exposure-screening-concepts",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill risk-exposure-screening-concepts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frisk-exposure-screening-concepts\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7213RCWV886P2R63MTQAEGW","bastion","Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7213MYSJE23KMMTD95Y3M3Z","web2-api-firewall-administrator","Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII\u002Fsecrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb2-api-firewall-administrator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7213HE08PE43M2H0QZENZP2","transaction-screening-workflow-concepts","Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7213DQ7TVE986643SR105Y4","solana-tracing-specialist","Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX\u002FJito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-tracing-specialist\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M72138PB2HTKJ0J39WNSRCRR","solana-onchain-intelligence-resources","Companion to blockint-skills Solana work-official doc indexes and stacks for RPC\u002Findexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy\u002Fregulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev\u002Ftesting), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-onchain-intelligence-resources\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent","Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[]]