skills.rest
Jamkris
JamkrisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

api-connector-builder

Implement a repo-native API connector matching an existing integration pattern.

86|21|Updated Feb 9, 2026
Search Tags:#automation#api#integration#scaffolding#connectors#repo-pattern
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill api-connector-builder-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-connector-builder
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/api-connector-builder
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill api-connector-builder-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build a repo-native API connector that mirrors an existing integration pattern, enabling rapid, consistent additions without creating new architectures.

Core Features & Use Cases

  • Inspects the host repo to map file layouts, config models, auth patterns, error handling, tests, and registry wiring.
  • Defines and limits scope to the host pattern when adding new integrations (e.g., Jira, Slack) to ensure consistency.
  • Builds in-repo native layers (config/schema, client/transport, mapping, registration, and tests) to align with the target project.

Quick Start

Review the target repository and implement a new connector that mirrors its existing 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 build a new API connector that matches existing integration patterns in my repo?▼

To build a new API connector that matches existing integration patterns, inspect at least two existing connectors to map file layouts, auth models, and testing styles, then implement the new connector using those repo-native layers.

What is the best way to add Jira or Slack integrations without creating new architectures?▼

The best way to add Jira or Slack integrations without creating new architectures is to mirror an existing integration pattern by defining scope to match the host project's config schema, error handling, and registry wiring.

How does mapping abstraction boundaries work when adding API connectors?▼

Mapping abstraction boundaries involves inspecting existing connectors to identify separation between config/schema, client/transport, mapping, registration, and tests, ensuring your new API connector respects these same host project boundaries.

Do I need existing connectors in my repo to scaffold a new API integration?▼

Yes, you need at least two existing connectors in your repo to scaffold a new API integration, because the process requires inspecting them to map file layout, config models, and testing style for consistency.

What are the limitations of using repo-native patterns for API connector scaffolding?▼

The limitation of repo-native API connector scaffolding is that it restricts scope to the host pattern, meaning it cannot introduce new architectures and strictly requires aligning with existing config schema, auth models, and registry wiring.

Related Skills

Explore More Software Engineering Skills→
MomoDavilukeMomoDaviluke
2

api-connector-builder

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

Community
Advanced
stharroldstharrold

initialize-repository

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

Community
Intermediate
mjunaidcamjunaidca
27

building-mcp-servers

Build MCP servers in TypeScript or Python with tool schemas and transports.

Community
Advanced
luongldptitluongldptit

api-connector-builder

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

Community
Intermediate