[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720ZDXP090RKWEGRKDJME8H":3,"skill-same:01M720ZDXP090RKWEGRKDJME8H":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},"01M720ZDXP090RKWEGRKDJME8H","chainalysis-sanctions-screening",null,"Routes to Chainalysis public Sanctions Screening surfaces-the free Sanctions REST API (address checks against OFAC SDN crypto listings) and the EVM on-chain oracle-plus how they differ from paid Chainalysis customer data. Use when the user references Chainalysis sanctions tooling, public.chainalysis.com, or repo notes in Chainalysis.md-not for legal conclusions, full vendor ToU reproduction, or substituting official government sanctions lists.","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\u002Fchainalysis-sanctions-screening\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: chainalysis-sanctions-screening\ndescription: Routes to Chainalysis public Sanctions Screening surfaces-the free Sanctions REST API (address checks against OFAC SDN crypto listings) and the EVM on-chain oracle-plus how they differ from paid Chainalysis customer data. Use when the user references Chainalysis sanctions tooling, public.chainalysis.com, or repo notes in Chainalysis.md-not for legal conclusions, full vendor ToU reproduction, or substituting official government sanctions lists.\n---\n\n# Chainalysis - public sanctions screening (reference)\n\n**Educational routing only.** This skill does **not** reproduce Chainalysis **Terms of Use**, **Privacy Policy**, or other legal text. For binding terms, rate limits, signup URLs, and contract addresses, use **Chainalysis’s current public documentation** and dashboards.\n\n## What the public product family covers (high level)\n\n| Surface | Role (conceptual) |\n|---------|-------------------|\n| **Sanctions API** | **REST** service: check whether a **cryptocurrency address** appears on **sanctions-related** listings Chainalysis exposes for this API (commonly described in relation to **OFAC SDN** crypto addresses). Authenticate with an **API key** (typically `X-API-Key` header). |\n| **Oracle (EVM)** | **On-chain** smart contract aimed at dApps that need **in-protocol** screening-upstream docs describe a narrower scope than the API (e.g. **Ethereum\u002FEVM** address checks vs API response shape). |\n\n**Customers:** If you use paid Chainalysis products, upstream docs note you may receive **broader** identifications (e.g. **Chainalysis Identifications**, clustering beyond what the free public API exposes). Treat **customer** docs and contracts as authoritative for your org.\n\n## Integration facts to verify live (do not trust stale copies)\n\n- **No browser CORS:** Public docs state the API is **not** meant for direct **cross-origin** browser calls-use a **backend** or server-side caller.\n- **Authentication:** Requests typically send `X-API-KEY` \u002F `X-API-Key` (confirm header name in current docs).\n- **Example host pattern** seen in public materials: `https:\u002F\u002Fpublic.chainalysis.com\u002Fapi\u002Fv1\u002Faddress\u002F\u003Caddress>` - **paths and versions change**; copy from official docs before shipping.\n- **Rate limits:** Documentation cites high-volume windows (e.g. thousands of requests per few minutes)-**confirm the current limit** in official docs; **429\u002F403** handling belongs in your integration.\n- **Support (public channel listed in materials):** `sanctions-api-support@chainalysis.com` - verify on the **live** support page.\n\n## Local excerpt in this repository\n\nThe repo may include **`Chainalysis.md`** - a **local excerpt \u002F scratch** of public-facing API and terms text. Use it only as a **convenience pointer**; **integration details** (endpoints, fields, legal terms) must match **current** Chainalysis publications.\n\n## How to use with blockint\n\n| Need | Skill |\n|------|--------|\n| Ethical investigation workflow, reporting, sanctions **process** context | **crypto-investigation-compliance** |\n| Sanctions + risk tools via Range MCP (separate product) | **range-ai-investigation-playbook** |\n| Risk indicator \u002F exposure vocabulary (educational) | **risk-exposure-screening-concepts** |\n| Address\u002Ftransaction screening **workflow** concepts (educational) | **address-screening-workflow-concepts**, **transaction-screening-workflow-concepts** |\n| AML \u002F analytics platforms (vendor-neutral) | **blockchain-analytics-operations** |\n\n## Guardrails\n\n- **Sanctions compliance is legal and jurisdictional** - API output is **not** a substitute for **OFAC** \u002F **EU** \u002F **UN** lists, **licensed counsel**, or your institution’s **compliance program**.\n- **Accuracy:** Vendor docs disclaim **guarantees** on timeliness and completeness-design **human review** and **primary-source** checks for material decisions.\n- **Secrets:** Never commit or paste **API keys** or **internal** investigation exports into public repos or chats.\n- **Prohibited use:** Respect Chainalysis **API Terms** (no scraping, no abuse, no competing “clone” of their product features-read the **live** terms).\n\n**Goal:** a neutral blockint router for **Chainalysis public Sanctions Screening** surfaces and the optional **`Chainalysis.md`** excerpt, without mirroring vendor legal text or implying non-public product scope.\n","# Chainalysis - public sanctions screening (reference)\n\n**Educational routing only.** This skill does **not** reproduce Chainalysis **Terms of Use**, **Privacy Policy**, or other legal text. For binding terms, rate limits, signup URLs, and contract addresses, use **Chainalysis’s current public documentation** and dashboards.\n\n## What the public product family covers (high level)\n\n| Surface | Role (conceptual) |\n|---------|-------------------|\n| **Sanctions API** | **REST** service: check whether a **cryptocurrency address** appears on **sanctions-related** listings Chainalysis exposes for this API (commonly described in relation to **OFAC SDN** crypto addresses). Authenticate with an **API key** (typically `X-API-Key` header). |\n| **Oracle (EVM)** | **On-chain** smart contract aimed at dApps that need **in-protocol** screening-upstream docs describe a narrower scope than the API (e.g. **Ethereum\u002FEVM** address checks vs API response shape). |\n\n**Customers:** If you use paid Chainalysis products, upstream docs note you may receive **broader** identifications (e.g. **Chainalysis Identifications**, clustering beyond what the free public API exposes). Treat **customer** docs and contracts as authoritative for your org.\n\n## Integration facts to verify live (do not trust stale copies)\n\n- **No browser CORS:** Public docs state the API is **not** meant for direct **cross-origin** browser calls-use a **backend** or server-side caller.\n- **Authentication:** Requests typically send `X-API-KEY` \u002F `X-API-Key` (confirm header name in current docs).\n- **Example host pattern** seen in public materials: `https:\u002F\u002Fpublic.chainalysis.com\u002Fapi\u002Fv1\u002Faddress\u002F\u003Caddress>` - **paths and versions change**; copy from official docs before shipping.\n- **Rate limits:** Documentation cites high-volume windows (e.g. thousands of requests per few minutes)-**confirm the current limit** in official docs; **429\u002F403** handling belongs in your integration.\n- **Support (public channel listed in materials):** `sanctions-api-support@chainalysis.com` - verify on the **live** support page.\n\n## Local excerpt in this repository\n\nThe repo may include **`Chainalysis.md`** - a **local excerpt \u002F scratch** of public-facing API and terms text. Use it only as a **convenience pointer**; **integration details** (endpoints, fields, legal terms) must match **current** Chainalysis publications.\n\n## How to use with blockint\n\n| Need | Skill |\n|------|--------|\n| Ethical investigation workflow, reporting, sanctions **process** context | **crypto-investigation-compliance** |\n| Sanctions + risk tools via Range MCP (separate product) | **range-ai-investigation-playbook** |\n| Risk indicator \u002F exposure vocabulary (educational) | **risk-exposure-screening-concepts** |\n| Address\u002Ftransaction screening **workflow** concepts (educational) | **address-screening-workflow-concepts**, **transaction-screening-workflow-concepts** |\n| AML \u002F analytics platforms (vendor-neutral) | **blockchain-analytics-operations** |\n\n## Guardrails\n\n- **Sanctions compliance is legal and jurisdictional** - API output is **not** a substitute for **OFAC** \u002F **EU** \u002F **UN** lists, **licensed counsel**, or your institution’s **compliance program**.\n- **Accuracy:** Vendor docs disclaim **guarantees** on timeliness and completeness-design **human review** and **primary-source** checks for material decisions.\n- **Secrets:** Never commit or paste **API keys** or **internal** investigation exports into public repos or chats.\n- **Prohibited use:** Respect Chainalysis **API Terms** (no scraping, no abuse, no competing “clone” of their product features-read the **live** terms).\n\n**Goal:** a neutral blockint router for **Chainalysis public Sanctions Screening** surfaces and the optional **`Chainalysis.md`** excerpt, without mirroring vendor legal text or implying non-public product scope.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fchainalysis-sanctions-screening",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 chainalysis-sanctions-screening",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill chainalysis-sanctions-screening",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill chainalysis-sanctions-screening","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchainalysis-sanctions-screening\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",[],[]]