Validate a SKILL.md before publishing — checks frontmatter completeness, semver, and that every declared bin actually resolves on PATH. Use before `clawhub publish`, or when a skill fails to load / shows as missing requirements.
Coding
ingest-preflight
Try itBefore publishing to ClawHub, validate a skill-shaped folder (required files, frontmatter, size, auth, slug availability, and a dry-run publish) with one script. Use when authoring or packaging a skill and you want to catch structural problems before the real publish.
What it does
Before publishing to ClawHub, validate a skill-shaped folder (required files, frontmatter, size, auth, slug availability, and a dry-run publish) with one script. Use when authoring or packaging a skill and you want to catch structural problems before the real publish.
The skill document
ingest-preflight
A tiny, honest gatekeeper for the 数字资源入库 step. Run it on a packaged
skill folder before clawhub publish; it tells you exactly what is wrong so you
do not ship a broken asset.
When to use
- You have just finished the upstream workflow (content review, metadata fill, folder packaging) and want one authoritative check before publishing.
- You want a repeatable command instead of ad-hoc
ls/headinspection. - You are teaching the "process → ingest" chain and need a visible gate.
Prerequisites
clawhubCLI installed and onPATH.- Authenticated:
clawhub whoamireturns a publisher handle. - The asset folder contains at least
SKILL.md(frontmatter withnameanddescription).references/is recommended.
Run it
# from anywhere, point at the skill folder
bash scripts/preflight.sh /path/to/your-skill --slug your-unique-slug
What it checks (in order):
SKILL.mdexists.- Frontmatter starts with
---and containsnameanddescription. references/directory is present (warns, does not fail).- No file larger than 2M (warns).
clawhubCLI is present andclawhub whoamisucceeds.- The proposed
--slugis free (clawhub inspect). - Authoritative gate:
clawhub publish --dry-runactually accepts the folder.
Exit code 0 = safe to publish; 1 = fix the listed failures first.
Example (self-test)
bash scripts/preflight.sh . --slug ingest-preflight
Why it exists
The business-process tool packages the asset; clawhub is the tool that
ingests it. This script is the deterministic handoff check between them — it
keeps the "process" and "ingest" tools honest by refusing to continue until the
asset is structurally valid.
Related skills
Orchestrate a TaskFlow-managed ingestion job that validates, packages, and publishes an OpenClaw skill folder to the ClawHub registry, then verifies the published artifact. Use when a piece of digital content (an agent skill) must move through a durable multi-step flow and land in the ClawHub resource center in a reproducible way.
1 installs
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
Publish-ready review for ClawHub skills and plugins. 在正式发布前揪出文件缺失、版本不一致、环境声明、安全风险和同质化问题。
2 installs
Prepare and publish a local skill to ClawHub and GitHub using a workflow that keeps the local publish directory clean. Use this skill when the user wants to...
19 installs
Minimal demonstration skill for verifying a ClawHub publish flow. Prints a configurable greeting and the current date so the publish/ingest path can be exercised with a safe, side-effect-free artifact.
1 installs