--- name: openclaw-cws-publisher description: OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill. Use it when the user says "chrome web store publisher", "extension release publisher", "CWS publisher", or wants to package and harden a Chrome extension with CWS package, listing, design, local E2E, latest Chrome, competitor, leak, GitHub, and ClawHub gates. version: 0.3.5 homepage: https://github.com/zack-dev-cm/openclaw-cws-publisher license: MIT user-invocable: true metadata: {"openclaw":{"homepage":"https://github.com/zack-dev-cm/openclaw-cws-publisher","skillKey":"openclaw-cws-publisher","requires":{"bins":["git","gh","npx"],"anyBins":["python3","python"]},"install":[{"kind":"brew","label":"Install GitHub CLI","formula":"gh","bins":["gh"]}]}} --- # OpenClaw CWS Publisher Search intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish` ## Goal Prepare a Chrome extension repo for release with less metadata drift: - package the extension - validate the exact ZIP intended for upload against source manifest and CWS listing copy - scan tracked and untracked non-ignored files for obvious leak risks - run local reviewer/E2E gates - enforce design, UI, screenshot, and claim-alignment score gates - enforce storefront media uniqueness so portfolio waves do not reuse the same icon motif, promo layout, visual signature, thumbnail template, or exact asset - enforce public landing, privacy, support, reviewer, SEO, and Cloudflare canonical-page gates before dashboard submission - check current Chrome Stable release data before declaring E2E coverage fresh - run a lightweight competitor and positioning differentiation check - require a repo-local product-share/traffic-source gate when present, before treating a new extension as submission-ready - detect repo-local reviewer gates - generate GitHub metadata - generate optional ClawHub metadata and explicit tags - render reproducible publish commands ## Use This Skill When - the user wants a Chrome extension repo prepared for GitHub release - the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission - the user wants ClawHub tags and GitHub topics kept in sync - the user wants a leakage check before public release - the user already has a specific repo path to release ## Companion Scripts The public ClawHub artifact is instruction-only so install-gate audits can return `PASS`. When the companion repository is available, set: ```bash export OPENCLAW_CWS_PUBLISHER_DIR=/path/to/openclaw-cws-publisher/scripts/openclaw-cws-publisher ``` Then use `$OPENCLAW_CWS_PUBLISHER_DIR/

OpenClaw CWS Publisher

Description

Latest Changes

Install OpenClaw CWS Publisher with One Click