skills.rest
cogni-dao
cogni-daoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

third-party-integrator

Route third-party API integrations to Port/Adapter, App Capability, or MCP patterns.

4|5|Updated Nov 5, 2025
Search Tags:#integration#mcp#observability#architecture-patterns#contracts#port-adapter#app-capability
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill third-party-integrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: third-party-integrator
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/third-party-integrator
Command: npx skills add https://github.com/cogni-dao/cogni --skill third-party-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams consistently decide how to integrate 3rd-party APIs by routing work to the appropriate architectural pattern (Port/Adapter, App Capability, or MCP) before any implementation, ensuring maintainability, testability, and clear boundaries.

Core Features & Use Cases

  • Route signals using a decision matrix to pick the right pattern (Port/Adapter, App Capability, or MCP).
  • Provide canonical examples and wiring patterns from the repository (e.g., VCS, Polymarket/Kalshi, web search) to guide implementation.
  • Enforce contract-first design with API discovery, Zod-based validation, typed errors, and CI isolation via fake adapters.
  • Provide guidelines for observability, error handling, version pinning, and safe integration practices.

Quick Start

Describe a 3rd party service you want to integrate and I will route it to the proper pattern and generate the initial contracts.

Frequently Asked Questions about third-party-integrator

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

FAQPage Schema
What is the best way to architect third-party API integrations?▼

Third-party API integrations are best routed using a decision matrix to select an architectural pattern like Port/Adapter, App Capability, or MCP before writing code. This ensures maintainability, testability, and clear system boundaries.

How do I implement contract-first design for external SDKs and webhooks?▼

Contract-first design for external SDKs and webhooks is implemented using Zod schemas for validation, typed error handling, and API version pinning. This enforces strict data contracts prior to writing integration logic.

When do I need a Port/Adapter pattern versus an App Capability for API routing?▼

You need a Port/Adapter pattern versus an App Capability by applying a decision matrix to route integration signals. This matrix evaluates the specific external API, SDK, or webhook provider to determine the correct architectural fit.

Can I use fake adapters for CI isolation and observability in 3rd-party integrations?▼

Yes, you can use fake adapters for CI isolation and structured observability in 3rd-party integrations. This enables safe testing and monitoring of external API interactions without hitting live provider endpoints.

How to handle API version pinning and typed errors for external API providers?▼

API version pinning and typed errors for external API providers are handled through contract-first design. This approach enforces strict validation with Zod schemas and structured error handling to maintain integration stability.

Related Skills

Explore More Software Engineering Skills→
kennypallchizaca-coderkennypallchizaca-coder

03-routing-strategy

Define portable routing strategies with nested layouts and lazy loading.

Community
Intermediate
teocraftersteocrafters

zod-schema-creation

Generate Zod validation schemas with i18n error messages for API requests.

Official
Intermediate
nubivnubiv

cpp-testing

Create and configure C++ tests with GoogleTest, GoogleMock, CMake, and CTest.

Community
Advanced
HarriesHarries

mcporter

Discover and call MCP servers and tools from the terminal.

Community
Intermediate