ingest-preflight
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.
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.
- Downloads
- Security audit
- Pass
- Last updated
- 2mo ago
- Current version
- v1.0.0
- License
- MIT-0
