integration-builder

Scaffold npm packages and implement adapter contracts for Open Mercato integrations.

1.6k|354|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill integration-builder-open-mercato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-builder
Source: https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/integration-builder
Command: npx skills add https://github.com/open-mercato/open-mercato --skill integration-builder-open-mercato

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new integration provider packages for the Open Mercato Integration Marketplace, ensuring consistency and adherence to standards.

Core Features & Use Cases

  • Scaffolds New Packages: Automates the creation of directory structures and essential files (package.json, tsconfig.json, src/index.ts, etc.) for new integrations.
  • Guides Implementation: Provides detailed instructions and templates for core files like integration.ts, adapter implementations, webhook handlers, health checks, and UI widgets.
  • Ensures Compliance: Enforces adherence to adapter contracts, naming conventions, and marketplace requirements.
  • Use Case: When you need to add a new payment gateway (e.g., "Stripe Connect") or a shipping carrier (e.g., "FedEx") to Open Mercato, this Skill provides the framework and guidance to build the necessary integration package.

Quick Start

Use the integration-builder skill to create a new payment gateway integration for Stripe Connect.

Frequently Asked Questions about integration-builder

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

FAQPage Schema
How do I build a custom integration package for the Open Mercato marketplace?

To build a custom integration package, scaffold an npm package with the required directory structure and implement the specific adapter contracts for categories like payment, shipping, or data_sync. This ensures your integration complies with marketplace standards.

What adapter categories are supported when developing an Open Mercato integration?

Supported adapter categories include payment, shipping, data_sync, communication, storage, and webhook. Each category requires specific contract implementations to properly process data and interact with the marketplace framework.

How do I scaffold an npm package for a new payment gateway integration?

Scaffolding an npm package automates the creation of essential files like package.json, tsconfig.json, and src/index.ts. This provides the baseline module structure needed to start implementing your payment gateway adapter.

Do I need to implement health checks and webhooks for an Open Mercato integration?

Yes, implementing health checks and webhook processing is required. The integration framework provides templates and guidance for handling these components, along with credential management and UI widget injection, to ensure full marketplace compliance.

Can I add internationalization and tests to my Open Mercato integration package?

Yes, adding internationalization and tests is part of the guided development process. The framework enforces strict package naming conventions and module structure, ensuring your integration is fully tested and localized before marketplace submission.

What is the correct module structure for an Open Mercato integration provider package?

The correct module structure includes specific core files such as integration.ts, adapter implementations, and webhook handlers. Adhering to these strict package naming conventions and module structures ensures your package is accepted into the marketplace.