What problem does it solve? Finished software work often ships as a loose drop: READMEs that reference unpushed commits, install commands that only work on the author's machine, raw-vs-blob GitHub URL mistakes, and private local aliases like @personal leaking into public docs. This Skill turns finished work into a verified public package and proves a stranger can actually install it before anything is called live. ## Core Features & Use Cases - Launch packaging (Lane A): Inventories every launch surface (repo, GitHub Pages, README, skill pack, MCP server, social copy), confirms branch/commit/live URLs, and produces public copy with proof links and a ship/ship-with-caveats/hold verdict. - Install verification (Lane B): Runs the exact install command from a clean temporary directory after pushing, and diagnoses failures with a symptom-to-fix table covering 404s, missing --path flags, blob-vs-raw URLs, and frontmatter mismatches. - Use Case: You just finished a new Claude Code skill and want to announce it. The Skill verifies the folder exists at main, runs the install command from a temp dir, checks every link in the launch copy, and only then recommends shipping. ## Quick Start Use the suede-launch-packaging skill to package my finished skill folder for public release and verify the install command works from a clean temporary directory.
