skills.rest
MomoDaviluke
MomoDavilukeCOMMUNITY
Explore all skills by this author →
GitHub

api-connector-builder

Automate API connector creation by mirroring the host project's integration pattern.

2|Updated Mar 3, 2026
Search Tags:#testing#architecture#integration#pattern#connector#repo-native
One-click install
npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill api-connector-builder-momodaviluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-connector-builder
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/api-connector-builder
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill api-connector-builder-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build a new API connector or provider by matching the target repo's existing integration pattern exactly, avoiding architecture drift.

Core Features & Use Cases

  • Connector layout, config schema, auth model, error handling, test style, and registration/discovery wiring aligned with the host repo.
  • Use Case: Add a Jira connector following the repo's existing connector pattern.
  • Use Case: Create a new integration for an API using the repo's standard surface.

Quick Start

Implement a repo-native API connector by mirroring the host project's existing connector pattern.

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 without causing architecture drift?▼

An API connector follows a host project's existing integration pattern to ensure consistency. It mirrors the repository's file layouts, config models, authentication schemes, error handling, test styles, and registry wiring to prevent architecture drift.

How do I create a new API integration that matches my repository's existing pattern?▼

You create a new API integration by mirroring the host repository's standard connector surface. This ensures the new integration aligns its layout, config schema, auth model, error handling, test style, and registration wiring with existing project conventions.

What's the best way to build a Jira connector following an existing repo pattern?▼

The best way to build a Jira connector following a repo pattern is to automate the creation process by mirroring the host project. This applies the repository's standard layout, config, auth, error handling, tests, and discovery wiring to the new connector.

Does building a repo-native API connector require matching existing test styles and config models?▼

Yes, building a repo-native API connector requires matching existing test styles and config models. It satisfies requirements for consistent file layouts, authentication schemes, error handling, test styles, and registry wiring within the target repository.

When do I need to use a repo-native connector builder for API integration?▼

You need a repo-native connector builder when adding new API integrations across projects that require pattern-consistent connectors. It prevents architecture drift by ensuring any new provider matches the target repo's exact integration pattern.

Related Skills

Explore More Software Engineering Skills→
vrcmsvrcms
1

api-connector-builder

Standardize new API connectors with repository-native patterns and authentication models.

Community
Intermediate
stharroldstharrold

initialize-repository

Replicate workflow-system context from a source repository to a new target repository.

Community
Intermediate
t-stringst-strings

Global Error Handling

Centralize error types, logging, and exception flow across modules.

Official
Basic
klu-devklu-dev
2

api-connector-builder

Generate API connectors by adapting existing repository integration patterns.

Community
Intermediate