[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720XMW5GDFPC6237CV8R7N9":3,"skill-same:01M720XMW5GDFPC6237CV8R7N9":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},"01M720XMW5GDFPC6237CV8R7N9","address-screening-workflow-concepts",null,"Educational map of address-centric compliance screening-tags vs markers, single and bulk import, address list and detail views, audit trails, blacklist and whitelist policy effects, and delete behavior. Use when the user asks how commercial screening UIs organize wallets\u002Fcontracts, KYA-style exports, or rescreen policies-not for legal advice or bypassing controls.","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\u002Faddress-screening-workflow-concepts\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: address-screening-workflow-concepts\ndescription: Educational map of address-centric compliance screening-tags vs markers, single and bulk import, address list and detail views, audit trails, blacklist and whitelist policy effects, and delete behavior. Use when the user asks how commercial screening UIs organize wallets\u002Fcontracts, KYA-style exports, or rescreen policies-not for legal advice or bypassing controls.\n---\n\n# Address screening workflow (concepts)\n\n**Educational reference only.** Exact limits (row counts, credit rules, field names) vary by **product** and **release**-confirm in live documentation (**phalcon-compliance-documentation** for Phalcon Compliance). Pair with **risk-exposure-screening-concepts** and **behavioral-risk-screening-concepts** for what engines measure.\n\n## What is being screened?\n\n**Addresses** usually mean **wallets or contracts** on specific **chains**. In a VASP or platform context, these are often **customer** or **counterparty** addresses that **touch** your service. **Proactive** screening is meant to surface high-risk entities early so teams can apply **policy** (review, block, escalate)-not to replace **legal** process or **law-enforcement** channels.\n\n## Tags vs markers\n\n| Concept | Typical role |\n|---------|----------------|\n| **Tags** | Human-readable **labels** to distinguish addresses in the UI. Often split into **default** tags (from the **provider’s** curated or verified dataset) and **user-defined** tags. User-defined values commonly **override** defaults when both exist. |\n| **Markers** | **Categories** by attribute or behavior (for example **deposit** address, **frozen**, **VIP**, **pending review**). |\n\n**System markers** (often immutable in the product):\n\n- Sourced from the **provider’s** risk or reference **database** (for example sanctioned, mixer-per vendor taxonomy).\n- May be **non-editable** in the UI.\n\n**Custom markers** (tenant-defined):\n\n- Internal classifications your team adds.\n- Usually **editable**; products may cap **total** markers per address (for example **system + custom** combined ≤ **5**-verify in docs).\n\nNaming of fields differs by vendor; treat the table as **pattern**, not a spec.\n\n## Import and screening methods\n\nCommon operational paths:\n\n1. **Single address** - Enter an address; the product **resolves** chain metadata and pulls **tags** \u002F **system markers** from its integrations, then you **select** it for ongoing screening.\n2. **Bulk CSV** - Upload many addresses using a **template** from the product (chain name, address, optional tag\u002Fmarker\u002Fcustomer id).\n\nTypical **CSV-style** columns (names vary):\n\n| Field | Purpose |\n|-------|---------|\n| Chain | Exact chain identifier required by the template |\n| Address | On-chain identifier |\n| Tag | Optional private user tag |\n| Marker | Optional custom marker |\n| Customer ID | Optional internal customer key (new or existing) |\n\nBulk uploads often have a **row limit per file** (for example on the order of **100** addresses-confirm current limit). After import, review **success\u002Ffailure** rows in the UI.\n\n## Address list\n\nScreened addresses usually appear in a **list** with columns such as: address, **risk summary**, **open alerts**, **last screened** time, **markers**, **customer**, **time added**, **rescreen** status-exact columns depend on the product.\n\n## Address details page\n\nDrilling into one address, products commonly expose:\n\n- **Basic information** - Entity\u002Fcategory (if modeled), chain, markers, tags, balances, aggregate **inflow** \u002F **outflow**.\n- **Risk summary** - High-level rollup of triggered alerts.\n- **Risk overview** - Finer breakdown: identified risk types, exposure-style views (for example share of tainted notionals), lists of **exposed** or **related** addresses, and links to **graph** or **trace** tools **where the product integrates them** (vendor-specific).\n- **Alerts** - Filterable alert history for that address.\n- **Audit log** - **Comments** (collaboration) and **system events** (screening runs, risk changes, automation).\n\nCommon **actions**:\n\n- **Rescreen** - Force a fresh screening run (subject to product rules and **credits**).\n- **Export KYA-style report** - Pack address metadata and risk findings for **internal** or **audit** communication (not a substitute for regulatory filings).\n\n## Blacklist vs whitelist (policy lists)\n\nProducts often let operators put addresses on **internal** lists. **Effects are policy- and product-specific**; a common **pattern** looks like:\n\n**Blacklist (blocked \u002F high-friction list):**\n\n- May force a **high** internal severity (for example **critical** risk tier).\n- May **skip** ordinary periodic screening (to save credits) while still treating the address as **blocked** or **escalated**.\n- May **disable** automatic **rescreen** cycles.\n- May **propagate** severity to **direct** counterparties in some configurations (strong compliance implications-follow your program’s rulebook).\n\n**Whitelist (trusted \u002F low-friction list):**\n\n- May mark the address as **no** or **low** internal risk for **policy** purposes.\n- May **exclude** from standard engine passes and **rescreen** loops to save credits.\n\n**Caution:** whitelist entries are **operational** decisions inside the tool-they do **not** change real-world illicit activity off-platform. Document **approvals** and **review cadence**.\n\n## Deleting an address\n\nRemoving an address from the **inventory** typically **expires** or **closes** **alerts** tied to that record in the product. It does **not** erase public-chain history. Confirm retention and audit requirements before deletion.\n\n## Guardrails\n\n- **Do not** paste **production** customer lists, CSVs, or internal IDs into **public** chats.  \n- **Do not** assist with **evading** sanctions, **mis-labeling** peers, or **gaming** whitelist policies.  \n- Prefer **primary** legal and sanctions sources for **regulatory** obligations; UI risk tiers are **heuristics**.\n\n## See also\n\n- **transaction-screening-workflow-concepts** - tx hash \u002F transfer-level screening, **deposit** vs **withdrawal**, STR-style exports.\n\n**Goal:** a portable mental model of **address screening** UIs and **list** semantics aligned with common compliance products, without binding a specific **vendor** implementation.\n","# Address screening workflow (concepts)\n\n**Educational reference only.** Exact limits (row counts, credit rules, field names) vary by **product** and **release**-confirm in live documentation (**phalcon-compliance-documentation** for Phalcon Compliance). Pair with **risk-exposure-screening-concepts** and **behavioral-risk-screening-concepts** for what engines measure.\n\n## What is being screened?\n\n**Addresses** usually mean **wallets or contracts** on specific **chains**. In a VASP or platform context, these are often **customer** or **counterparty** addresses that **touch** your service. **Proactive** screening is meant to surface high-risk entities early so teams can apply **policy** (review, block, escalate)-not to replace **legal** process or **law-enforcement** channels.\n\n## Tags vs markers\n\n| Concept | Typical role |\n|---------|----------------|\n| **Tags** | Human-readable **labels** to distinguish addresses in the UI. Often split into **default** tags (from the **provider’s** curated or verified dataset) and **user-defined** tags. User-defined values commonly **override** defaults when both exist. |\n| **Markers** | **Categories** by attribute or behavior (for example **deposit** address, **frozen**, **VIP**, **pending review**). |\n\n**System markers** (often immutable in the product):\n\n- Sourced from the **provider’s** risk or reference **database** (for example sanctioned, mixer-per vendor taxonomy).\n- May be **non-editable** in the UI.\n\n**Custom markers** (tenant-defined):\n\n- Internal classifications your team adds.\n- Usually **editable**; products may cap **total** markers per address (for example **system + custom** combined ≤ **5**-verify in docs).\n\nNaming of fields differs by vendor; treat the table as **pattern**, not a spec.\n\n## Import and screening methods\n\nCommon operational paths:\n\n1. **Single address** - Enter an address; the product **resolves** chain metadata and pulls **tags** \u002F **system markers** from its integrations, then you **select** it for ongoing screening.\n2. **Bulk CSV** - Upload many addresses using a **template** from the product (chain name, address, optional tag\u002Fmarker\u002Fcustomer id).\n\nTypical **CSV-style** columns (names vary):\n\n| Field | Purpose |\n|-------|---------|\n| Chain | Exact chain identifier required by the template |\n| Address | On-chain identifier |\n| Tag | Optional private user tag |\n| Marker | Optional custom marker |\n| Customer ID | Optional internal customer key (new or existing) |\n\nBulk uploads often have a **row limit per file** (for example on the order of **100** addresses-confirm current limit). After import, review **success\u002Ffailure** rows in the UI.\n\n## Address list\n\nScreened addresses usually appear in a **list** with columns such as: address, **risk summary**, **open alerts**, **last screened** time, **markers**, **customer**, **time added**, **rescreen** status-exact columns depend on the product.\n\n## Address details page\n\nDrilling into one address, products commonly expose:\n\n- **Basic information** - Entity\u002Fcategory (if modeled), chain, markers, tags, balances, aggregate **inflow** \u002F **outflow**.\n- **Risk summary** - High-level rollup of triggered alerts.\n- **Risk overview** - Finer breakdown: identified risk types, exposure-style views (for example share of tainted notionals), lists of **exposed** or **related** addresses, and links to **graph** or **trace** tools **where the product integrates them** (vendor-specific).\n- **Alerts** - Filterable alert history for that address.\n- **Audit log** - **Comments** (collaboration) and **system events** (screening runs, risk changes, automation).\n\nCommon **actions**:\n\n- **Rescreen** - Force a fresh screening run (subject to product rules and **credits**).\n- **Export KYA-style report** - Pack address metadata and risk findings for **internal** or **audit** communication (not a substitute for regulatory filings).\n\n## Blacklist vs whitelist (policy lists)\n\nProducts often let operators put addresses on **internal** lists. **Effects are policy- and product-specific**; a common **pattern** looks like:\n\n**Blacklist (blocked \u002F high-friction list):**\n\n- May force a **high** internal severity (for example **critical** risk tier).\n- May **skip** ordinary periodic screening (to save credits) while still treating the address as **blocked** or **escalated**.\n- May **disable** automatic **rescreen** cycles.\n- May **propagate** severity to **direct** counterparties in some configurations (strong compliance implications-follow your program’s rulebook).\n\n**Whitelist (trusted \u002F low-friction list):**\n\n- May mark the address as **no** or **low** internal risk for **policy** purposes.\n- May **exclude** from standard engine passes and **rescreen** loops to save credits.\n\n**Caution:** whitelist entries are **operational** decisions inside the tool-they do **not** change real-world illicit activity off-platform. Document **approvals** and **review cadence**.\n\n## Deleting an address\n\nRemoving an address from the **inventory** typically **expires** or **closes** **alerts** tied to that record in the product. It does **not** erase public-chain history. Confirm retention and audit requirements before deletion.\n\n## Guardrails\n\n- **Do not** paste **production** customer lists, CSVs, or internal IDs into **public** chats.  \n- **Do not** assist with **evading** sanctions, **mis-labeling** peers, or **gaming** whitelist policies.  \n- Prefer **primary** legal and sanctions sources for **regulatory** obligations; UI risk tiers are **heuristics**.\n\n## See also\n\n- **transaction-screening-workflow-concepts** - tx hash \u002F transfer-level screening, **deposit** vs **withdrawal**, STR-style exports.\n\n**Goal:** a portable mental model of **address screening** UIs and **list** semantics aligned with common compliance products, without binding a specific **vendor** implementation.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Faddress-screening-workflow-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 address-screening-workflow-concepts",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill address-screening-workflow-concepts",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill address-screening-workflow-concepts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faddress-screening-workflow-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",[],[]]