New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Suede Launch Packaging

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.

MITAuto-check passedDevelopment

Install Suede Launch Packaging

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-launch-packaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-launch-packaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-launch-packaging .claude/skills/suede-launch-packaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
suede-launch-packaging
GitHub stars
127
Token cost
~2.4k tokens
SKILL.md length
1,319 words
Files
4 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.

  • Works in 4 steps: No launch copy until the live surface is… → No install doc until the install command… → Set the ship gate before recommending… → …
  • Finished software work needs a clean public package (README
  • SKILL.md covers Gate policy: advisory, not…, Approved Suede S Mark, Step 0: Inventory the launch… and Hard gates (advisory), plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Launch Packaging is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned launch packaging and install verification. Use when finished software work needs a clean public package (README, docs page, install command, release note, GitHub Pages update, skill-pack release, MCP server, or launch/social copy) or when a release needs handoff notes, an install fails, a public user cannot add a skill, a raw-vs-blob URL returns HTML, or @personal or a local plugin alias leaks into public docs. Verifies the live URL and runs the exact install command from a clean temporary directory…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `references/lanes.md`).

It sits in Development, covering MCP servers, Go-to-market strategy and Changelog and release notes. It works with Model Context Protocol and GitHub. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.

When your agent uses it

  • Finished software work needs a clean public package (README
  • Install command
  • GitHub Pages update
  • Skill-pack release

Example prompts

  • “/suede-launch-packaging”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. No launch copy until the live surface is verified. Fetch the live URL or public artifact and confirm the expected status or render first…
  2. No install doc until the install command was run from a clean temporary directory after pushing. Success from inside the local repo does…
  3. Set the ship gate before recommending any announcement. A hold verdict is your recommendation that nothing goes out yet, including "soft"…
  4. @personal and local plugin aliases never appear in public docs, READMEs, MCP catalog output, or explainer copy. They are local operator…

What it can do on your machine

Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Suede Launch Packaging loads about 2.4k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 209 tokens; SKILL.md has 1,319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~209
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 1,319 words, ~2,352 tokens.

Download SKILL.mdSave it as .claude/skills/suede-launch-packaging/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
suede-launch-packaging
description
Suede-owned launch packaging and install verification. Use when finished software work needs a clean public package (README, docs page, install command, release note, GitHub Pages update, skill-pack release, MCP server, or launch/social copy) or when a release needs handoff notes, an install fails, a public user cannot add a skill, a raw-vs-blob URL returns HTML, or `@personal` or a local plugin alias leaks into public docs. Verifies the live URL and runs the exact install command from a clean temporary directory before anything is called live. NOT FOR: product, course, or artist campaign launches (use suede-campaign-in-a-box or suede-marketing-plan); writing announcement copy from scratch (use suede-copy); MCP tool-catalog QA (use suede-mcp-qa); landing-page conversion work (use suede-site-alchemy).
metadata.version
1.0.0

Suede Launch Packaging

Gate policy: advisory, not blocking

Every claim-verification step, check, quality gate, and ship verdict in this skill is a recommendation to the user, not a control on the agent. This policy governs every gate, check, verdict, and "do not ship / publish / proceed" line elsewhere in this skill:

  • Run every check and report the results honestly. Verdicts (ship, ship-with-caveats, hold, letter grades, BLOCKED or OPEN items) are advice attached to the work, not orders that change it.
  • Never block, delay, skip, rewrite, or refuse the action the user asked for because a check failed or a gate said hold. Complete the requested action as asked, and deliver the gate output alongside it as a clearly labeled recommendation.
  • A failed gate changes what you report, never what you do.
  • Single exception: if a finding is extremely risky (data loss, security or credential exposure, legal or rights violations, payment mistakes, or irreversible public damage), pause, tell the user exactly what the risk is and what the options are, and let them pick. Their choice is final.

Approved Suede S Mark

Launch art, social cards, docs headers, app assets, and release visuals may use only docs/assets/suede-ai-logo-transparent.png from JasonColapietro/suede-creator-skills as the Suede S mark (SHA-256 83a7ee0317e4debe2e7b076c20ba067feb76a587f9e829dc6310ae4be4b44dfa). Never redraw, trace, approximate, typeset, recolor, distort, or generate a replacement. If the canonical asset is missing or its checksum differs, block the branded visual and request the approved file.

Ship Suede work as a launch, not a loose drop. This skill turns finished work into a clean public package AND makes sure a stranger can actually install and run it. Packaging a public release and proving the install both live here.

Core principle: a release nobody can install is not a launch. Nothing is "live" until you fetched it yourself, and no install path ships until the exact command ran from a clean temporary directory.

Step 0: Inventory the launch (detect first)

Before picking a lane, name exactly what is being launched. Do not assume from the request; check the repo, branch, and live surface. One request often spans several rows (a skill launch = repo + README + install command + social copy). List every row that applies: each needs its own verification.

Launch surfaceVerify before writing copyProof artifact
Repo or releaseDefault branch is public; the launch commit is pushed; tags/releases exist if referencedRepo URL + commit hash
GitHub Pages or sitePage renders at the public URL; no stale buildLive URL + screenshot
README or docs updateRendered page matches the pushed sourceRendered docs URL
Skill or skill packSkill folder exists at main; install command runs from a clean temp dirInstall command transcript
MCP serverServer starts; tools/list matches the catalogsuede-mcp-qa output
App featureFeature is live behind the public route, not just mergedLive route readback
Social or email copyEvery link resolves; every claim matches the live productLink sweep results

Hard gates (advisory)

Do not rationalize past these silently. Each one is a strong recommendation about ordering: run the check before the step it guards. If the user directs you past one, proceed as directed and label the output with exactly which verification is missing.

  1. No launch copy until the live surface is verified. Fetch the live URL or public artifact and confirm the expected status or render first. Copy drafted against "it should be live" is a violation.
  2. No install doc until the install command was run from a clean temporary directory after pushing. Success from inside the local repo does not count: the local checkout masks missing pushes and private paths.
  3. Set the ship gate before recommending any announcement. A hold verdict is your recommendation that nothing goes out yet, including "soft" posts: state it plainly with the reasons, then let the user decide.
  4. @personal and local plugin aliases never appear in public docs, READMEs, MCP catalog output, or explainer copy. They are local operator notes only.

Pick the lane

Most launches use both lanes in order: package the release, then prove the install. Pick what the request is asking for.

  • Lane A: Package the launch. Work is ready to leave the local machine and needs a clean public package: a repo, live URL, docs page, README section, install command, release note, GitHub Pages update, skill-pack release, MCP server, feature, or social/email copy. Start here for "ship this," "write the release," "package this drop."
  • Lane B: Install support. An install fails, a public user cannot add a skill, @personal leaks into public copy, or a README, docs, MCP catalog, or public explainer step needs a simpler, public-first path. Start here for "the install is broken," "fix the install command," "why can't they add this skill," "the marketplace is confusing." Lane A always runs Lane B's command-test step before publishing.

When both apply (most full launches), run Lane A to assemble the package, then run Lane B to verify and correct every install path inside it before you ship.

Show full SKILL.md (492 more words)Show less

Lane Playbooks

Lane A (package the launch) and Lane B (install support) are in references/lanes.md. Pick the lane above, then read it. Lane A also needs Lane B's command-test step before publishing, so a Lane A run reads both. The evidence boundaries below and the Suede S mark rules apply to either lane.

Evidence boundaries (applies to both lanes)

  • 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). Live-URL and clean-temp-dir install verification are governed by Hard gates 1 and 2 above, which carry the required ordering.
  • Keep @personal and any local-only plugin commands out of all public copy. They are local operator notes.
  • No competitor product names in any public copy.

