integrations-engineer

Name: integrations-engineer
Availability: InStock
Author: asfbay-bit

Design and implement third-party API integrations with a Planner/Builder/Tester workflow.

Updated Apr 12, 2026

Search Tags:#automation #api #integration #oauth #webhooks #tri-agent

Ready to run

npx skills add https://github.com/asfbay-bit/opchain --skill integrations-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integrations-engineer
Source: https://github.com/asfbay-bit/opchain/tree/main/skills/integrations-engineer
Command: npx skills add https://github.com/asfbay-bit/opchain --skill integrations-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrations Engineer helps teams design and implement robust third-party API integrations using a Planner/Builder/Tester tri-agent loop, enabling reliable connections to external services (OAuth flows, webhooks, API keys) and handling failures gracefully.

Core Features & Use Cases

Planner designs integration specs based on service docs
Builder implements clients, auth, and error handling
Tester validates against sandbox or live endpoints, with health checks

Quick Start

Provide the service you want to integrate and I will generate an end-to-end integration plan.

Frequently Asked Questions about integrations-engineer

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

FAQPage Schema

How do I design and implement third-party API integrations with OAuth flows and webhooks?▼

You can design and implement third-party API integrations using a Planner/Builder/Tester tri-agent workflow that generates structured integration specs, typed clients, and token management for OAuth flows and webhooks.

What is the best way to handle API token management and retry logic for external services?▼

The best way to handle API token management and retry logic is using a structured tri-agent workflow that enforces secure secret handling via KV/storage, automated retry logic, and continuous health checks for external service connections.

Can I use this approach to connect enterprise stacks like Salesforce, Slack, and payment services?▼

Yes, this approach applies to external service integrations across enterprise stacks, with concrete use cases including Salesforce, Slack, and payment services, handling both API key connections and OAuth flows.

How does the tri-agent workflow structure API integration development?▼

The tri-agent workflow structures API integration development by having a Planner design integration specs from service docs, a Builder implement clients and error handling, and a Tester validate against sandbox or live endpoints with health checks.

Do I need to provide API documentation before generating an integration plan?▼

Yes, you need to provide the external service you want to integrate, and the Planner agent will generate an end-to-end integration plan by designing integration specs based on the service documentation.

Why do my external API integrations fail when handling authentication and error handling?▼

External API integrations often fail due to unstructured token management and missing error handling, which this tri-agent workflow solves by enforcing typed clients, secure secret handling, and robust retry logic during implementation.