integration-builder

Scaffold provider integration packages for the Open Mercato Integration Marketplace.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dominikpalatynski/test-ready-app --skill integration-builder-dominikpalatynski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-builder
Source: https://github.com/dominikpalatynski/test-ready-app/tree/main/.ai/skills/integration-builder
Command: npx skills add https://github.com/dominikpalatynski/test-ready-app --skill integration-builder-dominikpalatynski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds standardized, end-to-end integration scaffolds for new providers in the Open Mercato Integration Marketplace, reducing boilerplate and ensuring consistency across adapters, credentials, widgets, webhooks, health checks, i18n, and tests.

Core Features & Use Cases

  • Scaffold npm workspace packages under packages/<provider-package>/ with a complete project structure and configuration.
  • Implement core files and contracts, including adapter integration, DI setup, and module metadata.
  • Enable credential plumbing, widget injection, webhook processing, and health checks, plus i18n and tests.
  • Accelerate onboarding for new providers (e.g., Stripe, DHL, SendGrid) by providing a battle-tested template.

Quick Start

Run the generators to create a new provider package under packages/ and begin implementing the adapter and supporting artifacts.

Frequently Asked Questions about integration-builder

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

FAQPage Schema
How do I scaffold a new provider integration for the Open Mercato marketplace?

Scaffolding a new provider integration for the Open Mercato marketplace requires automating the creation of npm workspace packages under packages/, complete with adapters, credentials, widget injection, and webhook processing boilerplate.

What files and contracts are needed to register a new provider in an integration marketplace?

Registering a new provider in an integration marketplace requires core files for adapter integration, DI wiring, module metadata, hub contracts, health checks, and security compliance to ensure marketplace readiness.

How do I set up i18n and tests for npm workspace provider packages?

Setting up i18n and tests for npm workspace provider packages involves generating standardized internationalization configurations and test suites during the initial scaffolding process to ensure consistency across new adapters.

Can I use automated scaffolding to add webhook processing and health checks to provider integrations?

Yes, automated scaffolding can generate provider integrations that include built-in webhook processing and health check implementations, reducing boilerplate and ensuring consistent status mapping across marketplace packages.

What is the best way to reduce boilerplate when onboarding multiple providers like Stripe or DHL?

The best way to reduce boilerplate when onboarding multiple providers like Stripe or DHL is using a standardized scaffolding template that automates credential plumbing, widget injection, and DI wiring across npm workspace packages.

Does integration scaffolding enforce security and status mapping compliance for marketplace adapters?

Integration scaffolding enforces marketplace compliance by automatically applying security protocols, status mapping standards, and hub contracts to newly generated provider adapters within the workspace architecture.