{"id":"6ffc5ad5-4d0d-4a16-9b28-1e0047adf336","entityType":"agent","slug":"clawhub-zack-dev-cm-openclaw-cws-publisher","name":"OpenClaw CWS Publisher","canonicalUrl":"https://www.xpersona.co/agent/clawhub-zack-dev-cm-openclaw-cws-publisher","canonicalPath":"/agent/clawhub-zack-dev-cm-openclaw-cws-publisher","generatedAt":"2026-10-10T23:46:44.200Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":null},"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 publi...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s170hyv1nagjajq3y5c6kpzx3s84jp29:openclaw-cws-publisher","sourceUrl":"https://clawhub.ai/zack-dev-cm/openclaw-cws-publisher","homepage":"https://clawhub.ai/zack-dev-cm/skills/openclaw-cws-publisher","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/zack-dev-cm/openclaw-cws-publisher","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/zack-dev-cm/skills/openclaw-cws-publisher","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"OpenClaw CWS Publisher technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":null},"stars":null,"forks":null,"downloads":1276,"packageName":null,"latestVersion":"0.3.5","tractionLabel":"1.3K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T19:46:19.761Z","lastCrawledAt":"2026-10-10T19:46:19.761Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T19:46:19.761Z","lastVerifiedAt":null,"highlights":[{"version":"0.3.5","createdAt":"2026-05-15T08:01:56.971Z","changelog":"Make public skill package instruction-only for install-gate PASS and move helper scripts to companion repo path.","fileCount":5,"zipByteSize":7032},{"version":"0.3.3","createdAt":"2026-05-06T16:35:45.561Z","changelog":"Add Cloudflare public-page, SEO, privacy, reviewer, and design evidence gates for CWS release readiness","fileCount":13,"zipByteSize":22697},{"version":"0.3.2","createdAt":"2026-05-03T23:59:21.111Z","changelog":"Harden generated publish guidance: scan tracked and untracked non-ignored files, require reviewed-file staging, remove auto-push, and pin the ClawHub CLI command.","fileCount":13,"zipByteSize":22285},{"version":"0.3.1","createdAt":"2026-05-03T23:53:58.656Z","changelog":"Redact secret-like and local-only matches in publish-surface reports so leak scans do not copy sensitive values.","fileCount":13,"zipByteSize":22180},{"version":"0.3.0","createdAt":"2026-05-01T07:12:03.420Z","changelog":"Add CWS ZIP/listing validation, local E2E discovery, design/UI gates, Chrome Stable checks, competitor checks, and hardening publish preflights.","fileCount":13,"zipByteSize":21447},{"version":"0.2.5","createdAt":"2026-04-30T02:35:57.366Z","changelog":"Reviewed source and refreshed public ClawHub skill surface.","fileCount":8,"zipByteSize":8689},{"version":"0.2.4","createdAt":"2026-04-25T17:46:28.562Z","changelog":"Fix runtime requirement metadata so Git, GitHub CLI, npx, and Python alternatives are represented correctly.","fileCount":8,"zipByteSize":8688},{"version":"0.2.3","createdAt":"2026-04-24T13:07:13.521Z","changelog":"Refresh public skill metadata for GitHub and ClawHub release sync.","fileCount":8,"zipByteSize":8635}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s170hyv1nagjajq3y5c6kpzx3s84jp29:openclaw-cws-publisher","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s170hyv1nagjajq3y5c6kpzx3s84jp29:openclaw-cws-publisher` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/zack-dev-cm/openclaw-cws-publisher before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T23:46:44.197Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-zack-dev-cm-openclaw-cws-publisher/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":null},"readme":"Skill: OpenClaw CWS Publisher\n\nOwner: zack-dev-cm\n\nSummary: OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill. Use it when the user says \"chrome web store publisher\", \"extension release publi...\n\nTags: browser-automation:0.3.5, chrome-extension:0.3.5, chrome-web-store:0.3.5, cloudflare:0.3.5, design-gates:0.3.5, latest:0.3.5, local-e2e:0.3.5, openclaw:0.3.5, privacy:0.3.5, release-automation:0.3.5, release-checks:0.3.5, seo:0.3.5\n\nVersion history:\n\nv0.3.5 | 2026-05-15T08:01:56.971Z | user\n\nMake public skill package instruction-only for install-gate PASS and move helper scripts to companion repo path.\n\nv0.3.3 | 2026-05-06T16:35:45.561Z | user\n\nAdd Cloudflare public-page, SEO, privacy, reviewer, and design evidence gates for CWS release readiness\n\nv0.3.2 | 2026-05-03T23:59:21.111Z | user\n\nHarden generated publish guidance: scan tracked and untracked non-ignored files, require reviewed-file staging, remove auto-push, and pin the ClawHub CLI command.\n\nv0.3.1 | 2026-05-03T23:53:58.656Z | user\n\nRedact secret-like and local-only matches in publish-surface reports so leak scans do not copy sensitive values.\n\nv0.3.0 | 2026-05-01T07:12:03.420Z | user\n\nAdd CWS ZIP/listing validation, local E2E discovery, design/UI gates, Chrome Stable checks, competitor checks, and hardening publish preflights.\n\nv0.2.5 | 2026-04-30T02:35:57.366Z | user\n\nReviewed source and refreshed public ClawHub skill surface.\n\nv0.2.4 | 2026-04-25T17:46:28.562Z | user\n\nFix runtime requirement metadata so Git, GitHub CLI, npx, and Python alternatives are represented correctly.\n\nv0.2.3 | 2026-04-24T13:07:13.521Z | user\n\nRefresh public skill metadata for GitHub and ClawHub release sync.\n\nv0.2.2 | 2026-04-22T12:48:45.704Z | user\n\nAdd reviewer-gate preflight and pending-review safeguards.\n\nv0.2.1 | 2026-04-17T08:18:35.986Z | user\n\nAdd public-site-base support for reviewer-facing support, privacy, and test-instructions links.\n\nv0.2.0 | 2026-04-15T17:12:36.167Z | user\n\nSplit LocalLens out and narrow the public release kit.\n\nv0.1.2 | 2026-04-15T14:02:54.730Z | user\n\nAdd GitHub metadata defaults and explicit ClawHub tags.\n\nv0.1.1 | 2026-04-15T08:05:58.528Z | user\n\nFix inventory matching, stale asset invalidation, and publish metadata.\n\nv0.1.0 | 2026-04-15T06:28:53.855Z | user\n\nInitial public release.\n\nArchive index:\n\nArchive v0.3.5: 5 files, 7032 bytes\n\nFiles: agents/openai.yaml (964b), LICENSE (1061b), skill-card.md (2828b), SKILL.md (10230b), _meta.json (141b)\n\nFile v0.3.5:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.5\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked and untracked non-ignored files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- enforce storefront media uniqueness so portfolio waves do not reuse the same\n  icon motif, promo layout, visual signature, thumbnail template, or exact asset\n- enforce public landing, privacy, support, reviewer, SEO, and Cloudflare\n  canonical-page gates before dashboard submission\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- require a repo-local product-share/traffic-source gate when present, before\n  treating a new extension as submission-ready\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Companion Scripts\n\nThe public ClawHub artifact is instruction-only so install-gate audits can return `PASS`.\nWhen the companion repository is available, set:\n\n```bash\nexport OPENCLAW_CWS_PUBLISHER_DIR=/path/to/openclaw-cws-publisher/scripts/openclaw-cws-publisher\n```\n\nThen use `$OPENCLAW_CWS_PUBLISHER_DIR/<script>.py` in the commands below.\n\n## Operating Order\n\n1. Run the repo-local product-share gate when present.\n   - Example: `npm run check:product-share` or `python3 scripts/check_product_share_gate.py --product <slug>`\n   - Block submission when the first traffic source, trust reason, share moment,\n     free MVP window, 30-60 day kill criteria, or ecosystem path is missing.\n2. Build the extension ZIP intended for upload.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/build_extension_zip.py\" --extension-dir <repo>/extension --out <zip>`\n3. Validate the exact ZIP, source manifest, and listing contract.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/validate_cws_package.py\" --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json`\n   - Default posture blocks stale ZIPs, Manifest V2, `tabs`, `debugger`, `<all_urls>`, persistent host permissions, declarative content scripts, remote script/eval patterns, missing permission justifications, privacy-practice drift, and no-host ZIPs whose listing still carries host-permission copy.\n   - If a product genuinely needs host permissions, use `--allow-host-permissions` only after the listing and reviewer instructions explain the shipped user-facing need.\n4. Scan tracked and untracked non-ignored files for obvious publish leaks.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/scan_publish_surface.py\" --root <repo> --json-out <json> --markdown-out <md>`\n5. Run local reviewer/E2E gates.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/run_local_e2e_gates.py\" --repo-root <repo> --json-out <json> --markdown-out <md>`\n   - The script discovers `check:cws`, `check:public`, `check:public:visual`, `test:e2e:reviewer`, `test:e2e`, and `scripts/reviewer_gate.py` when present.\n6. Enforce the design/UI/UX evidence gate.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/check_design_gate.py\" --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json`\n   - Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least `8/10` for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.\n   - For multi-extension or portfolio submissions, `docs/design-gate.json` must\n     include `media_identities` with unique `icon_motif`, `promo_layout`, and\n     `visual_signature` values plus store-icon, small-promo, and marquee-promo\n     asset paths for each item. Recolored copies of the same thumbnail template\n     are a blocker even when dimensions and basic scores pass.\n7. Enforce public landing and SEO gates.\n   - The CWS-facing site must have a polished product-first landing page, a\n     readable privacy policy, support page, reviewer guide, robots.txt,\n     sitemap.xml, canonical URLs, Open Graph/Twitter metadata, and factual\n     SoftwareApplication JSON-LD when applicable.\n   - Prefer Cloudflare Pages or another owned HTTPS host as the canonical CWS\n     listing surface. GitHub source-viewer URLs and temporary fallback mirrors\n     must not remain in active listing metadata.\n   - Block submission when SEO metadata points to an old domain, when public\n     pages look like policy stubs, or when privacy/support/reviewer pages do\n     not reflect the exact package permissions and user-data behavior.\n8. Check current Chrome Stable release data.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/check_chrome_release.py\" --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>`\n   - Source: Chrome for Testing last-known-good Stable feed, cross-checked with ChromiumDash, Chrome Releases, and Chrome for Developers release notes when making decisions.\n9. Run a competitor/differentiation check.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/check_competitors.py\" --listing-json <repo>/docs/cws/listing.json --competitors-json <repo>/docs/cws/competitors.json --min-competitors 3 --markdown-out <md>`\n   - Record at least three comparable products or explicit substitutes; flag risky claims like `#1`, `best`, `official`, and close-copy positioning.\n10. Generate launch metadata.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/generate_launch_manifest.py\" --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n11. Render publish commands.\n   - `python3 \"$OPENCLAW_CWS_PUBLISHER_DIR/render_publish_commands.py\" --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Prefer `activeTab` plus `scripting` after an explicit user gesture over persistent host permissions.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish a new product when a repo-local product-share gate is missing,\n  failing, or says `rework`, `park`, or `kill`.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.\n- Do not publish when the design/UI gate is missing or any score is below `8/10`.\n- Do not publish when a store icon, small promo tile, marquee promo tile, or\n  portfolio thumbnail reuses another product's motif/layout/signature or exact\n  asset bytes.\n- Do not publish when public SEO/canonical metadata is missing, points at a\n  fallback domain, or contradicts the CWS listing contract.\n- Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.\n- Do not publish listing copy that claims official affiliation, best-in-class status, background crawling, server sync, or broad permissions unless the shipped product and public evidence prove it.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Current Policy Anchors\n\n- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies\n- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements\n- `activeTab` plus `scripting` model: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab\n- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions\n- Chrome release notes: https://developer.chrome.com/release-notes/\n- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases\n\n## Companion Repo Scripts\n\n- `scripts/openclaw-cws-publisher/build_extension_zip.py`\n- `scripts/openclaw-cws-publisher/validate_cws_package.py`\n- `scripts/openclaw-cws-publisher/scan_publish_surface.py`\n- `scripts/openclaw-cws-publisher/run_local_e2e_gates.py`\n- `scripts/openclaw-cws-publisher/check_design_gate.py`\n- `scripts/openclaw-cws-publisher/check_chrome_release.py`\n- `scripts/openclaw-cws-publisher/check_competitors.py`\n- `scripts/openclaw-cws-publisher/generate_launch_manifest.py`\n- `scripts/openclaw-cws-publisher/render_publish_commands.py`\n\nFile v0.3.5:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.5\",\n  \"publishedAt\": 1778832116971\n}\n\nFile v0.3.5:skill-card.md\n\n## Description:\n\nOpenClaw CWS Publisher helps agents package and harden Chrome extensions for Chrome Web Store release with package, listing, design, local E2E, Chrome release, competitor, leak, GitHub, and ClawHub gates.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zack-dev-cm](https://clawhub.ai/user/zack-dev-cm)\n\n### License/Terms of Use:\n\nMIT\n\n## Use Case:\n\nDevelopers and release engineers use this skill to prepare a specific Chrome extension repository for Chrome Web Store submission by checking package contents, listing consistency, public-site readiness, leak risk, local review gates, and launch metadata.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The wrong repository path or extension ZIP could be assessed for release.\n\nMitigation: Confirm the target repo path and exact ZIP before treating the output as Chrome Web Store submission guidance.\n\nRisk: The public skill artifact depends on separately supplied companion scripts.\n\nMitigation: Review any companion scripts referenced by OPENCLAW_CWS_PUBLISHER_DIR before executing proposed commands.\n\nRisk: Leak scans may inspect tracked and untracked non-ignored files in the target repository.\n\nMitigation: Review scan scope and remove or ignore sensitive local files before running publication checks.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zack-dev-cm/skills/openclaw-cws-publisher)\n- [Project homepage](https://github.com/zack-dev-cm/openclaw-cws-publisher)\n- [Chrome Web Store Program Policies](https://developer.chrome.com/docs/webstore/program-policies/policies)\n- [Manifest V3 remote-code requirements](https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements)\n- [Chrome extension activeTab model](https://developer.chrome.com/docs/extensions/develop/concepts/activeTab)\n- [Chrome extension permission warnings](https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions)\n- [Chrome release notes](https://developer.chrome.com/release-notes/)\n- [ChromiumDash release feed](https://chromiumdash.appspot.com/fetch_releases)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and configuration references]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May reference separately supplied companion scripts and repo-local release evidence.]\n\n## Skill Version(s):\n\n0.3.5 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.3.5:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If using the companion repo scripts, set OPENCLAW_CWS_PUBLISHER_DIR to scripts/openclaw-cws-publisher. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nFile v0.3.5:LICENSE\n\nMIT License\n\nCopyright (c) 2026 Zack\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\nArchive v0.3.3: 13 files, 22697 bytes\n\nFiles: agents/openai.yaml (861b), scripts/build_extension_zip.py (1078b), scripts/check_chrome_release.py (6649b), scripts/check_competitors.py (6463b), scripts/check_design_gate.py (4215b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (4452b), scripts/run_local_e2e_gates.py (4926b), scripts/scan_publish_surface.py (3709b), scripts/validate_cws_package.py (9904b), SKILL.md (8273b), _meta.json (141b)\n\nFile v0.3.3:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.3\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked and untracked non-ignored files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- enforce public landing, privacy, support, reviewer, SEO, and Cloudflare\n  canonical-page gates before dashboard submission\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP intended for upload.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Validate the exact ZIP, source manifest, and listing contract.\n   - `python3 {baseDir}/scripts/validate_cws_package.py --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json`\n   - Default posture blocks stale ZIPs, Manifest V2, `tabs`, `debugger`, `<all_urls>`, persistent host permissions, declarative content scripts, remote script/eval patterns, missing permission justifications, privacy-practice drift, and no-host ZIPs whose listing still carries host-permission copy.\n   - If a product genuinely needs host permissions, use `--allow-host-permissions` only after the listing and reviewer instructions explain the shipped user-facing need.\n3. Scan tracked and untracked non-ignored files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n4. Run local reviewer/E2E gates.\n   - `python3 {baseDir}/scripts/run_local_e2e_gates.py --repo-root <repo> --json-out <json> --markdown-out <md>`\n   - The script discovers `check:cws`, `check:public`, `check:public:visual`, `test:e2e:reviewer`, `test:e2e`, and `scripts/reviewer_gate.py` when present.\n5. Enforce the design/UI/UX evidence gate.\n   - `python3 {baseDir}/scripts/check_design_gate.py --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json`\n   - Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least `8/10` for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.\n6. Enforce public landing and SEO gates.\n   - The CWS-facing site must have a polished product-first landing page, a\n     readable privacy policy, support page, reviewer guide, robots.txt,\n     sitemap.xml, canonical URLs, Open Graph/Twitter metadata, and factual\n     SoftwareApplication JSON-LD when applicable.\n   - Prefer Cloudflare Pages or another owned HTTPS host as the canonical CWS\n     listing surface. GitHub source-viewer URLs and temporary fallback mirrors\n     must not remain in active listing metadata.\n   - Block submission when SEO metadata points to an old domain, when public\n     pages look like policy stubs, or when privacy/support/reviewer pages do\n     not reflect the exact package permissions and user-data behavior.\n7. Check current Chrome Stable release data.\n   - `python3 {baseDir}/scripts/check_chrome_release.py --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>`\n   - Source: Chrome for Testing last-known-good Stable feed, cross-checked with ChromiumDash, Chrome Releases, and Chrome for Developers release notes when making decisions.\n8. Run a competitor/differentiation check.\n   - `python3 {baseDir}/scripts/check_competitors.py --listing-json <repo>/docs/cws/listing.json --competitors-json <repo>/docs/cws/competitors.json --min-competitors 3 --markdown-out <md>`\n   - Record at least three comparable products or explicit substitutes; flag risky claims like `#1`, `best`, `official`, and close-copy positioning.\n9. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n10. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Prefer `activeTab` plus `scripting` after an explicit user gesture over persistent host permissions.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.\n- Do not publish when the design/UI gate is missing or any score is below `8/10`.\n- Do not publish when public SEO/canonical metadata is missing, points at a\n  fallback domain, or contradicts the CWS listing contract.\n- Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.\n- Do not publish listing copy that claims official affiliation, best-in-class status, background crawling, server sync, or broad permissions unless the shipped product and public evidence prove it.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Current Policy Anchors\n\n- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies\n- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements\n- `activeTab` plus `scripting` model: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab\n- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions\n- Chrome release notes: https://developer.chrome.com/release-notes/\n- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/validate_cws_package.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/run_local_e2e_gates.py`\n- `scripts/check_design_gate.py`\n- `scripts/check_chrome_release.py`\n- `scripts/check_competitors.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.3.3:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.3\",\n  \"publishedAt\": 1778085345561\n}\n\nFile v0.3.3:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.3.2: 13 files, 22285 bytes\n\nFiles: agents/openai.yaml (861b), scripts/build_extension_zip.py (1078b), scripts/check_chrome_release.py (6649b), scripts/check_competitors.py (6463b), scripts/check_design_gate.py (4215b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (4452b), scripts/run_local_e2e_gates.py (4926b), scripts/scan_publish_surface.py (3709b), scripts/validate_cws_package.py (9904b), SKILL.md (7266b), _meta.json (141b)\n\nFile v0.3.2:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.2\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked and untracked non-ignored files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP intended for upload.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Validate the exact ZIP, source manifest, and listing contract.\n   - `python3 {baseDir}/scripts/validate_cws_package.py --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json`\n   - Default posture blocks stale ZIPs, Manifest V2, `tabs`, `debugger`, `<all_urls>`, persistent host permissions, declarative content scripts, remote script/eval patterns, missing permission justifications, privacy-practice drift, and no-host ZIPs whose listing still carries host-permission copy.\n   - If a product genuinely needs host permissions, use `--allow-host-permissions` only after the listing and reviewer instructions explain the shipped user-facing need.\n3. Scan tracked and untracked non-ignored files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n4. Run local reviewer/E2E gates.\n   - `python3 {baseDir}/scripts/run_local_e2e_gates.py --repo-root <repo> --json-out <json> --markdown-out <md>`\n   - The script discovers `check:cws`, `check:public`, `check:public:visual`, `test:e2e:reviewer`, `test:e2e`, and `scripts/reviewer_gate.py` when present.\n5. Enforce the design/UI/UX evidence gate.\n   - `python3 {baseDir}/scripts/check_design_gate.py --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json`\n   - Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least `8/10` for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.\n6. Check current Chrome Stable release data.\n   - `python3 {baseDir}/scripts/check_chrome_release.py --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>`\n   - Source: Chrome for Testing last-known-good Stable feed, cross-checked with ChromiumDash, Chrome Releases, and Chrome for Developers release notes when making decisions.\n7. Run a competitor/differentiation check.\n   - `python3 {baseDir}/scripts/check_competitors.py --listing-json <repo>/docs/cws/listing.json --competitors-json <repo>/docs/cws/competitors.json --min-competitors 3 --markdown-out <md>`\n   - Record at least three comparable products or explicit substitutes; flag risky claims like `#1`, `best`, `official`, and close-copy positioning.\n8. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n9. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Prefer `activeTab` plus `scripting` after an explicit user gesture over persistent host permissions.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.\n- Do not publish when the design/UI gate is missing or any score is below `8/10`.\n- Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.\n- Do not publish listing copy that claims official affiliation, best-in-class status, background crawling, server sync, or broad permissions unless the shipped product and public evidence prove it.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Current Policy Anchors\n\n- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies\n- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements\n- `activeTab` plus `scripting` model: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab\n- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions\n- Chrome release notes: https://developer.chrome.com/release-notes/\n- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/validate_cws_package.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/run_local_e2e_gates.py`\n- `scripts/check_design_gate.py`\n- `scripts/check_chrome_release.py`\n- `scripts/check_competitors.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.3.2:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.2\",\n  \"publishedAt\": 1777852761111\n}\n\nFile v0.3.2:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.3.1: 13 files, 22180 bytes\n\nFiles: agents/openai.yaml (861b), scripts/build_extension_zip.py (1078b), scripts/check_chrome_release.py (6649b), scripts/check_competitors.py (6463b), scripts/check_design_gate.py (4215b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (4369b), scripts/run_local_e2e_gates.py (4926b), scripts/scan_publish_surface.py (3632b), scripts/validate_cws_package.py (9904b), SKILL.md (7214b), _meta.json (141b)\n\nFile v0.3.1:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.1\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP intended for upload.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Validate the exact ZIP, source manifest, and listing contract.\n   - `python3 {baseDir}/scripts/validate_cws_package.py --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json`\n   - Default posture blocks stale ZIPs, Manifest V2, `tabs`, `debugger`, `<all_urls>`, persistent host permissions, declarative content scripts, remote script/eval patterns, missing permission justifications, privacy-practice drift, and no-host ZIPs whose listing still carries host-permission copy.\n   - If a product genuinely needs host permissions, use `--allow-host-permissions` only after the listing and reviewer instructions explain the shipped user-facing need.\n3. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n4. Run local reviewer/E2E gates.\n   - `python3 {baseDir}/scripts/run_local_e2e_gates.py --repo-root <repo> --json-out <json> --markdown-out <md>`\n   - The script discovers `check:cws`, `check:public`, `check:public:visual`, `test:e2e:reviewer`, `test:e2e`, and `scripts/reviewer_gate.py` when present.\n5. Enforce the design/UI/UX evidence gate.\n   - `python3 {baseDir}/scripts/check_design_gate.py --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json`\n   - Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least `8/10` for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.\n6. Check current Chrome Stable release data.\n   - `python3 {baseDir}/scripts/check_chrome_release.py --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>`\n   - Source: Chrome for Testing last-known-good Stable feed, cross-checked with ChromiumDash, Chrome Releases, and Chrome for Developers release notes when making decisions.\n7. Run a competitor/differentiation check.\n   - `python3 {baseDir}/scripts/check_competitors.py --listing-json <repo>/docs/cws/listing.json --competitors-json <repo>/docs/cws/competitors.json --min-competitors 3 --markdown-out <md>`\n   - Record at least three comparable products or explicit substitutes; flag risky claims like `#1`, `best`, `official`, and close-copy positioning.\n8. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n9. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Prefer `activeTab` plus `scripting` after an explicit user gesture over persistent host permissions.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.\n- Do not publish when the design/UI gate is missing or any score is below `8/10`.\n- Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.\n- Do not publish listing copy that claims official affiliation, best-in-class status, background crawling, server sync, or broad permissions unless the shipped product and public evidence prove it.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Current Policy Anchors\n\n- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies\n- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements\n- `activeTab` plus `scripting` model: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab\n- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions\n- Chrome release notes: https://developer.chrome.com/release-notes/\n- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/validate_cws_package.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/run_local_e2e_gates.py`\n- `scripts/check_design_gate.py`\n- `scripts/check_chrome_release.py`\n- `scripts/check_competitors.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.3.1:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.1\",\n  \"publishedAt\": 1777852438656\n}\n\nFile v0.3.1:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.3.0: 13 files, 21447 bytes\n\nFiles: agents/openai.yaml (861b), scripts/build_extension_zip.py (1078b), scripts/check_chrome_release.py (4701b), scripts/check_competitors.py (6463b), scripts/check_design_gate.py (4215b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (4369b), scripts/run_local_e2e_gates.py (4926b), scripts/scan_publish_surface.py (3193b), scripts/validate_cws_package.py (9904b), SKILL.md (7185b), _meta.json (141b)\n\nFile v0.3.0:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.0\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP intended for upload.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Validate the exact ZIP, source manifest, and listing contract.\n   - `python3 {baseDir}/scripts/validate_cws_package.py --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json`\n   - Default posture blocks stale ZIPs, Manifest V2, `tabs`, `debugger`, `<all_urls>`, persistent host permissions, declarative content scripts, remote script/eval patterns, missing permission justifications, privacy-practice drift, and no-host ZIPs whose listing still carries host-permission copy.\n   - If a product genuinely needs host permissions, use `--allow-host-permissions` only after the listing and reviewer instructions explain the shipped user-facing need.\n3. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n4. Run local reviewer/E2E gates.\n   - `python3 {baseDir}/scripts/run_local_e2e_gates.py --repo-root <repo> --json-out <json> --markdown-out <md>`\n   - The script discovers `check:cws`, `check:public`, `check:public:visual`, `test:e2e:reviewer`, `test:e2e`, and `scripts/reviewer_gate.py` when present.\n5. Enforce the design/UI/UX evidence gate.\n   - `python3 {baseDir}/scripts/check_design_gate.py --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json`\n   - Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least `8/10` for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.\n6. Check current Chrome Stable release data.\n   - `python3 {baseDir}/scripts/check_chrome_release.py --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>`\n   - Source: ChromiumDash Stable release feed, cross-checked with Chrome Releases and Chrome for Developers release notes when making decisions.\n7. Run a competitor/differentiation check.\n   - `python3 {baseDir}/scripts/check_competitors.py --listing-json <repo>/docs/cws/listing.json --competitors-json <repo>/docs/cws/competitors.json --min-competitors 3 --markdown-out <md>`\n   - Record at least three comparable products or explicit substitutes; flag risky claims like `#1`, `best`, `official`, and close-copy positioning.\n8. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n9. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Prefer `activeTab` plus `scripting` after an explicit user gesture over persistent host permissions.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.\n- Do not publish when the design/UI gate is missing or any score is below `8/10`.\n- Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.\n- Do not publish listing copy that claims official affiliation, best-in-class status, background crawling, server sync, or broad permissions unless the shipped product and public evidence prove it.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Current Policy Anchors\n\n- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies\n- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements\n- `activeTab` plus `scripting` model: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab\n- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions\n- Chrome release notes: https://developer.chrome.com/release-notes/\n- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/validate_cws_package.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/run_local_e2e_gates.py`\n- `scripts/check_design_gate.py`\n- `scripts/check_chrome_release.py`\n- `scripts/check_competitors.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.3.0:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.0\",\n  \"publishedAt\": 1777619523420\n}\n\nFile v0.3.0:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.2.5: 8 files, 8689 bytes\n\nFiles: agents/openai.yaml (667b), scripts/build_extension_zip.py (1078b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (2854b), scripts/scan_publish_surface.py (3193b), SKILL.md (3171b), _meta.json (141b)\n\nFile v0.2.5:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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 a Chrome extension, scan tracked files for public-surface leaks, and render GitHub or ClawHub release metadata with explicit tags.\nversion: 0.2.5\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- scan tracked files for obvious leak risks\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n3. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n4. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.2.5:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.2.5\",\n  \"publishedAt\": 1777516557366\n}\n\nFile v0.2.5:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package Chrome extensions, scan tracked files, and render GitHub or ClawHub release commands with explicit tags\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory, scan tracked files for public-surface leaks, detect any repo-local reviewer gate, generate launch metadata for the target repo, and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.2.4: 8 files, 8688 bytes\n\nFiles: agents/openai.yaml (667b), scripts/build_extension_zip.py (1078b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (2854b), scripts/scan_publish_surface.py (3193b), SKILL.md (3171b), _meta.json (141b)\n\nFile v0.2.4:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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 a Chrome extension, scan tracked files for public-surface leaks, and render GitHub or ClawHub release metadata with explicit tags.\nversion: 0.2.4\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- scan tracked files for obvious leak risks\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n3. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n4. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.2.4:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.2.4\",\n  \"publishedAt\": 1777139188562\n}\n\nFile v0.2.4:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package Chrome extensions, scan tracked files, and render GitHub or ClawHub release commands with explicit tags\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory, scan tracked files for public-surface leaks, detect any repo-local reviewer gate, generate launch metadata for the target repo, and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.2.3: 8 files, 8635 bytes\n\nFiles: agents/openai.yaml (667b), scripts/build_extension_zip.py (1078b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (2854b), scripts/scan_publish_surface.py (3193b), SKILL.md (3071b), _meta.json (141b)\n\nFile v0.2.3:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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 a Chrome extension, scan tracked files for public-surface leaks, and render GitHub or ClawHub release metadata with explicit tags.\nversion: 0.2.3\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"openclaw\":{\"homepage\":\"https://github.com/zack-dev-cm/openclaw-cws-publisher\",\"skillKey\":\"openclaw-cws-publisher\",\"requires\":{\"anyBins\":[\"python3\",\"git\",\"gh\",\"clawhub\"]}}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- scan tracked files for obvious leak risks\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n3. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n4. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.2.3:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.2.3\",\n  \"publishedAt\": 1777036033521\n}\n\nFile v0.2.3:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package Chrome extensions, scan tracked files, and render GitHub or ClawHub release commands with explicit tags\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory, scan tracked files for public-surface leaks, detect any repo-local reviewer gate, generate launch metadata for the target repo, and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.2.2: 8 files, 8635 bytes\n\nFiles: agents/openai.yaml (667b), scripts/build_extension_zip.py (1078b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (6282b), scripts/render_publish_commands.py (2854b), scripts/scan_publish_surface.py (3193b), SKILL.md (3071b), _meta.json (141b)\n\nFile v0.2.2:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: 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 a Chrome extension, scan tracked files for public-surface leaks, and render GitHub or ClawHub release metadata with explicit tags.\nversion: 0.2.2\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"openclaw\":{\"homepage\":\"https://github.com/zack-dev-cm/openclaw-cws-publisher\",\"skillKey\":\"openclaw-cws-publisher\",\"requires\":{\"anyBins\":[\"python3\",\"git\",\"gh\",\"clawhub\"]}}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- scan tracked files for obvious leak risks\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n3. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n4. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.\n- Do not publish when the leak scan has unresolved findings.\n- Do not publish when the target repo has a reviewer gate and it fails.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.\n- Do not assume generated artifacts should be committed.\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.2.2:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.2.2\",\n  \"publishedAt\": 1776862125704\n}\n\nFile v0.2.2:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package Chrome extensions, scan tracked files, and render GitHub or ClawHub release commands with explicit tags\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory, scan tracked files for public-surface leaks, detect any repo-local reviewer gate, generate launch metadata for the target repo, and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"\n\nArchive v0.2.1: 8 files, 7976 bytes\n\nFiles: agents/openai.yaml (630b), scripts/build_extension_zip.py (1078b), scripts/common.py (1995b), scripts/generate_launch_manifest.py (5802b), scripts/render_publish_commands.py (2137b), scripts/scan_publish_surface.py (3193b), SKILL.md (2376b), _meta.json (141b)\n\nFile v0.2.1:SKILL.md\n\n---\nname: openclaw-cws-publisher\ndescription: Package a Chrome extension, scan tracked files for public-surface leaks, and render GitHub or ClawHub release metadata with explicit tags.\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"openclaw\":{\"homepage\":\"https://github.com/zack-dev-cm/openclaw-cws-publisher\",\"skillKey\":\"openclaw-cws-publisher\",\"requires\":{\"anyBins\":[\"python3\",\"git\",\"gh\",\"clawhub\"]}}}\n---\n\n# OpenClaw CWS Publisher\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- scan tracked files for obvious leak risks\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Operating Order\n\n1. Build the extension ZIP.\n   - `python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>`\n2. Scan tracked files for obvious publish leaks.\n   - `python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>`\n3. Generate launch metadata.\n   - `python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>`\n   - If you already export `CWS_PUBLIC_SITE_BASE`, you can omit `--public-site-base` and the script will reuse that public reviewer-facing base.\n4. Render publish commands.\n   - `python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>`\n\n## Rules\n\n- Operate on the repo path the user named, not on arbitrary sibling directories.\n- Do not publish when the leak scan has unresolved findings.\n- Keep GitHub topics and ClawHub tags explicit in the generated manifest.\n- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.\n- Do not assume generated artifacts should be committed.\n\n## Bundled Scripts\n\n- `scripts/build_extension_zip.py`\n- `scripts/scan_publish_surface.py`\n- `scripts/generate_launch_manifest.py`\n- `scripts/render_publish_commands.py`\n\nFile v0.2.1:_meta.json\n\n{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.2.1\",\n  \"publishedAt\": 1776413915986\n}\n\nFile v0.2.1:agents/openai.yaml\n\ninterface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package Chrome extensions, scan tracked files, and render GitHub or ClawHub release commands with explicit tags\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory, scan tracked files for public-surface leaks, generate launch metadata for the target repo, and render GitHub or ClawHub publish commands with explicit topics and tags. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\"","readmeExcerpt":"Skill: OpenClaw CWS Publisher Owner: zack-dev-cm Summary: OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill. Use it when the user says \"chrome web store publisher\", \"extension release publi... Tags: browser-automation:0.3.5, chrome-extension:0.3.5, chrome-web-store:0.3.5, cloudflare:0.3.5, design-gates:0.3.5, latest:0.3.5, local-e2e:0.3.5, openclaw:0.3.5, privacy:0.3.5, release-automation:0.","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"export OPENCLAW_CWS_PUBLISHER_DIR=/path/to/openclaw-cws-publisher/scripts/openclaw-cws-publisher"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: openclaw-cws-publisher\ndescription: 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.\nversion: 0.3.5\nhomepage: https://github.com/zack-dev-cm/openclaw-cws-publisher\nlicense: MIT\nuser-invocable: true\nmetadata: {\"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\"]}]}}\n---\n\n# OpenClaw CWS Publisher\n\nSearch intent: `chrome web store publisher`, `extension release publisher`, `cws publisher`, `chrome extension publish`\n\n## Goal\n\nPrepare a Chrome extension repo for release with less metadata drift:\n\n- package the extension\n- validate the exact ZIP intended for upload against source manifest and CWS listing copy\n- scan tracked and untracked non-ignored files for obvious leak risks\n- run local reviewer/E2E gates\n- enforce design, UI, screenshot, and claim-alignment score gates\n- enforce storefront media uniqueness so portfolio waves do not reuse the same\n  icon motif, promo layout, visual signature, thumbnail template, or exact asset\n- enforce public landing, privacy, support, reviewer, SEO, and Cloudflare\n  canonical-page gates before dashboard submission\n- check current Chrome Stable release data before declaring E2E coverage fresh\n- run a lightweight competitor and positioning differentiation check\n- require a repo-local product-share/traffic-source gate when present, before\n  treating a new extension as submission-ready\n- detect repo-local reviewer gates\n- generate GitHub metadata\n- generate optional ClawHub metadata and explicit tags\n- render reproducible publish commands\n\n## Use This Skill When\n\n- the user wants a Chrome extension repo prepared for GitHub release\n- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission\n- the user wants ClawHub tags and GitHub topics kept in sync\n- the user wants a leakage check before public release\n- the user already has a specific repo path to release\n\n## Companion Scripts\n\nThe public ClawHub artifact is instruction-only so install-gate audits can return `PASS`.\nWhen the companion repository is available, set:\n\n```bash\nexport OPENCLAW_CWS_PUBLISHER_DIR=/path/to/openclaw-cws-publisher/scripts/openclaw-cws-publisher\n```\n\nThen use `$OPENCLAW_CWS_PUBLISHER_DIR/<script>.py` in the commands below.\n\n## Operating Order\n\n1. Run the repo-local product-share gate when present.\n   - Example: `npm run check:product-share` or `python3 scripts/check_product_share_gate.py --product <slug>`\n   - Block submission when the first traffic source, trust reason, share moment,\n     free MVP wi"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7dhjt1k1f111whp13fmrqwnh81tn1v\",\n  \"slug\": \"openclaw-cws-publisher\",\n  \"version\": \"0.3.5\",\n  \"publishedAt\": 1778832116971\n}"},{"path":"skill-card.md","content":"## Description:\n\nOpenClaw CWS Publisher helps agents package and harden Chrome extensions for Chrome Web Store release with package, listing, design, local E2E, Chrome release, competitor, leak, GitHub, and ClawHub gates.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[zack-dev-cm](https://clawhub.ai/user/zack-dev-cm)\n\n### License/Terms of Use:\n\nMIT\n\n## Use Case:\n\nDevelopers and release engineers use this skill to prepare a specific Chrome extension repository for Chrome Web Store submission by checking package contents, listing consistency, public-site readiness, leak risk, local review gates, and launch metadata.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The wrong repository path or extension ZIP could be assessed for release.\n\nMitigation: Confirm the target repo path and exact ZIP before treating the output as Chrome Web Store submission guidance.\n\nRisk: The public skill artifact depends on separately supplied companion scripts.\n\nMitigation: Review any companion scripts referenced by OPENCLAW_CWS_PUBLISHER_DIR before executing proposed commands.\n\nRisk: Leak scans may inspect tracked and untracked non-ignored files in the target repository.\n\nMitigation: Review scan scope and remove or ignore sensitive local files before running publication checks.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/zack-dev-cm/skills/openclaw-cws-publisher)\n- [Project homepage](https://github.com/zack-dev-cm/openclaw-cws-publisher)\n- [Chrome Web Store Program Policies](https://developer.chrome.com/docs/webstore/program-policies/policies)\n- [Manifest V3 remote-code requirements](https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements)\n- [Chrome extension activeTab model](https://developer.chrome.com/docs/extensions/develop/concepts/activeTab)\n- [Chrome extension permission warnings](https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions)\n- [Chrome release notes](https://developer.chrome.com/release-notes/)\n- [ChromiumDash release feed](https://chromiumdash.appspot.com/fetch_releases)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and configuration references]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May reference separately supplied companion scripts and repo-local release evidence.]\n\n## Skill Version(s):\n\n0.3.5 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."},{"path":"agents/openai.yaml","content":"interface:\n  display_name: \"OpenClaw CWS Publisher\"\n  short_description: \"Package and harden Chrome extensions with CWS package, listing, E2E, design, Chrome release, competitor, leak, and publish gates\"\n  default_prompt: \"Use $openclaw-cws-publisher to package the target extension directory; validate the exact ZIP against the source manifest and docs/cws/listing.json; scan tracked files for public-surface leaks; run repo-local reviewer/E2E gates; enforce the design/UI/UX evidence gate; check current Chrome Stable release data; run competitor/differentiation checks; generate launch metadata; and render GitHub or ClawHub publish commands with explicit topics and tags. If using the companion repo scripts, set OPENCLAW_CWS_PUBLISHER_DIR to scripts/openclaw-cws-publisher. If the extension has a dedicated public privacy/support site, pass --public-site-base or set CWS_PUBLIC_SITE_BASE so reviewer-facing links do not default to repo blobs or issue pages.\""},{"path":"LICENSE","content":"MIT License\n\nCopyright (c) 2026 Zack\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1540,"uniquenessScore":43,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T19:46:19.761Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T23:46:44.200Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}