「sanctions」の検索結果

Complete sanctions and export control analysis tool — individual designations, sectoral sanctions, dual-use goods, payment systems (SWIFT/USD), and extraterritorial regimes (EAR/ITAR/ FDPR US, ECL China). Triggers: "is X sanctioned?", "can I do business with X?", "can I sell Y to Z?", "pétrole Russie", "biens à double usage", "gel des avoirs", "sanctions internationales", "liste OFAC", "liste UE", "double usage", "embargo", "licence d'exportation", "SWIFT", "paiement en dollars", "US goods", "FDPR", "EAR", "ITAR", "BIS", "ECL chine", "no re-export clause", "sanctions sectorielles", "puis-je travailler avec X?", or any transaction involving a foreign person, product, sector, destination country, or payment in USD/EUR. Always adapt to user profile. Always run for any sanctions or export control query — even vague or exploratory ones.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

日本語の概要は準備中です。原文の説明を表示しています。

Screen a client, counterparty, payer or corporate against the sanctions lists published by the designating authorities themselves — the UK Sanctions List (FCDO), OFSI, the UN Security Council, the EU consolidated list and OFAC's SDN and non-SDN lists. Use when onboarding, before taking a payment, before completing a transaction, or whenever a name must be checked against sanctions. Produces candidates and provenance, never a clearance: the record names every list searched with its publication date and count, states what was NOT searched, and ends at a blank decision block. Fails closed — a cache that is missing, damaged, truncated or stale is reported NOT SEARCHED and the process exits non-zero, so nothing can read an incomplete run as clean. Matches across transliteration, diacritics, homoglyphs and initials, because nobody spells a name the way the publisher does. Standard library only; screening opens no network connection.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a spreadsheet of test entries — newly designated names from OFAC, OFSI, and EU sanctions lists plus deliberate variations of those names — to validate that a sanctions screening system catches fresh designations and is tuned to the right fuzziness threshold. Use this whenever the user asks for sanctions list update test data, screening regression test data, screening QA, fuzzy match calibration, or wants to verify their screening lists are current. Trigger even if the user doesn't say 'screening' explicitly — phrases like 'test my sanctions list', 'check our SDN coverage', 'is my list up to date', or 'build me a regression set from the latest designations' should also invoke this skill.

日本語の概要は準備中です。原文の説明を表示しています。

Retrieve normalized OFAC sanctions pressure — designation summaries, recent additions, and per-country/per-program aggregates including sanctioned vessels and aircraft. Use when the user asks which countries or programs face sanctions pressure, or what was recently designated.

日本語の概要は準備中です。原文の説明を表示しています。

Sanctions and export control analysis tool for Claude Desktop. Real-time individual screening across 30+ official lists (UN, EU, OFAC, OFSI, French DGT...), sectoral analysis, dual-use goods (EU Reg. 2021/821), US/China extraterritorial regimes (EAR, ITAR, FDPR, ECL), USD/SWIFT risk and jurisdictional mapping across 30+ countries. All results sourced and verified in real time — no memory-based answers. Responds in French, English, German, Spanish, Russian and Chinese. Updated 19 May 2026 (EU 20th package, UK SEUC, Cuba EO). Indicative guidance only — not legal advice.

日本語の概要は準備中です。原文の説明を表示しています。

Adjudicates whether a hit generated by sanctions, PEP, or adverse-media screening is a true positive, false positive, or requires human escalation. Use whenever a user presents a screening alert, a name match against a watchlist (OFAC SDN, EU consolidated list, UK OFSI, UN list, PEP list, adverse media hit, etc.), or asks to clear a screening hit / reduce false positives / determine whether a flagged name is actually the listed party. Use even when the user describes the task casually — "is this person actually on the sanctions list", "did we get a real match", "clear this alert", "I have a hit on X" — these are all screening-adjudication tasks. Produces a deterministic determination with full audit trail (structured JSON + human-readable narrative). Designed for use by compliance analysts and screening systems.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates geopolitical risk impact on investment portfolios with sanctions exposure, conflict risk, and supply chain disruption analysis. Use when analyzing geopolitical risk, assessing sanctions impact, or evaluating political event exposure.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a production-grade KYC / AML / sanctions screening pipeline for customer onboarding, transaction monitoring, and ongoing review. Triggers: "KYC", "AML", "OFAC", "sanctions screening", "PEP".

日本語の概要は準備中です。原文の説明を表示しています。

Public-records OSINT investigation framework — SEC EDGAR filings, USAspending contracts, Senate lobbying, OFAC sanctions, ICIJ offshore leaks, NYC property records (ACRIS), OpenCorporates registries, CourtListener court records, Wayback Machine archives, Wikipedia + Wikidata, GDELT news monitoring. Entity resolution across sources, cross-link analysis, timing correlation, evidence chains. Python stdlib only.

日本語の概要は準備中です。原文の説明を表示しています。

Follow the money via public records and sanctions data.

日本語の概要は準備中です。原文の説明を表示しています。

Retrieve composite country risk intelligence — Country Instability Index (CII), travel advisory level, and active sanctions exposure — for one country by ISO code. Use when the user asks how risky or unstable a country is right now.

日本語の概要は準備中です。原文の説明を表示しています。

