Claude-skill-registry composio-ci-runs
Use when Codex needs to run CI/CD or cross-service automations through the Composio MCP server.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/composio-ci-runs" ~/.claude/skills/majiayu000-claude-skill-registry-composio-ci-runs && rm -rf "$T"
manifest:
skills/data/composio-ci-runs/SKILL.mdsource content
Composio CI Runs
Purpose
Drive multi-service workflows (deploy previews, QA notifications, release toggles) using the Composio-hosted MCP server defined under
servers/composio.
Setup Checklist
- Export
+COMPOSIO_ENDPOINT
and updateCOMPOSIO_API_KEY
with the websocket transport.mcp.json - Map pipelines (e.g.,
,deploy-preview
) inside the Composio dashboard and document their inputs inpromote-prod
.servers/composio/README.md - Confirm each connector account (GitHub, Slack, Vercel, etc.) has least-privilege scopes before triggering live runs.
Workflow
- Plan – outline prerequisites (tests pass, approvals granted) and choose the pipeline or action ID to invoke.
- Trigger – call
/runPipeline
with structured payloads and include an idempotency key when rerunning.invokeAction - Monitor – poll
for status; fetch logs when state isgetRun
orfailed
and summarize them.warning - Close out – after success, post a short confirmation back to the requester; if failure repeats after one retry, halt and request human review.
Notes
- Record every automation invocation in the related pull request or issue so humans can audit history.
- Keep secrets out of payloads—Composio resolves connector credentials internally.
- This skill often pairs with
(to prep PRs) andgithub-operations
(for smoke tests); coordinate order explicitly in the plan.playwright-automation