typescript-providers

Implement and test TypeScript provider packages for AI framework adapters in the Composio monorepo.

30.0k|4.8k|Updated Feb 23, 2024
One-click install
npx skills add https://github.com/ComposioHQ/composio --skill typescript-providers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-providers
Source: https://github.com/ComposioHQ/composio/tree/main/.agents/skills/typescript-providers
Command: npx skills add https://github.com/ComposioHQ/composio --skill typescript-providers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Working on Composio's TypeScript provider packages requires knowing the monorepo's conventions for creating providers, keeping framework-native tool formats intact, and running the right verification commands. This Skill supplies that workflow so provider changes stay consistent and isolated from core.

Core Features & Use Cases

  • Provider Scaffolding: Create new provider packages under ts/packages/providers using the pnpm create:provider command, with an optional agentic flag.
  • Implementation Rules: Enforces preserving framework-native tool formats, keeping provider-specific code and dependencies out of core, and updating docs when public usage changes.
  • Verification Workflow: Runs typecheck, tests, and package builds filtered to the specific provider, with guidance on testing wrapping, tool-call handling, and schema conversion.
  • Use Case: When adding a new adapter for a framework like Mastra or updating the OpenAI Agents provider, follow the documented workflow to implement, test, and verify the change without leaking dependencies into @composio/core.

Quick Start

Ask the agent to implement a change to a TypeScript provider package under ts/packages/providers and follow the provider workflow reference for verification.

Frequently Asked Questions about typescript-providers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new TypeScript provider package in Composio?▼

Run pnpm create:provider <provider-name> from the monorepo root, optionally adding the --agentic flag. The new provider is scaffolded under ts/packages/providers/ where you implement the framework adapter.

How do I test changes to a Composio provider package?▼

Run pnpm --filter @composio/<provider> typecheck and pnpm --filter @composio/<provider> test, then pnpm build:packages. Add tests for wrapping, tool-call handling, schema conversion, and framework version compatibility when relevant.

Which AI frameworks have Composio TypeScript providers?▼

Providers exist for OpenAI Agents, Anthropic, Google, LangChain, Mastra, Vercel AI SDK, LlamaIndex, Cloudflare, and Claude Agent SDK. Each lives as a separate package under ts/packages/providers.

Can provider-specific dependencies be added to @composio/core?▼

No. Provider-specific code and dependencies must stay inside the provider package to avoid leaking them into core. Core-only changes are out of scope for this workflow and handled separately.

When should I not use the TypeScript providers workflow?▼

Do not use it for core-only changes to @composio/core that do not touch provider packages. For providers with Python counterparts, use the cross-sdk-parity skill to keep behavior aligned across SDKs.