Connect an extension
Adds hosted pages and install/uninstall links, then checks the first events without a backend of your own.
The skill teaches Codex what Ext Ops Panel does, how an extension is connected and how the API contracts differ. It takes you from project settings to a verified result.
Adds hosted pages and install/uninstall links, then checks the first events without a backend of your own.
Tells public Market and listing data apart from your project data, feedback and analytics.
Points to the contracts for custom metrics, the feedback widget, the customer card endpoint, uptime pings and heartbeat.
Checks payloads, versions and authorization against the current OpenAPI and your project code.
Walks you through verifying your extension or AI plugin, turning on consent and placing the author banner on your site or in a README.
ext-ops-panel folder with instructions and reference files.~/.codex/skills/ so the path is ~/.codex/skills/ext-ops-panel/SKILL.md.$ext-ops-panel explicitly.The archive contains text instructions only. Do not add tokens or account settings to it.
Use $ext-ops-panel. Connect my Chrome extension to Ext Ops Panel:
add welcome and uninstall, check Manifest V3 and show me
how to verify the events in the panel. Take the URLs from my project settings.The skill holds none of your URLs, keys or tokens. Codex takes them from the current project and checks the integration against the guide and the public contracts.
A second, separate skill for Claude and Codex: given an extension name or a Chrome Web Store link, it finds the listing in the public catalog on extops.dev and reports its audience, rating, permissions and how they changed, with a dated link to the page. No account, key or API.
Unzip it so the path is ~/.claude/skills/check-extension/SKILL.md for Claude Code or ~/.codex/skills/check-extension/SKILL.md for Codex.
Check this extension before I install it:
https://chromewebstore.google.com/detail/<name>/<id>