CLI Release

Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version, choose a release candidate, monitor a CLI release, or diagnose a failed CLI release. Do not use for TypeScript SDK Changesets releases or CLI source implementation.

31,162 stars 4,960 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ComposioHQ/composio --skill cli-release
Manual install
git clone --depth 1 https://github.com/ComposioHQ/composio.git /tmp/composio
mkdir -p ~/.claude/skills
cp -r /tmp/composio/.agents/skills/cli-release ~/.claude/skills/cli-release

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# CLI Release

Use this skill for the GitHub Release that powers the standalone `composio` binary and installer.

Read `references/release-workflow.md` before selecting a candidate or dispatching a workflow.

## Release Contract

- Never add a Changeset for `@composio/cli`; the package is ignored by Changesets and such files wedge `ts.release.yml`.
- Treat a merge to `next` that touches CLI paths as a beta build. Promote a tested beta with the `promote-stable` workflow action for the normal stable-release path.
- Never bump the private CLI `package.json` to select a binary version. For an
  intentional minor or major, build an explicitly versioned beta and promote
  that tested beta through the same stable path.
- Resolve beta tags and workflow state from GitHub immediately before acting. Never invent or reuse a stale candidate from memory.
- A stable promotion is a production write. If the user did not name the exact beta tag, present the resolved candidate and obtain explicit confirmation before dispatching it.
- Follow the release through asset verification and installation tests. Do not stop after the dispatch succeeds.

## Execution

1. Classify the request as automatic beta, manual beta, stable promotion, or recovery.
2. Run the playbook's read-only preflight and identify the exact source commit and release tag.
3. Dispatch only the requested workflow action and watch the resulting run to completion.
Read the full skill on GitHub

Details

Skill name
cli-release
Path
.agents/skills/cli-release/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the CLI Release skill do?

Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version, choose a release candidate, monitor a CLI release, or diagnose a failed CLI release. Do not use for TypeScript SDK Changesets releases or CLI source implementation.

How do I install the CLI Release skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ComposioHQ/composio --skill cli-release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is CLI Release popular?

It lives in ComposioHQ/composio, which has 31,162 GitHub stars and 4,960 forks, and is included in 1 curated skill list.

Related skills

Bug Fixing

31k

ComposioHQ/composio

Fix defects in the Composio SDK repository with focused reproduction, root-cause analysis, regression tests, and narrow verification. Use when the user reports a bug, failing test, CI regression, runtime defect, or incorrect SDK behavior. Do not use for new feature design or broad refactors.

Software DevelopmentIn 1 list5k

CLI Command

31k

ComposioHQ/composio

Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use cli-e2e there.

Software DevelopmentIn 1 list5k

CLI E2E

31k

ComposioHQ/composio

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

Testing & QAIn 1 list5k

Cross SDK Parity

31k

ComposioHQ/composio

Keep TypeScript and Python SDK behavior, generated client usage, public API naming, and docs examples aligned. Use when a change affects both SDKs, when generated client pins move, when comparing TS/Python behavior, or when a backend API contract changed. Do not use for single-language internal-only changes.

Software DevelopmentIn 1 list5k

Effect V4

31k

ComposioHQ/composio

Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all using the matching range effect@^4.1.0 — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/cli command surface, and the vendored effect source oracle. Use when writing or reviewing Effect v4 code, answering a v4 API question, working in effect/cli, defining a Context.Service service, modeling an error with Schema.TaggedError, bumping the Effect pins, or verifying an unfamiliar API against ts/vendor/effect. Do not use for CLI command UX/w

Software DevelopmentIn 1 list5k

Python Providers

31k

ComposioHQ/composio

Create, modify, test, or package Python provider adapters under python/providers, including framework-specific dependencies, public imports, type inference, and provider metadata. Use for Python provider work only; use python-sdk for core SDK changes.

Software DevelopmentIn 1 list5k

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.