What problem does it solve? Publishing or monetizing AI skills without centralized security and IP rules leads to duplicated policies, trademark violations, missing disclaimers, and unsafe third-party code. This Skill provides one canonical gate where all safety and compliance rules live, so other skills reference them instead of duplicating them. ## Core Features & Use Cases - Operate-time security posture: Treats connector and web content as untrusted input, requires human confirmation for side-effect tools, and guards against confused-deputy and prompt-injection risks. - Ship-time IP and publication checks: Enforces trademark-safe naming conventions, mandatory non-affiliation disclaimers, no third-party logos, explicit licenses, and elevated review before monetization. - Intake-time supply-chain audit: Requires line-by-line review of external skills with scripts or hooks, version pinning, and harvesting ideas rather than blindly enabling foreign code. - Use Case: Before uploading a connector skill named after a third-party product to a marketplace, run the gate checklist to verify the descriptive name, disclaimer, license, and brand-guideline compliance, blocking publication until every item passes. ## Quick Start Ask the assistant to run the safety and compliance gate before packaging and publishing your skill to GitHub or a marketplace.