Csm publish

Skill cloudsmith-labs/claude-code-skills/skills/csm-publish

Publish (push/upload) packages to Cloudsmith and configure package managers to pull from Cloudsmith registries. Use when the user wants to upload a package or artifact of any format (Python, npm, Debian, RPM, Docker, Maven, Helm, Cargo, NuGet, Go, raw files, and more), set up .npmrc/pip/Docker/Maven/Helm to install from a Cloudsmith repo, or wire publishing into CI.From its SKILL.md

Install

npx -y skills add cloudsmith-labs/claude-code-skills --skill csm-publish

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

Publish to Cloudsmith

Read ../../references/cloudsmith-core.md first: verify cloudsmith-state is working (otherwise run the setup skill).

Push a package

The general shape is:

cloudsmith push <format> OWNER/REPO[/<distro>/<release>] <file> [format flags]

Identify the format from the file/type the user wants to publish. Formats with per-format arguments (deb/rpm/alpine need a distro path, maven needs a POM, docker uses the registry instead) are summarised in references/formats.md.
Always check the exact flags first with cloudsmith push <format> --help — formats have specific required options and they change between CLI versions.
Run the push, then confirm sync completed: cloudsmith status OWNER/REPO/SLUG_PERM (the push output includes the identifier; --wait-interval/sync flags are available on push — see help).
If sync fails, show the failure reason from status, and offer cloudsmith resync.

Useful push options (most formats): --republish (overwrite same version — confirm first, it replaces an existing artifact), --tags tag1,tag2.

Configure a package manager to pull

For "how do I install from my Cloudsmith repo" requests, generate the config snippet for their tool from references/registry-config.md. Ask for OWNER/REPO and the format if not given. Point entitlement-token-based read access (for customers/CI without user accounts) at the csm-repos skill.

CI publishing

For CI pipelines, recommend:

the official cloudsmith-io/action for GitHub Actions, or the CLI in any CI (installed via pip) with CLOUDSMITH_API_KEY provided as a CI secret — never committed;
OIDC-based authentication for GitHub Actions where the org has it configured (no long-lived key in CI) — see https://docs.cloudsmith.com for "OIDC".