skills.rest
maverox
maveroxCOMMUNITY
Explore all skills by this author →
Website𝕏@M4veroXGitHub

connector-integration-validator

Validate connector integrations against official API documentation and UCS patterns.

Updated Dec 11, 2025
Search Tags:#authentication#integration#validation#macros#connector#api-docs#ucs
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill connector-integration-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connector-integration-validator
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/connector-integration-suite/skills/connector-integration-validator
Command: npx skills add https://github.com/maverox/claude-plugins --skill connector-integration-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate connector integration changes against official API documentation and UCS architecture patterns to ensure correctness and compliance across authentication, payment flows, amount converters, and status mappings.

Core Features & Use Cases

  • Verifies authentication patterns, flow implementations (Authorize, Capture, Void, Refund), and status mappings against API docs.
  • Checks alignment with UCS architecture and macro-based prerequisites.
  • Auto-activates for common review scenarios and accelerates PR reviews.

Quick Start

Provide a PR diff or connector name to run a UCS-aligned validation against the official API docs and UCS patterns.

Frequently Asked Questions about connector-integration-validator

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

FAQPage Schema
How do I validate connector integration changes against API documentation?▼

Connector integration validation checks PR changes against official API documentation and UCS architecture patterns. It verifies authentication, payment flows, amount converters, and status mappings to return a structured UCS-compliant validation report.

What payment flow implementations does UCS connector validation check?▼

UCS connector validation checks Authorize, Capture, Void, and Refund flow implementations. It verifies these payment flows against official API documentation and validates status mappings to ensure compliance with UCS architecture patterns.

Can I validate connector authentication patterns using a PR diff?▼

Yes, you can validate connector authentication patterns by providing a PR diff or connector name. The validator runs a UCS-aligned validation against official API docs and checks authentication pattern compliance automatically.

What's the best way to ensure connector compliance with UCS architecture patterns?▼

The best way to ensure UCS compliance is running an automated validation against official API docs and macro-based prerequisites. This checks authentication, payment flows, amount converters, and status mappings within PR changes or specified connectors.

Why does my connector status mapping fail UCS validation?▼

Connector status mapping validation fails when implementations do not align with official API documentation or UCS architecture patterns. The validator checks status mappings within PR changes and returns a structured report identifying specific compliance gaps.

Related Skills

Explore More Software Engineering Skills→
maveroxmaverox

connector-code-quality-review

Review connector integration changes for UCS architecture, security, and conventions.

Community
Advanced
maveroxmaverox

plan-connector-implementation

Plan and validate payment connector implementations from API specs.

Community
Advanced
maveroxmaverox

research-api-docs

Extract structured API specifications from payment connector documentation into spec.md.

Community
Advanced
airbytehqairbytehq
132

airbyte-sdk-reference

Reference Airbyte per-connector typed SDK APIs and usage patterns.

Official
Intermediate