kortix-connectors

Register and manage service connectors in a SQLite-backed registry.

20.1k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill kortix-connectors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kortix-connectors
Source: https://github.com/kortix-ai/suna/tree/main/core/kortix-master/opencode/skills/KORTIX-system/connectors
Command: npx skills add https://github.com/kortix-ai/suna --skill kortix-connectors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kortix connectors require a reliable, centralized registry to track which services are connected, preventing drift between environments and ensuring all tools reference a single source of truth.

Core Features & Use Cases

  • SQLite-backed registry in .kortix/kortix.db provides a single source of truth for all connected services.
  • CLI operations support listing, fetching, creating, and removing connectors (connector_list, connector_get, connector_setup, connector_remove).
  • Handles OAuth, CLI, and API-key based integrations for Pipedream, CLI, and API workflows.

Quick Start

Register a new connector using the CLI and verify with the list command

Frequently Asked Questions about kortix-connectors

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

FAQPage Schema
How do I centralize API and OAuth connector management to prevent configuration drift?

Centralize connector management by registering service connections in an SQLite-backed local registry at .kortix/kortix.db, establishing a single source of truth that prevents drift across integrated tools.

What is the best way to register a new OAuth service connection via CLI?

Register a new OAuth service connection by executing the connector_setup CLI command to store credentials, then verifying the entry in the SQLite registry using the connector_list command.

Can I manage API-key and CLI based integrations within the same local registry?

Yes, you can manage API-key and CLI based integrations alongside OAuth in the same local SQLite registry, applying standard setup and removal flows to maintain consistent access across Pipedream, CLI, and API workflows.

How do I list and remove existing service connections from the local registry?

List and remove existing service connections by executing the connector_list CLI operation to fetch current entries, then applying the connector_remove command to delete specific connectors from the SQLite database.

Does the connector registry require external dependencies to maintain connections?

The connector registry requires no external dependencies to maintain connections, relying solely on an internal SQLite database at .kortix/kortix.db to track and manage service setups without additional package requirements.