api-connector-builder

Generate repo-native API connector code matching existing integration patterns.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill api-connector-builder-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-connector-builder
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/api-connector-builder
Command: npx skills add https://github.com/luongldptit/move-ticket --skill api-connector-builder-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, out-of-place API integrations that break a repository's established patterns when adding new third-party service connectors or providers.

Core Features & Use Cases

  • Pattern Alignment: Guides you to match the host repo's existing connector layout, config schema, auth model, error handling, and test style.
  • End-to-End Implementation: Covers all required layers including config validation, client transport, mapping, registration, and test creation.
  • Use Case: If you need to add a new Jira integration to a project that already has existing Slack and GitHub providers, this Skill ensures the new connector fits seamlessly without requiring refactors to existing code.

Quick Start

Use the api-connector-builder skill to build a new Slack provider that exactly matches the structure, config schema, and test patterns of the existing GitHub provider in the current repository.

Frequently Asked Questions about api-connector-builder

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

FAQPage Schema
How do I add a new API integration that matches existing repo patterns?

To add a new API integration matching existing repo patterns, generate connector code that mirrors the repository's established file layouts, config models, auth flows, error handling, and test styles without introducing new architectural frameworks.

What is the best way to ensure code consistency when adding third-party service connectors?

The best way to ensure code consistency when adding third-party service connectors is to apply pattern matching against the codebase's existing providers, aligning config validation, client transport, mapping, and registry wiring end-to-end.

Does this approach require refactoring existing integrations like Slack or GitHub providers?

No, this approach does not require refactoring existing integrations like Slack or GitHub providers. It produces repo-native connector code that fits seamlessly into the established integration architecture without modifying current providers.

Can I use this to build a Jira integration for a project with established provider patterns?

Yes, you can build a Jira integration for a project with established provider patterns. It guides the creation of config validation, client transport, mapping, and test creation layers matching the existing codebase architecture.

What layers are covered when building a new API provider connector?

Building a new API provider connector covers all required layers including config validation, client transport, mapping, registration, and test creation. This ensures the new connector matches the repository's existing layout and schema.