add-integration

Automates adding a service to Sim by generating tools, blocks, icons, triggers, registries and docs.

Updated Apr 16, 2026

Search Tags:#automation #workflow #api #integration #tooling #sim

Ready to run

npx skills add https://github.com/tunacosgun/sim --skill add-integration-tunacosgun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-integration
Source: https://github.com/tunacosgun/sim/tree/main/.agents/skills/add-integration
Command: npx skills add https://github.com/tunacosgun/sim --skill add-integration-tunacosgun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of adding a new service integration to Sim, including tools, blocks, icons, triggers, and registries, so teams can onboard services quickly and consistently.

Core Features & Use Cases

End-to-end integration: research, tool creation, block configuration, icon addition, triggers (optional), registration, and docs generation.
Reusable automation: apply the same pattern to any service and ensure consistency across registries.
Use Case: A team wants to onboard a new payment service, automatically creating tools, blocks, and docs aligned with existing conventions.

Quick Start

Provide a service name and API docs; I will generate tools, blocks, icons, and registries to add the integration.

Frequently Asked Questions about add-integration

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

FAQPage Schema

How do I automate API integration for a new service end-to-end?▼

To automate API integration end-to-end, you provide a service name and API docs to generate tools, blocks, icons, triggers, and registries. This enforces consistent schemas and coordinates cross-cutting steps from research to publishing docs.

What does end-to-end service onboarding require for workflow automation?▼

End-to-end service onboarding requires research, tool creation, block configuration, icon addition, optional triggers, registration, and documentation generation. Automating this process ensures new services are added quickly and consistently across registries.

Can I use this automation to add triggers and blocks for any API service?▼

Yes, you can use this automation to add triggers and blocks for any API service. The reusable pattern applies to introducing new services across tools, blocks, and triggers while enforcing no-guess schemas and documenting expectations.

What is the best way to generate consistent documentation for API integrations?▼

The best way to generate consistent documentation for API integrations is to automate the process alongside tool and block creation. This ensures docs are published automatically and aligned with existing conventions during service onboarding.

Do I need to provide API docs to set up a new integration?▼

Yes, you need to provide API docs and a service name to set up a new integration. This ensures the automation enforces no-guess schemas and accurately documents expectations when generating tools, blocks, and registries.