llm-connect/registry/capabilities/capability.agents.llm-connector.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.agents.llm-connector	Pluggable LLM Adapter Library (llm-connect)	Provider-neutral Python/CLI LLM adapter library supporting OpenRouter, Gemini, OpenAI, and the Claude Code CLI out of the box, with a clean abstract interface for adding new providers.	llm-connect	draft	agents	llm adapter provider-neutral	discovery availability current target confidence rationale D3 D5 medium README documents a working quick-start (`create_adapter`, `RunConfig`, `execute_prompt`), the supported provider list, and both local-editable and future-published install paths. current target confidence rationale A2 A3 medium Installable today via `pip install -e` (local) with a documented future `pip install llm-connect` path once published; consumed today by sibling repos including `cya` (can-you-assist) and referenced as the intended backend for reuse-surface's own `establish --discover`.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations four providers implemented (OpenRouter, Gemini, OpenAI, Claude Code CLI) abstract adapter interface for adding new providers already a named integration point for other repos (can-you-assist's LLMAdapter seam, reuse-surface's establish --discover) level confidence basis known_reliability_risks R1 low consumer_quality_signals no llm-connect instance was running on this workstation during the REUSE-WP-0017 sweep, so establish --discover fell back to manual authoring for this campaign	intent includes excludes assumptions use_cases research_memos Give Python and CLI consumers a single, provider-neutral way to call LLMs, decoupling agent/tool code from any one vendor's SDK. provider-neutral adapter interface OpenRouter, Gemini, OpenAI, Claude Code CLI adapters RunConfig-based execution hosting or credential custody for providers (routes to OpenBao/operator paths per credential-routing conventions)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 Python package (`llm_connect`) library import cli	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md tests/	recommended_for not_recommended_for known_limitations any repo needing provider-neutral LLM calls instead of a vendor-specific SDK needs requiring a provider not yet adapted (extend via the abstract interface first) not yet published to a package index; local editable install only

Pluggable LLM Adapter Library (llm-connect)

Overview

llm-connect provides pluggable, provider-neutral LLM adapters for Python and the command line, supporting OpenRouter, Gemini, OpenAI, and the Claude Code CLI out of the box behind a clean abstract interface, and is already the intended backend for several sibling repos including can-you-assist and reuse-surface's own drafting tooling.

Assessment notes

Discovery

README documents a working quick-start (create_adapter, RunConfig, execute_prompt), the supported provider list, and both local-editable and future-published install paths.

Availability

Installable today via pip install -e (local) with a documented future pip install llm-connect path once published; consumed today by sibling repos including cya (can-you-assist) and referenced as the intended backend for reuse-surface's own establish --discover.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml