analitiq-connector-builder

Plugin analitiq-connector-builder from marketplace analitiq-claude-code-plugins in analitiq-ai/claude-code-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (4)

• connector-builder

  Build a connector JSON document conforming to the published Analitiq connector schema. Trigger when the user asks to author, build, scaffold, or generate a connector for a named provider — either an API/SaaS provider or a database engine. Trigger phrases include "build a connector for X", "scaffold

• connector-spec-api

  API connector authoring vocabulary — auth flows, HTTP transports, pagination, replication, post-auth discovery. Loaded by api-connector-creator only. Not invoked directly by users.

• connector-spec-db

  Database connector authoring vocabulary — driver selection, DSN URL templates with bindings and encoding, TLS declarations, resource discovery, the read/write type map, the SQL write path (sql_capabilities + the dialect renderers), and the Python package files. Loaded by db-connector-creator only. N

• connector-spec-storage

  Stub for the connector kinds the plugin declines rather than authors (RULE-CTOR-037), so this skill is intentionally minimal. Loaded only by storage-connector-creator (also a stub) when the orchestrator dispatches such a kind.

Subagents (7)

• api-connector-creator

  Author an API connector JSON document (kind=api) plus the connector's type map from ProviderFacts and enum classifications. Loads the connector-spec-api skill. Knows nothing about DSN/TLS or database transports. Use when the connector-builder orchestrator has classified a provider as kind=api. Outpu

• connector-drift-classifier

  Classify the version bump between a draft connector document and its previously released version, per the connector release table in connector-builder/references/metadata-and-versioning.md §Release version (version). Use after the draft has passed validation and before final release. Inputs are prev

• connector-provider-researcher

  Research a third-party provider against the published contract schemas and return its facts. The schemas the orchestrator passes define what a connector must know; this agent grounds every fact they ask about in the provider's official documentation and authors nothing. Runs per invocation at the sc

• connector-schema-validator

  Validate one draft connector-builder document, or a whole connector package, by submitting it to the analitiq-validator MCP server. Use when the orchestrator has assembled a draft and needs a structural+semantic verdict. Output is the server's Diagnostics envelope, or a validation-not-run finding wh

• db-connector-creator

  Author a database connector package (kind=database) from ProviderFacts and enum classifications — the connector JSON document, the connector's type map, and the Python package files (`connector.py`, `__init__.py`, `requirements.txt`, `pyproject.toml`). Loads the connector-spec-db skill. Knows nothin

• endpoint-creator

  Author an endpoint JSON document for an API connector package, conforming to the published api-endpoint contract. Invoked by the connector-builder orchestrator only when the connector kind is api, once per resource inside the endpoint fan-out. Multiple endpoint creators run in parallel — each author

• storage-connector-creator

  Stub agent for connector kinds the engine does not execute. The contract accepts them, so the plugin declines with a structured refusal instead of authoring one (RULE-CTOR-037); the orchestrator routes such a kind here and surfaces the refusal.

MCP servers (1)

• analitiq-validator

  connects to: https://api.analitiq.ai/v1/mcp/validator/v1

Similar plugins