add-integration

Automate third-party integration implementation for the Integrate TypeScript SDK.

4|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/integratedotdev/typescript-sdk --skill add-integration-integratedotdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-integration
Source: https://github.com/integratedotdev/typescript-sdk/tree/main/.agents/skills/add-integration
Command: npx skills add https://github.com/integratedotdev/typescript-sdk --skill add-integration-integratedotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually implementing new third-party integrations for the Integrate TypeScript SDK requires repetitive boilerplate creation, consistent wiring across core SDK files, and rigorous validation, which is time-consuming and prone to human error.

Core Features & Use Cases

  • End-to-end scaffolding: Generates all required integration files including factory, typed client interface, unit tests, and metadata entries.
  • Core SDK wiring: Guides updates to central SDK files (client, index, server, metadata) to ensure the new integration is properly registered and accessible.
  • Validation and compliance: Includes built-in verification steps to run type checks and test suites, ensuring the new integration meets SDK standards.
  • Use case: A developer needs to add a new Sentry integration to the SDK; this skill automates all boilerplate generation, core file updates, and validation to complete the task in minutes instead of hours.

Quick Start

Use the add-integration skill to implement a new GitHub integration for the Integrate TypeScript SDK by providing the integration spec including OAuth URLs, tool names, and default scopes.

Frequently Asked Questions about add-integration

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

FAQPage Schema
How do I add a new OAuth integration to a TypeScript SDK?

Adding a new OAuth integration to a TypeScript SDK requires generating factory files, typed client interfaces, and unit tests. You must also update core SDK metadata and exports to ensure the new integration is registered and accessible.

What is the best way to automate integration scaffolding for API-key authenticated services?

Automating integration scaffolding for API-key authenticated services involves generating boilerplate code, typed clients, and metadata entries. Using an automation skill ensures adherence to SDK coding standards and validates the setup by running type checks and test suites.

How do I wire core SDK files when adding a new third-party integration?

Wiring core SDK files when adding a new third-party integration requires updating central files like client, index, server, and metadata. This ensures the new integration module is properly registered, accessible, and compliant with SDK standards.

Can I validate new SDK integration modules against type checks and test suites automatically?

You can validate new SDK integration modules against type checks and test suites automatically by including built-in verification steps in your scaffolding workflow. This ensures the new integration meets SDK coding standards before deployment.

Does automated integration scaffolding work for both OAuth and API-key authenticated services?

Automated integration scaffolding works for both OAuth and API-key authenticated services. It generates the required factory files, typed client interfaces, and unit tests while updating core SDK metadata for either authentication method.

Why does manually adding third-party integrations to a TypeScript SDK take so long?

Manually adding third-party integrations to a TypeScript SDK takes long because it requires repetitive boilerplate creation and consistent wiring across core SDK files. Human error during this rigorous validation process further slows down development.