What problem does it solve?
Maintaining two SDKs in different languages often leads to drift: mismatched public APIs, divergent generated client versions, and inconsistent docs examples. This Skill provides a structured workflow to keep the TypeScript and Python Composio SDKs behaviorally aligned whenever a change affects both.
Core Features & Use Cases
- Public Contract Comparison: Check tools, sessions, connected accounts, auth configs, provider wrappers, error shapes, and docs examples across both SDKs.
- Generated Client Bump Workflow: Step-by-step commands for updating @composio/client pins in pnpm-workspace.yaml and composio-client in pyproject.toml, setup.py, and uv.lock.
- Naming Conventions: Enforces camelCase for TypeScript and snake_case for Python while preserving backend wire names in generated clients.
- Use Case: When a backend API contract changes, use this Skill to update the generated client pins in both SDKs, verify naming conventions, and run import/typecheck checks to confirm parity.
Quick Start
Ask the agent to verify that the TypeScript and Python SDKs expose equivalent behavior for a recent API change and to update the generated client pins in both packages.