Cross-SDK Parity
SkillDev toolsThis skill keeps changes to the TypeScript and Python SDKs consistent with each other. Once added, your AI can align behavior, public API naming, generated client usage, and docs examples across both SDKs. It is meant for changes that touch both languages, not single-language internal work.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill and use it whenever a change affects both SDKs, generated client pins move, you need to compare TypeScript and Python behavior, or a backend API contract changed. Skip it for changes that are internal to a single language.
Then ask your AI: use the Cross-SDK Parity skill
What your AI can do with it
- Keep TypeScript and Python SDK behavior aligned
- Match public API naming across both SDKs
- Keep docs examples consistent between the two languages
- Compare TypeScript and Python behavior for a change
- Update generated client usage when client pins move
- Apply backend API contract changes to both SDKs
What this skill tells your AI
The instructions your AI receives, as published by composiohq/composio in .agents/skills/cross-sdk-parity/SKILL.md and read by ahel’s review.
Use this skill when TypeScript and Python must stay aligned.
Read references/parity-workflow.md before changing shared SDK behavior or generated client pins.
Signals
- GitHub stars
- 30k
- Forks
- 5k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
cross-sdk-parity- Source
- github.com/composiohq/composio