sylphxai/skills

build-distribution-readiness

Prepare and verify a signed product package for its distribution channels — install, update, uninstall, and live readback. Use when shipping a binary, installer, package, or store build. Do not use to write store listing copy or screenshots.

First seen Aug 22, 2026

Installation

$ npx skills add sylphxai/skills --skill build-distribution-readiness

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sylphxai/skills · top by installs.

npx skills add sylphxai/skills

Browse all from sylphxai/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,200 B
  • docs SUMMARY.md 279 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Build Distribution Readiness

Local build, upload, review, publication, indexing, installation, and live behavior are different facts. A signed artifact that cannot install, update, or uninstall is not ready. Current official channel docs own the details.

Open [distribution channel matrix](references/distribution-channel-matrix.md) for app stores, web/PWA, Microsoft Store, Steam, and consoles. Open [CLI and package distribution](references/cli-and-package-distribution.md) for direct download, npm, Homebrew, WinGet, Cargo, or OCI. Open [desktop and PC release readiness](references/desktop-and-pc-release-readiness.md) for signing, installers, and launchers. Open [release communication](references/release-communication.md) when the release needs a changelog or migration notice.

Use optimize-store-listing for listing copy. Use launch-readiness for the go/no-go on the exact build.