Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cli Distribution And Packaging

DSecurity

Plan how a CLI ships and updates — single static binary vs runtime package, cross-compilation, install channels (Homebrew/Scoop/winget/npm/pipx), a build-stamped --version, and a safe installer. Use when making a tool installable and keeping it current.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentspythonrustgoshellnodedevops

Works with

cli

Security Analysis

D50/100
criticalPipes output to a shell interpreter
criticalDownloads and executes remote scripts — classic supply chain attack

Pro shows the line behind each finding and how to fix it

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill cli-distribution-and-packaging --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cli Distribution And Packaging?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Cli Distribution And Packaging
[![Security: D — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-cli-distribution-and-packaging/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-cli-distribution-and-packaging)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: cli-distribution-and-packaging
description: "Plan how a CLI ships and updates — single static binary vs runtime package, cross-compilation, install channels (Homebrew/Scoop/winget/npm/pipx), a build-stamped --version, and a safe installer. Use when making a tool installable and keeping it current."
---

# CLI Distribution & Packaging

## Pick the distribution form

| Language | Form | Why |
|---|---|---|
| Go / Rust (compiled) | **Single static binary** per OS/arch | Lowest install friction, no runtime to install |
| Node | **npm** package with a `bin` entry | Users already have npm |
| Python | **pipx** (isolated app install) | Avoids polluting the user's Python env |

A static single binary is the gold standard when the language can produce one — name the friction trade if you can't.

## Cross-compile the matrix

Produce per-**OS/arch** artifacts (at least macOS arm64+x64, Linux x64+arm64, Windows x64) with **checksums** and consistent archive names. Keep the build reproducible. CI wiring of this job + code-signing route to `devops-cicd`.

## Publish where users look

- macOS/Linux → **Homebrew** (tap + formula).
- Windows → **Scoop** and/or **winget**.
- Cross-platform script tools → **npm** / **pipx**.

Keep each channel's version + checksum in sync with the release so they never drift.

## `--version` and updates

- Stamp the binary at **build time** with **semver + commit**; `--version` must report exactly what's running (a version without the commit makes bug triage guesswork).
- Choose an update story: let the package manager upgrade, or add an **update check/notice** — and make sure it never blocks or surprises a non-interactive run.

## `curl | sh` installers (only if safe)

If you ship one, it must **verify a checksum/signature**, select the correct OS/arch artifact, install to a sane path, and be auditable. An unverified installer is arbitrary code execution.

Package the generated **shell completions** + a **man page** with the release. See the distribution tree in [`../../knowledge/cli-tooling-decision-trees.md`](../../knowledge/cli-tooling-decision-trees.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →