connector-creator

Scaffold local narai-primitives connectors with gather() and action interfaces.

10|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/narailabs/narai-primitives --skill connector-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connector-creator
Source: https://github.com/narailabs/narai-primitives/tree/main/plugins/connector-creator/skills/connector-creator
Command: npx skills add https://github.com/narailabs/narai-primitives --skill connector-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires narai-primitives/toolkit, @narai/connector-config, @narai/credential-providers, WebFetch/WebSearch/context7, and includes references (resource) components.

What problem does it solve?

Create a new custom connector for narai-primitives so Claude can call your SaaS API, internal REST/GraphQL service, CLI tool wrapper, shell-based workflow gate, or documented runbook without you building the connector framework by hand.

Core Features & Use Cases

  • Connector scaffolding for local use: Generates a minimal connector under .connectors/connectors/<slug>/ (project scope) or ~/.connectors/connectors/<slug>/ (user scope), updates config.yaml, and wires the connector into narai-primitives via gather().
  • Multi-flavor authoring from natural language: Detects whether you want an API/SDK wrapper, a shell-command approval gate, a composite orchestrator that chains existing connectors, or a knowledge-only runbook connector—and asks only the questions needed for the recognized shape.
  • Safety and operational guardrails: For shell-command gates and write/delete-capable action connectors, the toolkit policy gate and approval-mode behavior are supported automatically, minimizing unsafe “run first, ask later” outcomes.
  • Fallback for novel cases: For unrecognized services, performs lightweight research to inform the interview, then generates code from the connector contract.

Quick Start

Tell the AI: “Create a connector that lets me query Stripe from Claude and list my customers and charges.”

Frequently Asked Questions about connector-creator

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

FAQPage Schema
How do I create a custom API wrapper so Claude can call my SaaS endpoints?

You can scaffold a local narai-primitives connector that enables Claude to call custom services via gather() and connector action interfaces. The connector is generated under .connectors/ and wired into config.yaml, allowing Claude to query your SaaS API directly.

Can I wrap shell commands with an approval gate for Claude Code workflows?

Yes, you can build a shell-command approval gate connector. The toolkit policy gate and approval-mode behavior are supported automatically for shell-command gates, minimizing unsafe run first, ask later outcomes during execution.

What is a composite multi-connector workflow and when do I need one?

A composite multi-connector workflow is an orchestrator that chains existing connectors together. You need one when you want to scaffold a connector that sequences multiple existing API wrappers or shell-command gates into a single automated execution path.

Does this connector scaffolding work with both REST and GraphQL services?

Yes, connector scaffolding supports both REST and GraphQL endpoints. It detects whether you want an API/SDK wrapper, CLI-wrapped workflow, or documented runbook, then asks only the questions needed for the recognized shape to generate the connector code.

How do I configure credentials and config.yaml for a new local connector?

You configure credentials and config.yaml through safe first-run wiring. The scaffolding process requires YAML-frontmatter skill discovery and connector contract compliance, wiring the new connector into config.yaml and Claude Code PreToolUse gates automatically.

What happens when I try to scaffold a connector for an unrecognized service?

For unrecognized services, the scaffolder performs lightweight research to inform the interview. It then generates code from the connector contract, providing a fallback for novel cases where shape detection cannot identify a standard API or CLI wrapper pattern.