[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7213HE08PE43M2H0QZENZP2":3,"skill-same:01M7213HE08PE43M2H0QZENZP2":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},"01M7213HE08PE43M2H0QZENZP2","transaction-screening-workflow-concepts",null,"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.","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\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: transaction-screening-workflow-concepts\ndescription: 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.\n---\n\n# Transaction screening workflow (concepts)\n\n**Educational reference only.** Limits (batch sizes, engines, STR formats) change by **product** and **jurisdiction**-confirm in **phalcon-compliance-documentation** and your compliance program. Pair with **address-screening-workflow-concepts** (wallet inventory) and **risk-exposure-screening-concepts** (how **direction** affects participant and flow rules).\n\n## Unit of analysis\n\n- The **smallest** screening unit is often a **single transfer** (asset movement from **from** → **to** within a tx).\n- One **transaction** (one hash) may contain **many** transfers. Products may let you screen **each** transfer, **subset**, or roll up to **transaction-level** risk-behavior varies by vendor.\n\n## Direction (deposit vs withdrawal)\n\nSetting **Deposit** vs **Withdrawal** steers **which** rules and **which** side of the flow the engines emphasize:\n\n| Direction | Typical screening focus |\n|-----------|-------------------------|\n| **Deposit** | **Inflow** to the platform\u002Fcustomer relationship-provenance of funds **arriving**. |\n| **Withdrawal** | **Outflow** and **destination**-where funds **leave** toward. |\n\nCommon product behavior (verify in docs):\n\n- Rules can be **scoped** to one direction (for example deposit-only policies do **not** run on withdrawal-labeled items).\n- If **no** direction is set, some products default to **running both** deposit- and withdrawal-oriented passes to reduce misconfiguration.\n- Correct direction is used to **tune** rules and **reduce false positives**-it is an **operational** control, not a legal classification.\n\nThis aligns with participant\u002Fflow screening notes in **risk-exposure-screening-concepts**.\n\n## Labels\n\n**Labels** are user-defined strings for **organization** and **case context** on a **transaction** or **transfer** (distinct from address **tags\u002Fmarkers** in **address-screening-workflow-concepts**).\n\n## Import methods\n\n1. **Single transaction hash** - Paste a hash; the product **fetches** parsed transfers; you **select** which transfer(s) to screen and attach **direction**, **labels**, and **customer** linkage.\n2. **Bulk CSV** - Template-driven import of many rows (batch size caps are **product-specific**-on the order of **hundreds** per file in some docs).\n\nTypical **CSV-style** columns (names vary):\n\n| Field | Purpose |\n|-------|---------|\n| Chain | Network identifier per template |\n| Transaction hash | On-chain tx id |\n| Label | Optional private label |\n| Direction | Optional `Deposit` \u002F `Withdrawal` |\n| Customer ID | Optional internal customer key |\n| Transfer From \u002F Transfer To | Optional pair to **disambiguate** one transfer inside a multi-transfer tx |\n\nReview **per-row** import outcomes in the UI.\n\n## Transaction list\n\nLists commonly show: hash, **risk summary**, **screening direction**, **open alerts**, **last screened**, **notional** (often USD), **token amount**, **asset**, **from\u002Fto**, **timestamp**, **customer**, **labels**, **added** time. Multi-transfer rows may **collapse** with **expand** to child transfers.\n\n## Transaction details page\n\nTypical sections:\n\n- **Basic information** - Asset, time, labels, customer, etc.\n- **Risk summary** - Rolled-up alert view.\n- **Risk overview** - Finer breakdown: risk categories, exposure-style charts, exposed address lists, **fund-flow** narrative; products may link to an **external graph** or **trace** tool where integrated.\n- **Token transfers** - **Graph** plus **tabular** list of each transfer; **per-transfer** alerts; **unscreened** legs may be screenable on demand.\n- **Transfers overview** - Compact index with shortcuts into each transfer.\n- **Alerts** - Filterable list.\n- **Audit log** - **Comments** and **system events** (same idea as address workflow).\n\n**Rescreen** - Re-run screening for the **whole** transaction or a **specific** transfer; **direction** may be set per run.\n\n## STR-style and regulatory exports\n\nSome products expose **Suspicious Transaction Report (STR)** or regional equivalents:\n\n- **Region** selection matters-**formats** and **fields** differ by jurisdiction.\n- **Direction** is often a **prerequisite** for valid STR generation in the product model.\n- Reports may be generated **per transfer** when policy requires **transfer-level** suspicious activity narratives.\n\n**Not legal advice.** STR obligations depend on **local law** and **institutional** policy; use qualified **compliance** and **legal** review for filings.\n\n## Deleting a transaction\n\nRemoving a transaction record typically deletes **associated transfers** and **expires** related **alerts** **in the product**. Public-chain data **remain** on explorers.\n\n## Guardrails\n\n- **Do not** paste **live** production tx hashes tied to identifiable customers into **public** channels.  \n- **Do not** assist with **structuring** flows to **evade** monitoring or **mis-labeling** direction.  \n- STR and **travel rule** questions need **program-specific** guidance beyond generic skills.\n\n## See also\n\n- **address-screening-workflow-concepts** - wallet inventory, tags\u002Fmarkers, blacklist\u002Fwhitelist.  \n- **behavioral-risk-screening-concepts** - velocity and amount heuristics that may surface at transfer level.\n\n**Goal:** a portable mental model of **transaction** screening UIs and **direction** semantics aligned with common compliance products, without binding a specific **vendor** implementation.\n","# Transaction screening workflow (concepts)\n\n**Educational reference only.** Limits (batch sizes, engines, STR formats) change by **product** and **jurisdiction**-confirm in **phalcon-compliance-documentation** and your compliance program. Pair with **address-screening-workflow-concepts** (wallet inventory) and **risk-exposure-screening-concepts** (how **direction** affects participant and flow rules).\n\n## Unit of analysis\n\n- The **smallest** screening unit is often a **single transfer** (asset movement from **from** → **to** within a tx).\n- One **transaction** (one hash) may contain **many** transfers. Products may let you screen **each** transfer, **subset**, or roll up to **transaction-level** risk-behavior varies by vendor.\n\n## Direction (deposit vs withdrawal)\n\nSetting **Deposit** vs **Withdrawal** steers **which** rules and **which** side of the flow the engines emphasize:\n\n| Direction | Typical screening focus |\n|-----------|-------------------------|\n| **Deposit** | **Inflow** to the platform\u002Fcustomer relationship-provenance of funds **arriving**. |\n| **Withdrawal** | **Outflow** and **destination**-where funds **leave** toward. |\n\nCommon product behavior (verify in docs):\n\n- Rules can be **scoped** to one direction (for example deposit-only policies do **not** run on withdrawal-labeled items).\n- If **no** direction is set, some products default to **running both** deposit- and withdrawal-oriented passes to reduce misconfiguration.\n- Correct direction is used to **tune** rules and **reduce false positives**-it is an **operational** control, not a legal classification.\n\nThis aligns with participant\u002Fflow screening notes in **risk-exposure-screening-concepts**.\n\n## Labels\n\n**Labels** are user-defined strings for **organization** and **case context** on a **transaction** or **transfer** (distinct from address **tags\u002Fmarkers** in **address-screening-workflow-concepts**).\n\n## Import methods\n\n1. **Single transaction hash** - Paste a hash; the product **fetches** parsed transfers; you **select** which transfer(s) to screen and attach **direction**, **labels**, and **customer** linkage.\n2. **Bulk CSV** - Template-driven import of many rows (batch size caps are **product-specific**-on the order of **hundreds** per file in some docs).\n\nTypical **CSV-style** columns (names vary):\n\n| Field | Purpose |\n|-------|---------|\n| Chain | Network identifier per template |\n| Transaction hash | On-chain tx id |\n| Label | Optional private label |\n| Direction | Optional `Deposit` \u002F `Withdrawal` |\n| Customer ID | Optional internal customer key |\n| Transfer From \u002F Transfer To | Optional pair to **disambiguate** one transfer inside a multi-transfer tx |\n\nReview **per-row** import outcomes in the UI.\n\n## Transaction list\n\nLists commonly show: hash, **risk summary**, **screening direction**, **open alerts**, **last screened**, **notional** (often USD), **token amount**, **asset**, **from\u002Fto**, **timestamp**, **customer**, **labels**, **added** time. Multi-transfer rows may **collapse** with **expand** to child transfers.\n\n## Transaction details page\n\nTypical sections:\n\n- **Basic information** - Asset, time, labels, customer, etc.\n- **Risk summary** - Rolled-up alert view.\n- **Risk overview** - Finer breakdown: risk categories, exposure-style charts, exposed address lists, **fund-flow** narrative; products may link to an **external graph** or **trace** tool where integrated.\n- **Token transfers** - **Graph** plus **tabular** list of each transfer; **per-transfer** alerts; **unscreened** legs may be screenable on demand.\n- **Transfers overview** - Compact index with shortcuts into each transfer.\n- **Alerts** - Filterable list.\n- **Audit log** - **Comments** and **system events** (same idea as address workflow).\n\n**Rescreen** - Re-run screening for the **whole** transaction or a **specific** transfer; **direction** may be set per run.\n\n## STR-style and regulatory exports\n\nSome products expose **Suspicious Transaction Report (STR)** or regional equivalents:\n\n- **Region** selection matters-**formats** and **fields** differ by jurisdiction.\n- **Direction** is often a **prerequisite** for valid STR generation in the product model.\n- Reports may be generated **per transfer** when policy requires **transfer-level** suspicious activity narratives.\n\n**Not legal advice.** STR obligations depend on **local law** and **institutional** policy; use qualified **compliance** and **legal** review for filings.\n\n## Deleting a transaction\n\nRemoving a transaction record typically deletes **associated transfers** and **expires** related **alerts** **in the product**. Public-chain data **remain** on explorers.\n\n## Guardrails\n\n- **Do not** paste **live** production tx hashes tied to identifiable customers into **public** channels.  \n- **Do not** assist with **structuring** flows to **evade** monitoring or **mis-labeling** direction.  \n- STR and **travel rule** questions need **program-specific** guidance beyond generic skills.\n\n## See also\n\n- **address-screening-workflow-concepts** - wallet inventory, tags\u002Fmarkers, blacklist\u002Fwhitelist.  \n- **behavioral-risk-screening-concepts** - velocity and amount heuristics that may surface at transfer level.\n\n**Goal:** a portable mental model of **transaction** screening UIs and **direction** semantics aligned with common compliance products, without binding a specific **vendor** implementation.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Ftransaction-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 transaction-screening-workflow-concepts",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill transaction-screening-workflow-concepts",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill transaction-screening-workflow-concepts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-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},"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":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},"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":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},"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",[],[],{"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},"01M72131HP2PBV8CWYGSWV73Y6","solana-clustering-case-study-agent","Turns advanced Solana clustering work into complete, shareable public case studies-seed selection, multi-layer graphs, narrative arcs, visual evidence packs, and reproducible exports (CSV, queries). Use when the user wants a Solana rug\u002FSybil\u002Fsniper\u002Fphishing case study, X\u002Fthread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-clustering-case-study-agent\u002FSKILL.md",[],[]]