Geopolitical risk analysis: quantify crisis signals, identify precursors, and build event-driven strategies for war, sanctions, and supply disruption scenarios.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked 回复询盘, 外贸询盘怎么回, 帮我回客户邮件, 阿里国际站询盘回复, 客户只问价格怎么回, 跟进没回复的客户, or reply to a foreign-trade inquiry from a Chinese exporter. Produces a reply email in English (or the buyer's language) with a Chinese version for the sales team, a read of the inquiry's quality and the buyer's likely type, the questions to qualify the buyer, a price or quotation approach without underselling, and a follow-up sequence for no reply, with export-control and sanctions checks flagged.

日本語の概要は準備中です。原文の説明を表示しています。

Public-records OSINT: SEC, sanctions, courts, property.

日本語の概要は準備中です。原文の説明を表示しています。

Use the corp-finance-mcp server tools for specialty finance, regulatory, and compliance calculations. Invoke when performing private credit (unitranche, direct lending, syndication), insurance (loss reserving, premium pricing, Solvency II SCR), FP&A (variance analysis, break-even, working capital, rolling forecast), wealth management (retirement planning, tax-loss harvesting, estate planning), restructuring (recovery analysis, distressed debt), real assets (property valuation, project finance), venture capital (dilution, convertible instruments, fund returns), ESG (scoring, climate/carbon, green bonds, SLL), regulatory capital (Basel III, LCR/NSFR, ALM), compliance (MiFID II best execution, GIPS reporting), credit derivatives (CDS pricing, CVA/DVA), convertible bonds (binomial tree pricing, scenario analysis), lease accounting (ASC 842/IFRS 16, sale-leaseback), pension & LDI (funding analysis, liability-driven investing), sovereign risk (bond analysis, country risk), real options (binomial valuation, decision trees), equity research (SOTP, target price), commodity trading (spread analysis, storage economics), treasury management (cash management, hedge effectiveness), infrastructure finance (PPP models, concession valuation), crypto (token valuation, DeFi analysis), municipal bonds (pricing, credit analysis), structured products (notes, exotic), trade finance (LC, supply chain), fund structuring (US onshore, UK/EU, Cayman/BVI offshore, Luxembourg/Ireland), transfer pricing (BEPS/Pillar Two, intercompany pricing), tax treaty (treaty network optimization, holding structures), FATCA/CRS (reporting, entity classification), economic substance (multi-jurisdiction testing), regulatory reporting (AIFMD Annex IV, SEC Form PF, CFTC CPO-PQR), AML compliance (KYC risk scoring, sanctions screening), fund of funds (J-curve, commitment pacing, manager selection, secondaries pricing), bank analytics (NIM analysis, CAMELS rating, CECL provisioning, deposit beta, loan book), carbon markets (credit pricing, ETS compliance, CBAM, offset valuation, shadow carbon price), private wealth (concentrated stock, philanthropic vehicles, wealth transfer, direct indexing, family governance). All computation uses 128-bit decimal precision.

日本語の概要は準備中です。原文の説明を表示しています。

Summarizes raw background check data into structured executive reports with risk categorization (GREEN/YELLOW/RED). Use when processing criminal records, court filings, employment/education verification, sanctions screening, or adverse media for pre-employment screening, executive due diligence, or investment-grade investigations.

日本語の概要は準備中です。原文の説明を表示しています。

Produces a Rule 506(d) bad actor disqualification review for private securities offerings, including a covered persons register, tailored questionnaires mapping to each disqualifying event category, a documented reasonable-care diligence record, and classification analysis of flagged events with remediation or disclosure recommendations. Use this skill when conducting Rule 506(d) diligence, identifying covered persons for a Regulation D offering, drafting bad actor questionnaires, or analyzing potential disqualifying events involving criminal convictions, SEC orders, SRO sanctions, or state regulatory actions. Also trigger when the user mentions bad actor screening, covered persons analysis, Rule 506(d) questionnaire, disqualification waiver, or reasonable care defense. Even if the user just says "bad actor check" or "506(d) diligence," use this skill.

日本語の概要は準備中です。原文の説明を表示しています。

- Entry point for open-source intelligence, investigation and verification work. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise

日本語の概要は準備中です。原文の説明を表示しています。

- Trace cryptocurrency addresses and transactions on public blockchains using block explorers including Etherscan, Blockchair, mempool.space and Blockscout. Use when following a Bitcoin or Ethereum wallet, investigating where a ransom or scam payment went, or checking an address against sanctions listings

日本語の概要は準備中です。原文の説明を表示しています。

Turn public agenda, news, policy moves, geopolitical developments, sanctions, trade disputes, regulation, elections, diplomatic signals, and strategic-risk events into decision-ready briefs. Use when the user asks an agent to analyze what changed, why it matters, who is affected, what is uncertain, scenarios, watch-next indicators, or risk implications instead of producing a simple news summary.

日本語の概要は準備中です。原文の説明を表示しています。

World-Class Risk Management Playbook. Use for: business continuity planning (BCP), disaster recovery (DR), scenario planning, fraud prevention & detection, reputational risk management, geopolitical risk assessment, insurance & risk transfer, crisis communication, enterprise risk management (ERM), risk registers, BIA, RTO/RPO, ISO 22301, ISO 31000, COSO ERM, NIST CSF, DORA, operational resilience, three lines of defence, risk appetite, internal controls, segregation of duties, synthetic identity fraud, deepfake fraud, AML/CFT, KYC, sanctions screening, social listening, vendor risk, geopolitical exposure mapping, parametric insurance, cyber insurance, D&O, KRIs, risk dashboards. Trigger when discussing ANY risk management, business continuity, disaster recovery, fraud prevention, reputational risk, geopolitical risk, insurance strategy, crisis management, operational resilience, or enterprise risk topic. If in doubt, use this skill.

日本語の概要は準備中です。原文の説明を表示しています。