Red flags: stop

If you catch yourself thinking any of these, stop and run the gate:

  • "The README says it works.": The README is a claim, not a test. Run the command.
  • "I'll test the install after publishing.": Test from a clean temp dir first, or the launch holds.
  • "It installed fine on this machine.": The local checkout masks missing pushes. Clean temp dir only.
  • "The raw URL is obviously right.": Fetch it. Blob-vs-raw catches everyone eventually.
  • "Everyone reading this doc is internal, @personal is fine.": Public docs are public. Keep it out.
  • "We can announce now and fix the install path after.": The first-touch install IS the launch.

Routing

  • Launch page going public → suede-visibility-grader for a promotion-readiness grade before any push.
  • MCP server in the package → suede-mcp-qa before the install doc ships.
  • Page metadata, schema, or discoverability depth → suede-seo-audit.
  • Landing page must convert, not just inform → suede-site-alchemy.
  • Announcement or launch copy needs writing from scratch → suede-copy (or johnny-suede-write for the full writing stack).
  • Product, course, coaching, or artist campaign launch → suede-campaign-in-a-box (creator/artist) or suede-marketing-plan (product/service); this skill packages software releases and their install paths only.

Simple explanation (plain, for a 10-year-old)

Think of it like putting out a record instead of leaving a demo tape on the floor. First you make sure the song is really finished and you know where the master copy lives. Then you write the back-of-the-album note so a fan gets what the song is about, not how you wired the amps. Then you hand people the exact way to actually play it (the real link, the real install steps) and you try those steps yourself on a clean machine first, so nobody gets a broken download. You keep the messy backstage notes (like the private @personal shortcut) off the public sleeve. And you only say "it's out now" once you've clicked the link yourself and heard it play.

