Ext Desk - clear a browser extension for the Chrome Web Store

Paste your extension's manifest.json - and the service worker, content scripts and extension pages beside it - and work that same bundle through four lanes: a Manifest V3 and least-privilege permission audit that goes key by key, a service-worker lifecycle pass that replays an eviction against every listener, a content-script pass that costs what your injection does to every page it runs on, and a Chrome Web Store submission pack that writes the single-purpose statement and one justification per permission. A free in-browser reader parses the manifest the way Chrome's loader does first: it catches the comment and the trailing comma Chrome rejects outright, validates every match pattern, names the permission your code never calls and the chrome.* API you call with no permission behind it, and shows the install warning each permission puts in front of the user. A derived work built on four agent skills about building browser extensions: @xenitv1/browser-extension, @sickn33/chrome-extension-developer, @pproenca/chrome-extension and @davila7/browser-extension-builder.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.