ClawHub

ClawHub Web Publisher

v1.0.0

Publish OpenClaw skills to ClawHub using the web dashboard only (no CLI login). Use when an agent must reliably upload a local skill folder, avoid auth-loop...

⭐ 0· 360·1 current·1 all-time
by@dalomeve
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the instructions: the SKILL.md describes a manual web-dashboard upload flow and privacy checks, and the skill does not request unrelated credentials, binaries, or install steps.
ℹ
Instruction Scope
Instructions reasonably stay within the publishing task (open dashboard, select folder, run privacy scans, capture results). Note: the procedure assumes the agent/operator can use the signed-in browser session and access the local skill directory for upload — if an automated agent has privileges to open that browser session and pick arbitrary local files, that capability enables uploading any local data, so the user should ensure only the intended folder is selected and that the agent's browser/file access is trusted.
✓
Install Mechanism
Instruction-only skill with no install spec and no downloaded code; nothing is written to disk by the skill itself.
✓
Credentials
No environment variables, credentials, or config paths are requested. The privacy checklist and secret-pattern scan are appropriate for a publisher.
✓
Persistence & Privilege
always:false and agent invocation defaults are normal; the skill does not request permanent presence or system-wide configuration changes.
Assessment
This skill appears to do what it says: guide a human/agent to upload a local skill via the ClawHub web dashboard while checking for secrets. Before using it, (1) manually confirm the agent or helper will only select the intended skill folder (not broader home directories), (2) run the provided secret search yourself and replace any real keys with placeholders, and (3) ensure the signed-in browser profile is the correct account. If you need fully automated publishing (CLI/API), this skill is not appropriate — look for a CLI- or API-based publisher that explicitly requires and documents necessary credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97f7tgvdhc8h4g6sp794fcras820k69

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments