What problem does it solve? Chrome extensions that declare broad host permissions at install time trigger scary install warnings that drive users away. This Skill shows how to run content scripts on arbitrary third-party pages by requesting host access at runtime instead, avoiding the install-time warning entirely. ## Core Features & Use Cases - Runtime Permission Requests: Declare origins under optional_host_permissions and call chrome.permissions.request() synchronously inside a real foreground user gesture, since Chrome rejects requests from service-worker message handlers. - Dynamic Script Registration: Register content scripts with chrome.scripting.registerContentScripts() instead of static content_scripts manifest entries, using the silent scripting permission. - Grant Reconciliation: On every service worker start, compare your stored enabled-flag against the actually granted permission and re-register or clean up, since users can revoke the grant from chrome://extensions. - Use Case: You are building an extension that reads event details from any web page the user visits. Use this Skill to request site access only when the user clicks your toolbar button, then dynamically inject the content script without ever showing an install-time host warning. ## Quick Start Use the extension-host-permissions skill to set up runtime host permission requests and dynamic content script registration in my Chrome extension manifest.
