CLI Release
SkillDev toolsOnce added, your AI can release and recover the Composio CLI binary from start to finish. It builds beta versions, promotes them to stable releases, and fixes releases that fail along the way. All of the release steps run through GitHub workflows.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, ask your AI to build a beta or publish a stable release of the Composio CLI binary. It will run the release steps through GitHub workflows and handle recovery if something fails.
Then ask your AI: use the CLI Release skill
What your AI can do with it
- Build beta versions of the Composio CLI binary
- Promote a beta build to a stable release
- Select the right beta tag for a release
- Verify release assets and installations
- Recover from failed releases
What this skill tells your AI
The instructions your AI receives, as published by composiohq/composio in .agents/skills/cli-release/SKILL.md and read by ahel’s review.
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/clior@composio/cli-local-tools; both packages are ignored by Changesets and such files wedgets.release.yml. - Treat a merge to
nextthat touches CLI paths as a beta build. Promote a tested beta with thepromote-stableworkflow action for the normal stable-release path. - Never bump the private CLI
package.jsonto 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
- Classify the request as automatic beta, manual beta, stable promotion, or recovery.
- Run the playbook's read-only preflight and identify the exact source commit and release tag.
- Dispatch only the requested workflow action and watch the resulting run to completion.
- Verify the published release and downstream checks named in the playbook.
- Report the released tag, source beta or commit, workflow URL, asset state, install-test result, and any remaining follow-up.
Signals
- GitHub stars
- 30k
- Forks
- 5k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
cli-release- Source
- github.com/composiohq/composio