ClawHub Publish

Publish OpenClaw skills to ClawHub marketplace (clawhub.ai). Use when deploying a skill to ClawHub for the first time, updating an existing published skill,...

Security Scan

The skill's requirements and instructions are internally consistent with a ClawHub publish workflow: it only reads/edits local skill files and invokes the clawhub CLI for publishing, and it does not request unrelated credentials or install/execute hidden code.

Purpose & Capability

Name/description match the instructions: the SKILL.md describes sanitizing and versioning local skill folders and running the clawhub CLI to publish. No unrelated credentials, binaries, or installs are declared.

Instruction Scope

Instructions operate on the local skill folder (C:\MAIBOT\skills\<skill-name>), references/* files, and the clawhub CLI; they ask the agent to inspect and rewrite SKILL.md and references for language/personal info and then run clawhub publish. This scope matches the stated purpose. Note: the workflow includes writing files (PowerShell example) and expects PTY/browser login for the CLI.

Install Mechanism

There is no automated install spec; the doc only recommends installing the official npm clawhub CLI (npm i -g clawhub). No downloads, archives, or third-party URLs are embedded in the skill.

Credentials

The skill declares no environment variables or credentials. The only external authority required is a clawhub account (handled via clawhub login). No unrelated secrets are requested.

Persistence & Privilege

always is false and the skill does not request persistent platform privileges or modify other skills' configs. It does instruct editing files within the skill folder and local notes (memory/marketplace-strategy.md, Obsidian), which is appropriate for a publish workflow.

Assessment

This skill appears coherent for publishing skills to ClawHub, but review before use: 1) Backup the local skill folder so automated edits can be undone. 2) Inspect SKILL.md and references/* to ensure there are no secrets or private data before publishing (the workflow itself edits these files). 3) Be aware the workflow expects Windows-style paths (C:\MAIBOT) and uses PowerShell examples — adjust if you use another OS. 4) You will need the clawhub CLI and to authenticate via browser (clawhub login); the skill does not ask for API keys directly. 5) Only proceed if you trust the agent to read and write files in your skill and notes directories. If you want tighter control, perform the described checks and the actual publish command manually instead of allowing an agent to run them autonomously.

Prerequisites

• clawhub CLI installed: npm i -g clawhub
• Logged in: clawhub whoami (if not: clawhub login via PTY + browser)
• Target skill folder exists under C:\MAIBOT\skills\<skill-name>\

Workflow

1. Pre-publish Checklist

Run against each skill before publishing. See references/checklist.md for full criteria.

Quick scan:

Get-Content "C:\MAIBOT\skills\<skill-name>\SKILL.md" -Encoding UTF8 | Select-Object -First 40

Must verify:

• description: field is in English (this is what ClawHub users see first)
• No Korean text in SKILL.md body
• No personal paths (C:\Users\jini9, JINI_SYNC, etc.)
• No internal account names or credentials
• Generic placeholders used where personal config appeared

2. Language & Sanitization Fix

If Korean or personal info is found:

1. Rewrite SKILL.md fully in English
2. Replace personal paths with generic placeholders ($VAULT_PATH, ~/vault, your-username)
3. Move any references/*.md content to English as well
4. Write with UTF-8: [System.IO.File]::WriteAllText($path, $content, [System.Text.Encoding]::UTF8)

3. Determine Version

Scenario	Version bump
First publish	1.0.0
Content fix / translation	1.1.0 (minor)
New section / major rewrite	2.0.0 (major)
Typo / small fix	1.0.1 (patch)

4. Publish

cd C:\MAIBOT
clawhub publish ./skills/<skill-name> `
  --slug <slug> `
  --name "<Display Name>" `
  --version <X.Y.Z> `
  --changelog "<one-line summary of changes>"

Slug rules:

• Lowercase, hyphens only
• Must be globally unique on ClawHub
• If slug taken: append -mai suffix (e.g., obsidian-daily-mai)

5. Verify

clawhub whoami   # confirm still authenticated
# Then check: https://clawhub.ai/u/jini92

6. Update Records

After successful publish, update both:

• C:\MAIBOT\memory\marketplace-strategy.md — add row to ClawHub table
• Obsidian _DASHBOARD.md — add to Current Sprint as Done

Batch Publish

To publish multiple skills at once, run steps 1–4 for each in sequence. Check references/checklist.md for the full quality bar before each.

Common Errors

Error	Fix
Not logged in	Run clawhub login in PTY mode; open browser URL when shown
Only the owner can publish updates	Slug taken by another user; add -mai suffix
Login session timeout (code 1)	Rerun clawhub login — PTY must stay alive until browser auth completes