Verified:GitHub

api-connector-builder

Create repository-native API connectors matching existing integration patterns.

Updated Sep 13, 2025

Search Tags:#test fixtures #api connector #integration architecture #rbac-aware security #config schema #auth model #pagination retries

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill api-connector-builder-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-connector-builder
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/api-connector-builder
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill api-connector-builder-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you build a new integration surface that matches the existing connector architecture of the target repository, so the new provider fits cleanly with its config schema, auth model, error handling, tests, and registration wiring.

Core Features & Use Cases

Repo-native connector replication: Builds the new integration by mirroring the house style from at least two existing connectors/providers, including layout and abstraction boundaries.
Integration-specific scope definition: Limits the implementation to only the surfaces the repo actually needs (auth flow, core read/write operations, pagination/rate limits, and webhook/polling model).
Production-quality integration wiring: Ensures registry/discovery hooks, config validation, and test fixtures match the repository’s conventions rather than being generic or vendor-derived.

Quick Start

Use the api-connector-builder skill to create a new Jira connector that follows the same integration pattern, config/auth model, and test style as the repo’s existing providers.

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 connector that matches my repository's existing integration patterns?▼

An API connector builder creates a repo-native integration surface by learning the host repository's existing connector architecture, then defining an integration-specific scope for auth flows, pagination, and core read/write operations that matches current conventions.

How do I implement pagination and retries for a new provider integration?▼

You implement pagination and retries by replicating the abstraction boundaries and error handling logic established by existing connectors in the repository, ensuring the new provider adheres to the house style rather than using generic vendor patterns.

What is the best way to define an integration-specific scope for a Jira or Slack connector?▼

The best way to define an integration-specific scope is to limit the implementation to only the surfaces the repository actually needs, such as the auth flow, core read/write operations, pagination, rate limits, and webhook or polling model.

Does the api-connector-builder support RBAC-aware security and custom config schemas?▼

Yes, the connector builder supports RBAC-aware security and config schema validation by ensuring these components match the repository's existing conventions rather than applying generic or vendor-derived configurations.

How do I write test fixtures for a new API integration that fit my codebase?▼

You write test fixtures by matching the repository's existing test style and conventions, ensuring the new provider's tests align with the house style discovered from at least two existing connectors in the codebase.