SkillHub Publish Assistant

Problem It Solves

Before publishing a skill, the friction is usually metadata and material completeness: SKILL.md name, version, or description may not match the directory, README.md may miss Quick start or Who it is for, CHANGELOG.md may skip the current release, scripts may contain hard-coded tokens, and external dependencies may be undeclared. Copying the skill directly to SkillHub can fail because of frontmatter, formatting, or sensitive content.

How It Works

skillhub-publish turns release preparation into a confirmable pipeline:

• Phase 0 pre-flight check: probes WorkBuddy, OpenClaw, Hermes, and Universal platform paths, confirms the target skill directory, reads the SKILL.md frontmatter, and reports blocking or warning states.
• Phase 1 six-dimension audit: read-only checks for file structure, frontmatter fields, content quality, version consistency, security scanning, and external dependencies, producing P0/P1/P2 findings.
• Phase 2 review and confirmation: presents each issue, suggested fix, and impact so the user can fix, skip, or customize; P0 items cannot be skipped.
• Phase 3 repair and generation: creates a desktop release copy, applies confirmed fixes to frontmatter, placeholders, version mismatches, and security issues, then generates README.md, a SkillHub listing description, and release notes.
• Phase 3.5 sanitization: applies private or built-in rules to .md and .yaml files in the copy while leaving the original skill untouched.
• Phase 4 validation and delivery: re-checks P0 items, outputs a report, the release package location, and copyable description text.

Boundaries And Caveats

This skill is for pre-release preparation of an existing local skill. It does not automatically submit to SkillHub, delete files, or modify the original skill directory. Audit findings are derived from existing files, and content that cannot be inferred from sources is marked. If private sanitization rules conflict with built-in rules, private rules take precedence.