Security

SkillHub Publish Auditor

Try it

Use when preparing a Skill folder for public release to SkillHub, ClawHub, or another agent-skill marketplace, especially before publishing third-party insta...

What it does

Use when preparing a Skill folder for public release to SkillHub, ClawHub, or another agent-skill marketplace, especially before publishing third-party insta...

The skill document

SkillHub Publish Auditor

Overview

Audit an agent Skill as a public package, not a private note. The goal is to catch release blockers, weak discovery metadata, unsafe scripts, credential leaks, unfinished template markers, and packaging issues before upload.

Quick Start

Run the bundled auditor from the skill folder you want to publish:

python /scripts/audit_skill_release.py  --markdown

Use --json for CI or automated marketplace checks.

Release Standard

Apply four gates in order:

  1. Structure: SKILL.md exists, frontmatter parses, name is publishable, and no unfinished template markers remain.
  2. Discovery: description starts with Use when, names concrete triggers, and does not summarize the whole workflow.
  3. Safety: scripts and references do not read secrets, hide instruction-override payloads, run destructive shell commands, or send local data out.
  4. Packaging: resource links resolve, examples are intentional, auxiliary files are not clutter, and UI metadata is useful.

Read references/release-checklist.md when judging borderline findings or preparing a manual review.

Required Behavior

  • Treat every file in the candidate skill as publishable supply-chain content.
  • Inspect scripts before recommending release, even when SKILL.md looks clean.
  • Mark issues as blocker, warn, or info; keep each finding specific.
  • Recommend exact file-level fixes, but do not auto-edit unless the user asks.
  • If the skill executes code, require at least one local smoke test or explain why no test can run.

Common Mistakes

MistakeFix
Publishing template textRemove unfinished markers and generated instructions.
Description explains workflowRewrite it as trigger conditions only.
Security review stops at SKILL.mdScan every script, reference, config, and example.
Marketplace metadata ignoredCheck agents/openai.yaml when present.
"Harmless" helper scripts read env filesFlag environment, SSH, credential, token, and key access.

Output Contract

End with a release decision:

  • READY: no blockers.
  • READY_WITH_WARNINGS: warnings remain, but no release blocker.
  • BLOCKED: one or more blockers must be fixed before publishing.

Related skills

Skill Publish Readiness

Publish-ready review for ClawHub skills and plugins. 在正式发布前揪出文件缺失、版本不一致、环境声明、安全风险和同质化问题。

2 installs

Skill Auditor

Deep audit for installed ClawHub skills — usage analysis, permission review, conflict detection

4 installs

Skill Release Audit

Pre-publish quality and safety auditor for AI agent skills (SKILL.md + scripts/ + references/ format used by Claude Code, Cursor, OpenAI Codex, GitHub Copilo...

1 installs

Skill Auditor

Automated security audit for AI agent skills. Use BEFORE installing any skill from ClawHub, GitHub, or other sources. Scans SKILL.md + all files for 30+ red...

by Zoran2 installs

Skill Audit & Publish

Audit-first pipeline to publish an OpenClaw skill to ClawHub without leaking personal data, credentials, or model-specific references. Five stages — Sanitize, Transform, Verify, Publish, Install-check — with explicit user approval before every irreversible step. Use this when the user wants to publish a skill to ClawHub, sanitize a skill before publishing, run a pre-publish PII/secret audit, or follow the ClawHub publish workflow. Trigger phrases: 'publish to ClawHub', 'publish my skill', 'sanitize before publish', 'pre-publish checklist', 'clawhub publish command', 'upload a skill to clawhub'.

8 installs