add-provider

Add AI providers to ClaudeBar using a TDD workflow.

1.4k|127|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/tddworks/ClaudeBar --skill add-provider-tddworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-provider
Source: https://github.com/tddworks/ClaudeBar/tree/main/.claude/skills/add-provider
Command: npx skills add https://github.com/tddworks/ClaudeBar --skill add-provider-tddworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClaudeBar often requires extending its capabilities when new AI providers emerge. This Skill guides engineers on adding a provider using a test-driven development (TDD) workflow to ensure correct integration and testability.

Core Features & Use Cases

  • Guided provider integration: Step-by-step approach for parsing tests, probe development, and provider wiring.
  • TDD-first workflow: Encourages red/green/refactor cycles to validate probes and providers before production use.
  • Extensible architecture patterns: Demonstrates how to structure provider, probe, and settings with optional ISP sub-protocols for configuration.

Quick Start

Explain the steps to add a new provider to ClaudeBar following the TDD workflow.

Frequently Asked Questions about add-provider

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

FAQPage Schema
How do I add a new AI provider to ClaudeBar using TDD?

Adding a new AI provider to ClaudeBar using TDD involves a guided workflow of writing parsing tests, implementing a CLI-based UsageProbe, developing the Provider class, and registering the provider in infrastructure tests.

What components are required to integrate a new provider with a TDD workflow?

Integrating a new provider requires implementing a UsageProbe for CLI probing, a Provider class for wiring, tests within Tests/InfrastructureTests, and optional ISP sub-protocols for provider-specific configuration settings.

When should I use ISP sub-protocols for provider configuration?

You should use optional ISP sub-protocols for provider configuration when introducing a new AI provider that requires specific, isolated settings beyond the standard architecture patterns, ensuring correct integration and testability.

How does the TDD-driven workflow validate new providers before production?

The TDD-driven workflow validates new providers by enforcing red/green/refactor cycles, starting with parsing tests in Tests/InfrastructureTests to ensure the probe and provider implementation behave correctly before production use.

Can I add a provider to ClaudeBar without writing infrastructure tests?

Adding a provider without writing infrastructure tests breaks the TDD-first workflow, which relies on Tests/InfrastructureTests to validate the UsageProbe and Provider class implementation for correct, testable integration.