How do I install the Composiohq Composio CLI Release Promotion skill?

Run npx skillmds@latest add tuyv/composiohq-composio-cli-release-promotion in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Composiohq Composio CLI Release Promotion safe to use?

SkillMD's automated safety review verdict for this skill is WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Composiohq Composio CLI Release Promotion?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Composiohq Composio CLI Release Promotion free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Composiohq Composio CLI Release Promotion?

tuyv (@tuyv) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Composiohq Composio CLI Release Promotion by tuyv

Name: Composiohq Composio CLI Release Promotion
Author: tuyv

File contents

CLI Release Promotion

Use this skill when working on the Composio CLI release pipeline or when an agent needs to test a beta CLI binary and trigger the final stable promotion.

What This Covers

Finding the beta release tag produced from the Changesets release PR
Smoke-testing that beta release through the existing installation path
Promoting only an existing beta release to a stable CLI release

Beta Release Model

Beta releases are created by .github/workflows/build-cli-binaries.yml
They are triggered from the Changesets release PR titled Release: update version
Beta tags use the form @composio/cli@<version>-beta.<pr-number>
Stable releases are promoted manually from an existing beta tag through the same workflow

Validate The Beta

Pick the beta tag you intend to promote, then test it before promotion.

Use the existing installation health check workflow if you only need repo-side validation:

gh workflow run cli.test-installation.yml -f version='@composio/cli@0.2.18-beta.123'

For a local smoke test, install that exact beta binary and verify the upgrade path:

curl -fsSL https://raw.githubusercontent.com/ComposioHQ/composio/main/install.sh | bash -s -- '@composio/cli@0.2.18-beta.123'
composio --version
composio upgrade --beta

composio upgrade --beta should stay on the beta channel and resolve the newest prerelease, not the latest stable release.

Promote To Stable

Only promote by referencing an existing beta tag.

Run the CLI binary workflow manually with that beta tag:

gh workflow run build-cli-binaries.yml -f beta_tag='@composio/cli@0.2.18-beta.123'

The workflow will:

verify the beta release exists
reject non-prerelease tags
derive the stable tag @composio/cli@0.2.18
rebuild from the beta release's recorded commit
publish the stable GitHub release

Reference Files

Read these when you need implementation details:

.github/workflows/build-cli-binaries.yml
ts/packages/cli/src/commands/upgrade.cmd.ts
ts/packages/cli/src/services/upgrade-binary.ts
ts/docs/internal/release.md

---name: composiohq-composio-cli-release-promotiondescription: Validate a Composio CLI beta release and promote it to a stable release by dispatching the CLI binary workflow with an existing beta tag.---# CLI Release PromotionUse this skill when working on the Composio CLI release pipeline or when an agent needs to test a beta CLI binary and trigger the final stable promotion.## What This Covers- Finding the beta release tag produced from the Changesets release PR- Smoke-testing that beta release through the existing installation path- Promoting only an existing beta release to a stable CLI release## Beta Release Model- Beta releases are created by `.github/workflows/build-cli-binaries.yml`- They are triggered from the Changesets release PR titled `Release: update version`- Beta tags use the form `@composio/cli@<version>-beta.<pr-number>`- Stable releases are promoted manually from an existing beta tag through the same workflow## Validate The BetaPick the beta tag you intend to promote, then test it before promotion.Use the existing installation health check workflow if you only need repo-side validation:```bashgh workflow run cli.test-installation.yml -f version='@composio/cli@0.2.18-beta.123'```For a local smoke test, install that exact beta binary and verify the upgrade path:```bashcurl -fsSL https://raw.githubusercontent.com/ComposioHQ/composio/main/install.sh | bash -s -- '@composio/cli@0.2.18-beta.123'composio --versioncomposio upgrade --beta````composio upgrade --beta` should stay on the beta channel and resolve the newest prerelease, not the latest stable release.## Promote To StableOnly promote by referencing an existing beta tag.Run the CLI binary workflow manually with that beta tag:```bashgh workflow run build-cli-binaries.yml -f beta_tag='@composio/cli@0.2.18-beta.123'```The workflow will:- verify the beta release exists- reject non-prerelease tags- derive the stable tag `@composio/cli@0.2.18`- rebuild from the beta release's recorded commit- publish the stable GitHub release## Reference FilesRead these when you need implementation details:- `.github/workflows/build-cli-binaries.yml`- `ts/packages/cli/src/commands/upgrade.cmd.ts`- `ts/packages/cli/src/services/upgrade-binary.ts`- `ts/docs/internal/release.md`

Frequently asked questions

Composiohq Composio CLI Release Promotion