external-integration

Name: external-integration
Availability: InStock
Author: aquarius-wing

Verify external API, SDK, and library integrations before writing code.

Updated Feb 21, 2026

Search Tags:#testing #documentation #integration #verification #sdk #mapping #external-api

Ready to run

npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill external-integration-aquarius-wing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-integration
Source: https://github.com/aquarius-wing/polymarket-dev-tools/tree/main/.cursor/skills/external-integration
Command: npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill external-integration-aquarius-wing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrating with external systems (APIs, SDKs, libraries) often introduces risks like undocumented behavior, version drift, and unverified data mappings. This Skill enforces a verification-first approach to ensure correctness, security, and maintainability before any integration code is written.

Core Features & Use Cases

Validate external API docs by cross-checking parameters, responses, and versions.
Obtain real-world example data to drive precise mapping logic and reduce guesswork.
Apply to REST, GraphQL, and SDK-based integrations, including library upgrades and third-party changes.

Quick Start

Follow the verified process of documenting, validating, and mapping external integrations before implementing code.

Frequently Asked Questions about external-integration

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

FAQPage Schema

How do I verify external API integrations before writing any code?▼

Verify external API integrations by enforcing a verification-first workflow that cross-checks official documentation, acquires sample payloads, and validates version compatibility before implementing any mapping logic or code.

What is the best way to prevent version drift when upgrading SDK libraries?▼

Prevent version drift during SDK library upgrades by reviewing changelogs, checking version compatibility, and validating updated parameters and responses against official documentation before coding.

How do I map external API responses accurately using real-world sample data?▼

Map external API responses accurately by acquiring real-world sample payloads from the target system, then using that verified example data to drive precise mapping logic and reduce guesswork.

Can I use this verification workflow for both REST and GraphQL integrations?▼

Yes, you can use this verification workflow for both REST and GraphQL integrations, as well as SDK usage and library upgrades, ensuring version checks and changelog reviews across protocols.

What should I do if external API documentation does not match actual responses?▼

If external API documentation does not match actual responses, enforce a verification-first approach to cross-check parameters against real-world sample payloads, ensuring precise mapping logic before coding.

Why should I review changelogs before implementing third-party library upgrades?▼

Review changelogs before implementing third-party library upgrades to identify undocumented behavior, verify version compatibility, and ensure data mappings remain correct and secure.