Skip to content
cccskills
FreePublished on GitHub

cli-release

Build beta versions of the Composio CLI, promote a tested beta to a stable release, and investigate failed releases. Guides verification of published binaries and installation tests through the Build CLI Binaries workflow.

OriginalShow the original description

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.

See how to install

Good for

  • Build a CLI beta release
  • Promote a tested beta to stable
  • Verify release assets and installation
  • Investigate and recover a failed release

Files included (2)

  • SKILL.md2.1 KB
  • references/release-workflow.md7.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.
  4. Verify the published release and downstream checks named in the playbook.
  5. Report the released tag, source beta or commit, workflow URL, asset state, install-test result, and any remaining follow-up.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

bug-fixing

FreeSummary

Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.

  • Reproducing and fixing reported SDK bugs
  • Investigating failing tests
  • Fixing regressions in automated CI checks
ComposioHQ/composio30.6KUpdated Oct 18, 2026

cli-command

FreeSummary

Design, implement, and review Composio CLI commands, including user interactions, output, errors, and configuration. It guides command wiring and service changes using Effect and effect/cli, with references for implementation patterns.

  • Designing CLI command behavior and output
  • Implementing command wiring with Effect
  • Reviewing configuration and error handling
ComposioHQ/composio30.6KUpdated Oct 18, 2026

cli-e2e

FreeSummary

Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.

  • Add end-to-end tests for CLI commands
  • Debug unexpected CLI test output
  • Keep test data isolated between tests
ComposioHQ/composio30.6KUpdated Oct 18, 2026

composio

FreeSummary

Set up and use Composio to connect AI agents with apps such as Gmail, Slack, and Notion. Selects guidance for personal accounts or product integrations, covering setup, app operations, troubleshooting, and migration.

  • Connect a personal AI agent to apps
  • Integrate account connections into a product
  • Diagnose failed connections or tool calls
ComposioHQ/composio30.6KUpdated Oct 18, 2026

cross-sdk-parity

FreeSummary

Keep TypeScript and Python SDKs consistent when shared behavior or backend APIs change. Aligns public API names, use of generated clients, and documentation examples, including updates to the fixed versions of generated clients.

  • Align a change across both SDKs
  • Compare TypeScript and Python behavior
  • Update fixed versions of generated clients
ComposioHQ/composio30.6KUpdated Oct 18, 2026

docs-decisions

FreeSummary

Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.

  • Update Composio documentation content and changelogs
  • Revise Fumadocs settings and documentation automation prompts
  • Record or update documentation decisions
ComposioHQ/composio30.6KUpdated Oct 18, 2026

See all skills by ComposioHQ

Report a problem with this skill