CtrlK
BlogDocsLog inGet started
Tessl Logo

add-provider

Guide for adding new AI providers to ClaudeBar using TDD patterns. Use this skill when: (1) Adding a new AI assistant provider (like Antigravity, Cursor, etc.) (2) Creating a usage probe for a CLI tool or local API (3) Following TDD to implement provider integration (4) User asks "how do I add a new provider" or "create a provider for X"

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable TDD guide with concrete templates, a clear phased workflow, verification checklist, and appropriately split reference files. It avoids concept padding and leans on real bundle references.

DimensionReasoningScore

Conciseness

The body is dense with actionable code templates and tables, with almost no prose explaining concepts Claude already knows; each section earns its place despite its length.

3 / 3

Actionability

Provides concrete, copy-paste-ready Swift templates with exact file paths and commands, plus a complete worked example in references; the {Provider} placeholders are justified by the template nature rather than being pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced five-phase TDD workflow (Red → Green per phase) with explicit verification via the closing checklist, including running the existing 300+ test suite.

3 / 3

Progressive Disclosure

The body is an organized overview that signals two real one-level-deep references (antigravity-example.md, provider-icon-guide.md), both verified to exist in the bundle, with easy navigation.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concisely states a concrete capability and gives explicit, natural-language triggers covering the main use cases. It uses third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "adding new AI providers to ClaudeBar using TDD patterns", "creating a usage probe for a CLI tool or local API", "implement provider integration" — matching the "Lists multiple specific concrete actions" anchor.

3 / 3

Completeness

Explicitly answers both what ("Guide for adding new AI providers to ClaudeBar using TDD patterns") and when (a four-item "Use this skill when" clause), satisfying the "both what AND when with explicit triggers" anchor.

3 / 3

Trigger Term Quality

Includes natural phrasings a user would actually say, with quoted triggers like "how do I add a new provider" and "create a provider for X", giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

The ClaudeBar provider/TDD niche is specific and the triggers ("add a new provider", "create a provider for X") are distinct, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
tddworks/ClaudeBar
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.