Export Compliance & Trade Controls

This skill appears coherent and low-risk in terms of installation and requested privileges, but consider the following before you install or use it: - Data sources: The SKILL.md does not name authoritative sources for SDN/Entity Lists, Country Charts, or the latest EAR/ITAR guidance. Confirm how the agent will obtain up-to-date denied-party lists (official OFAC downloads, government feeds, or a vetted commercial screening API). - Not a substitute for counsel: Use the output as a starting point — always have a qualified export compliance officer or external counsel confirm ECCN classifications and license decisions. - Protect sensitive inputs: You will likely supply product technical details, customer names/addresses, and transaction values. Treat that as sensitive business/PII; avoid pasting highly sensitive technical secrets or export-controlled technical data into an untrusted agent environment. - Auditability: If you rely on the skill for compliance workflows, ensure you have an audit trail (source of denied-party checks, timestamps, and who reviewed the result). - Integration caution: If you plan to connect the agent to networked screening services or commercial watchlist APIs, vet those integrations and their credentials separately — the skill does not request or manage them. If you want higher assurance, ask the skill author to document (a) the authoritative data sources or APIs it expects, and (b) recommended handling for sensitive customer/technical data.