End every meaningful launch with the simple explanation above, then the usual breakdown (Lane A output and, when an install is involved, Lane B output), then Cue Suede so the operator can request a change, preserve what worked, or say nothing to keep it as-is.

© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/suede-launch-packaging of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • references/lanes.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Launch Packaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Suede Launch Packaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Launch Packaging this skillJasonColapietro/suede-creator-skills127—~2.4kAutomated safety check: PassMIT
Release Prepjohnhuang316/code-index-mcp1k—~680Automated safety check: PassMIT
Project Releaseswimmwatch/cloakbrowser-mcp164—~1.9kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Reading Livekit Docslivekit-examples/agent-starter-python2641 repos~1.1kAutomated safety check: PassMIT
Project Pull Requestswimmwatch/cloakbrowser-mcp164—~1kAutomated safety check: PassMIT

Similar skills

  • Release Prep

    johnhuang316/code-index-mcp

    A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.

    1k GitHub stars~680 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Project Release

    swimmwatch/cloakbrowser-mcp

    Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.

    164 GitHub stars~1.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Reading Livekit Docs

    livekit-examples/agent-starter-python

    Looks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory.

    264 GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    164 GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Os Release

    CronusL-1141/AI-company

    发布 AI Team OS 新版本的完整清单——预检、版本七处锁步、中英双语 CHANGELOG、双份 dist 构建、私有术语扫描、commit/tag、双仓推送、建 GitHub Release 条目并核对 latest 徽章、事后核对。当准备发版、补建漏掉的 Release 条目、或核对已发版本的线上状态时使用。

    371 GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo

  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes

  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Suede Launch Packaging

What does Suede Launch Packaging do?

Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills. Suede Launch Packaging is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned launch packaging and install verification.

When should I use Suede Launch Packaging?

Suede Launch Packaging fits situations like: finished software work needs a clean public package (README; install command; GitHub Pages update; skill-pack release.

How do I install Suede Launch Packaging in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-launch-packaging -a claude-code`. Or copy the skill folder (skills/suede-launch-packaging in JasonColapietro/suede-creator-skills) into .claude/skills/suede-launch-packaging in your project. Claude Code loads it when a task matches its description.

How do I install Suede Launch Packaging in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-launch-packaging -a codex`. Or copy the skill folder (skills/suede-launch-packaging in JasonColapietro/suede-creator-skills) into .agents/skills/suede-launch-packaging in your project. Codex loads it when a task matches its description.

Can I use Suede Launch Packaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-launch-packaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-launch-packaging, .gemini/skills/suede-launch-packaging, .github/skills/suede-launch-packaging and .opencode/skills/suede-launch-packaging in your project.

What does Suede Launch Packaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Suede Launch Packaging is instructions for the agent only.

Does Suede Launch Packaging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Suede Launch Packaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Suede Launch Packaging use?

Suede Launch Packaging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Suede Launch Packaging use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Suede Launch Packaging?

Skills that share tags, products or a category with Suede Launch Packaging: Release Prep (johnhuang316/code-index-mcp, 1k stars), Project Release (swimmwatch/cloakbrowser-mcp, 164 stars), Release (PrefectHQ/fastmcp, 28k stars) and Reading Livekit Docs (livekit-examples/agent-starter-python, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Launch Packaging?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.