/suede-launch-packaging · Launch readiness

No launch leaves without proof.

Nothing is called live until the exact install command runs from a clean temporary directory, never from inside the checkout that built it. Any @personal alias or local-only path is stripped before the copy goes public. README, docs page, release note, GitHub Pages update, MCP server, or skill-pack release: same gate, same handoff notes.

View skill folder Install options

"package this launch so the claims hold" /suede-launch-packaging Ask in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.

$ /suede-launch-packaging package v1.0 install commands verified live · docs linked evidence check: every number has a source LAUNCH PACKET SEALED · PROOF INSIDE

Copy just this skill

Claude Code project-level copy:

git clone https://github.com/JasonColapietro/suede-creator-skills.git /tmp/suede-creator-skills
mkdir -p .claude/skills
cp -R /tmp/suede-creator-skills/skills/suede-launch-packaging .claude/skills/

Codex installer:

python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
    --repo JasonColapietro/suede-creator-skills \
    --path skills/suede-launch-packaging

What it covers

Launch inventory for repos, GitHub Pages sites, docs updates, skill packs, MCP servers, app features, and social or email copy.
Public packaging around repo URLs, live URLs, docs pages, README sections, release notes, proof links, screenshots, build output, live routes, and raw GitHub URLs.
Install support for Codex and Claude installs, repo-and-path commands, raw-URL fixes, MCP setup, local plugin notes, and marketplace confusion.
Hard gates for live-surface checks, clean-temp install tests, ship gate status, and keeping @personal or local aliases out of public docs.
Copy, SEO, link, and evidence-boundary checks before publishing, plus handoff notes and launch status.

When to use it

Use it when a skill, repo, site, MCP server, feature, or docs update is ready to share.
Use it when an install fails, a public user cannot add a skill, @personal leaks into public copy, or a public explainer needs a simpler path.
Use it before announcement or launch copy that depends on a verified live URL or public artifact.
Use it when README, docs, or launch copy needs proof links and tested install commands.
Not for: MCP-specific tool/resource/prompt validation depth (use Suede MCP QA).
Not for: SEO/schema depth beyond install proof links (use Suede SEO Audit).

Best prompt

Use $suede-launch-packaging to package this skill release for public docs. Verify the live surface first, list the launch surfaces, add proof links, test the Claude Code and Codex install commands from a clean temporary directory, remove any @personal or local-only paths from public copy, and return the Lane A and Lane B output with status.

Related skills

Use Suede Visibility Grader for the promotion-readiness grade, Suede Copy for announcement copy, and Suede MCP QA before MCP install docs ship.

Evidence boundaries

This skill organizes and prepares a release and its install paths. It does NOT clear rights, confirm ownership, approve payouts, write to any registry, or guarantee outcomes (reach, ranking, results).

Install this skill

It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.

terminal · install the pack

Claude Code

$ /plugin marketplace add JasonColapietro/suede-creator-skills
$ /plugin install suede-skills@suede

Codex

$ codex plugin add suede-skills@suede-codex

Cursor, Copilot, and Windsurf install through the skills CLI. Every path is on the install page, and every folder is readable first on GitHub.