Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill.
Install Openclaw Cws Publisher
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisher --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openclaw-cws-publisher .claude/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .claude/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisherType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisher --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/openclaw-cws-publisher .agents/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .agents/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisher --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/openclaw-cws-publisher .cursor/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .cursor/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/openclaw-cws-publisher--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisher --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/openclaw-cws-publisher .gemini/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .gemini/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisherInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/openclaw-cws-publisher .github/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .github/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-cws-publisher --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/openclaw-cws-publisher .opencode/skills/openclaw-cws-publisher && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-cws-publisher" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/openclaw-cws-publisher into .opencode/skills/openclaw-cws-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-cws-publisher", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openclaw-cws-publisher- GitHub stars
- 2.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 697 words
- Files
- 14 (incl. scripts)
- Skills in repo
- 1,235
- Repo updated
- First seen
- Licence
- MIT
At a glance
OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill.
- Works in 9 steps: Build the extension ZIP intended for… → Validate the exact ZIP, source manifest,… → Scan tracked and untracked non-ignored… → …
- The user says chrome web store publisher
- SKILL.md covers Goal, Use This Skill When, Operating Order and Rules, plus 2 more sections
- Runs Python scripts from its folder; calls python3
What it does
Openclaw Cws Publisher is an agent skill from LeoYeAI/openclaw-master-skills. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts (for example `.clawhub/origin.json`, `_meta.json` and `agents/openai.yaml`).
It sits in Testing & QA, covering Browser extensions and End-to-end testing. It works with GitHub and Chrome Extensions. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- The user says chrome web store publisher
- Extension release publisher
- Wants to package and harden a Chrome extension with CWS package
Example prompts
- “chrome web store publisher”
- “extension release publisher”
- “CWS publisher”
- “/openclaw-cws-publisher”
Requirements
- Python 3
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Build the extension ZIP intended for upload.
- Validate the exact ZIP, source manifest, and listing contract.
- Scan tracked and untracked non-ignored files for obvious publish leaks.
- Run local reviewer/E2E gates.
- Enforce the design/UI/UX evidence gate.
- Check current Chrome Stable release data.
- Run a competitor/differentiation check.
- Generate launch metadata.
- Render publish commands.
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 10 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developer.chrome.comchromiumdash.appspot.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openclaw Cws Publisher loads about 1.8k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 697 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 697 words, ~1,817 tokens.
Download SKILL.mdSave it as
.claude/skills/openclaw-cws-publisher/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.- name
- openclaw-cws-publisher
- description
- OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill. Use it when the user says "chrome web store publisher", "extension release publisher", "CWS publisher", or wants to package and harden a Chrome extension with CWS package, listing, design, local E2E, latest Chrome, competitor, leak, GitHub, and ClawHub gates.
- version
- 0.3.2
- homepage
- https://github.com/zack-dev-cm/openclaw-cws-publisher
- license
- MIT
- user-invocable
- true
OpenClaw CWS Publisher
Search intent: chrome web store publisher, extension release publisher, cws publisher, chrome extension publish
Goal
Prepare a Chrome extension repo for release with less metadata drift:
- package the extension
- validate the exact ZIP intended for upload against source manifest and CWS listing copy
- scan tracked and untracked non-ignored files for obvious leak risks
- run local reviewer/E2E gates
- enforce design, UI, screenshot, and claim-alignment score gates
- check current Chrome Stable release data before declaring E2E coverage fresh
- run a lightweight competitor and positioning differentiation check
- detect repo-local reviewer gates
- generate GitHub metadata
- generate optional ClawHub metadata and explicit tags
- render reproducible publish commands
Use This Skill When
- the user wants a Chrome extension repo prepared for GitHub release
- the user wants CWS ZIP/listing/privacy/design/E2E readiness checked before dashboard submission
- the user wants ClawHub tags and GitHub topics kept in sync
- the user wants a leakage check before public release
- the user already has a specific repo path to release
Operating Order
- Build the extension ZIP intended for upload.
python3 {baseDir}/scripts/build_extension_zip.py --extension-dir <repo>/extension --out <zip>
- Validate the exact ZIP, source manifest, and listing contract.
python3 {baseDir}/scripts/validate_cws_package.py --zip <zip> --source-manifest <repo>/extension/manifest.json --listing-json <repo>/docs/cws/listing.json- 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. - If a product genuinely needs host permissions, use
--allow-host-permissionsonly after the listing and reviewer instructions explain the shipped user-facing need.
- Scan tracked and untracked non-ignored files for obvious publish leaks.
python3 {baseDir}/scripts/scan_publish_surface.py --root <repo> --json-out <json> --markdown-out <md>
- Run local reviewer/E2E gates.
python3 {baseDir}/scripts/run_local_e2e_gates.py --repo-root <repo> --json-out <json> --markdown-out <md>- The script discovers
check:cws,check:public,check:public:visual,test:e2e:reviewer,test:e2e, andscripts/reviewer_gate.pywhen present.
- Enforce the design/UI/UX evidence gate.
python3 {baseDir}/scripts/check_design_gate.py --design-report <repo>/docs/design-gate.json --screenshot-metadata <repo>/assets/listing/screenshot-1.png.source.json- Every changed public page, popup, CWS screenshot, promo tile, hero, and media asset must score at least
8/10for product clarity, visual trust, evidence integrity, responsive polish, accessibility, and claim alignment.
- Check current Chrome Stable release data.
python3 {baseDir}/scripts/check_chrome_release.py --tested-chrome-version <local chrome version> --json-out <json> --markdown-out <md>- Source: Chrome for Testing last-known-good Stable feed, cross-checked with ChromiumDash, Chrome Releases, and Chrome for Developers release notes when making decisions.
- Run a competitor/differentiation check.
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>- Record at least three comparable products or explicit substitutes; flag risky claims like
#1,best,official, and close-copy positioning.
- Generate launch metadata.
python3 {baseDir}/scripts/generate_launch_manifest.py --repo-root <repo> --owner <github-owner> --public-site-base <https://public-site.example/> --out <json>- If you already export
CWS_PUBLIC_SITE_BASE, you can omit--public-site-baseand the script will reuse that public reviewer-facing base.
- Render publish commands.
python3 {baseDir}/scripts/render_publish_commands.py --manifest <json> --out <md>
Show full SKILL.md (248 more words)Show less
Rules
- Operate on the repo path the user named, not on arbitrary sibling directories.
- Inspect the ZIP intended for upload, not only the source tree, before calling a Chrome Web Store package ready.
- Prefer
activeTabplusscriptingafter an explicit user gesture over persistent host permissions. - Do not publish when the leak scan has unresolved findings.
- Do not publish when the target repo has a reviewer gate and it fails.
- Do not publish when package/listing/privacy claims disagree with the ZIP manifest.
- Do not publish when the design/UI gate is missing or any score is below
8/10. - Do not publish when local E2E was only run on an older Chrome milestone without recording the current Stable release check.
- 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.
- Keep GitHub topics and ClawHub tags explicit in the generated manifest.
- Use a dedicated public site base for support, privacy-policy, and reviewer-instructions links when the extension has one.
- If a Chrome Web Store draft is already pending review, do not recommend canceling or replacing it unless a verified acceptance blocker exists.
- Do not assume generated artifacts should be committed.
Current Policy Anchors
- Chrome Web Store Program Policies: https://developer.chrome.com/docs/webstore/program-policies/policies
- Manifest V3 remote-code requirements: https://developer.chrome.com/docs/webstore/program-policies/mv3-requirements
activeTabplusscriptingmodel: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab- Permission warnings and host permission warnings: https://developer.chrome.com/docs/extensions/develop/concepts/declare-permissions
- Chrome release notes: https://developer.chrome.com/release-notes/
- Chrome release feed: https://chromiumdash.appspot.com/fetch_releases
Bundled Scripts
scripts/build_extension_zip.pyscripts/validate_cws_package.pyscripts/scan_publish_surface.pyscripts/run_local_e2e_gates.pyscripts/check_design_gate.pyscripts/check_chrome_release.pyscripts/check_competitors.pyscripts/generate_launch_manifest.pyscripts/render_publish_commands.py
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 13 other files (scripts) in skills/openclaw-cws-publisher of LeoYeAI/openclaw-master-skills.
- SKILL.md
- .clawhub/origin.json
- _meta.json
- agents/openai.yaml
- scripts/build_extension_zip.py
- scripts/check_chrome_release.py
- scripts/check_competitors.py
- scripts/check_design_gate.py
- scripts/common.py
- scripts/generate_launch_manifest.py
- scripts/render_publish_commands.py
- scripts/run_local_e2e_gates.py
- scripts/scan_publish_surface.py
- scripts/validate_cws_package.py
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Openclaw Cws Publisher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openclaw Cws Publisher this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Repomix Browser Extension Developeryamadashy/repomix | 29k | 1 repos | ~288 | Automated safety check: Pass | MIT | |
| Deepseek Automationzhu1090093659/deepseek-pp | 1.9k | — | ~2.1k | Automated safety check: Notes | Apache-2.0 | |
| Spec Driven Developzhu1090093659/deepseek-pp | 1.9k | — | ~6.9k | Automated safety check: Pass | Apache-2.0 | |
| Release ExtensionYorick-Ryu/deep-share | 144 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Cherry Studio Regression TestsCherryHQ/cherry-studio | 53k | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Deepseek Automation
zhu1090093659/deepseek-pp
A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.
Spec Driven Develop
zhu1090093659/deepseek-pp
Automates pre-development workflow for large-scale complex tasks.
Release Extension
Yorick-Ryu/deep-share
Release browser extensions or similar small packaged apps by upgrading a semantic version, packaging build artifacts, creating a git commit and tag, pushing to the remote, and publishing a GitHub…
Cherry Studio Regression Tests
CherryHQ/cherry-studio
Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.
- Official
Nemoclaw Maintainer Fix E2E Failures
NVIDIA/NemoClaw
Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.
More from LeoYeAI/openclaw-master-skills
All 1,200 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Works with
Categories
Questions about Openclaw Cws Publisher
What does Openclaw Cws Publisher do?
OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill. Openclaw Cws Publisher is an agent skill from LeoYeAI/openclaw-master-skills. OpenClaw CWS Publisher is a public ClawHub Chrome Web Store publisher skill.
When should I use Openclaw Cws Publisher?
Openclaw Cws Publisher fits situations like: the user says chrome web store publisher; extension release publisher; wants to package and harden a Chrome extension with CWS package.
How do I install Openclaw Cws Publisher in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a claude-code`. Or copy the skill folder (skills/openclaw-cws-publisher in LeoYeAI/openclaw-master-skills) into .claude/skills/openclaw-cws-publisher in your project. Claude Code loads it when a task matches its description.
How do I install Openclaw Cws Publisher in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a codex`. Or copy the skill folder (skills/openclaw-cws-publisher in LeoYeAI/openclaw-master-skills) into .agents/skills/openclaw-cws-publisher in your project. Codex loads it when a task matches its description.
Can I use Openclaw Cws Publisher in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-cws-publisher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-cws-publisher, .gemini/skills/openclaw-cws-publisher, .github/skills/openclaw-cws-publisher and .opencode/skills/openclaw-cws-publisher in your project.
What does Openclaw Cws Publisher need to run?
Going by SKILL.md and its folder, Openclaw Cws Publisher needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Openclaw Cws Publisher access the network?
SKILL.md names 2 domains. As links in the text: developer.chrome.com and chromiumdash.appspot.com. This is read from the text; nothing was executed.
Is Openclaw Cws Publisher safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Openclaw Cws Publisher use?
Openclaw Cws Publisher is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openclaw Cws Publisher use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openclaw Cws Publisher?
Skills that share tags, products or a category with Openclaw Cws Publisher: Repomix Browser Extension Developer (yamadashy/repomix, 29k stars), Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars), Spec Driven Develop (zhu1090093659/deepseek-pp, 1.9k stars) and Release Extension (Yorick-Ryu/deep-share, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openclaw Cws Publisher?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.