How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

c4-component - Skill - OpenSmartRoute

Name: c4-component
Author: sickn33

Imported from sickn33/agentic-awesome-skills (skills/c4-component/SKILL.md). Install upstream with npx skills add sickn33/agentic-awesome-skills --skill c4-component. Copyright stays with the author.

C4 Component Level: [Component Name]

Use this skill when

Working on c4 component level: [component name] tasks or workflows
Needing guidance, best practices, or checklists for c4 component level: [component name]

Do not use this skill when

The task is unrelated to c4 component level: [component name]
You need a different domain or tool outside this scope

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.

Overview

Name: [Component name]
Description: [Short description of component purpose]
Type: [Component type: Application, Service, Library, etc.]
Technology: [Primary technologies used]

Purpose

[Detailed description of what this component does and what problems it solves]

Software Features

Code Elements

This component contains the following code-level elements:

c4-code-file-1.md - [Description]
c4-code-file-2.md - [Description]

Interfaces

[Interface Name]

Protocol: [REST/GraphQL/gRPC/Events/etc.]
Description: [What this interface provides]
Operations:
- operationName(params): ReturnType - [Description]

Dependencies

Components Used

[Component Name]: [How it's used]

External Systems

[External System]: [How it's used]

Component Diagram

Use proper Mermaid C4Component syntax. Component diagrams show components within a single container:

C4Component
    title Component Diagram for [Container Name]

    Container_Boundary(container, "Container Name") {
        Component(component1, "Component 1", "Type", "Description")
        Component(component2, "Component 2", "Type", "Description")
        ComponentDb(component3, "Component 3", "Database", "Description")
    }
    Container_Ext(externalContainer, "External Container", "Description")
    System_Ext(externalSystem, "External System", "Description")

    Rel(component1, component2, "Uses")
    Rel(component2, component3, "Reads from and writes to")
    Rel(component1, externalContainer, "Uses", "API")
    Rel(component2, externalSystem, "Uses", "API")


**Key Principles** (from [c4model.com](https://c4model.com/diagrams/component)):

- Show components **within a single container** (zoom into one container)
- Focus on **logical components** and their responsibilities
- Show **component interfaces** (what they expose)
- Show how components **interact** with each other
- Include **external dependencies** (other containers, external systems)

Master Component Index Template

# C4 Component Level: System Overview

## System Components

### [Component 1]
- **Name**: [Component name]
- **Description**: [Short description]
- **Documentation**: c4-component-name-1.md

### [Component 2]
- **Name**: [Component name]
- **Description**: [Short description]
- **Documentation**: c4-component-name-2.md

## Component Relationships
[Mermaid diagram showing all components and their relationships]

Example Interactions

"Synthesize all c4-code-*.md files into logical components"
"Define component boundaries for the authentication and authorization code"
"Create component-level documentation for the API layer"
"Identify component interfaces and create component diagrams"
"Group database access code into components and document their relationships"

Key Distinctions

vs C4-Code agent: Synthesizes multiple code files into components; Code agent documents individual code elements
vs C4-Container agent: Focuses on logical grouping; Container agent maps components to deployment units
vs C4-Context agent: Provides component-level detail; Context agent creates high-level system diagrams

Output Examples

When synthesizing components, provide:

Clear component boundaries with rationale
Descriptive component names and purposes
Comprehensive feature lists for each component
Complete interface documentation with protocols and operations
Links to all contained c4-code-*.md files
Mermaid component diagrams showing relationships
Master component index with all components
Consistent documentation format across all components

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Install c4-component and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "sickn33-agentic-awesome-skills-c4-component", "kind": "skill", "name": "c4-component", "description": "Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships.", "publisher": "sickn33", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/sickn33/agentic-awesome-skills", "path": "skills/c4-component/SKILL.md", "ref": "HEAD", "url": "https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/c4-component/SKILL.md", "key": "sickn33/agentic-awesome-skills/skills/c4-component/SKILL.md" } }, "instructions": "# C4 Component Level: [Component Name]\n\n## Use this skill when\n\n- Working on c4 component level: [component name] tasks or workflows\n- Needing guidance, best practices, or checklists for c4 component level: [component name]\n\n## Do not use this skill when\n\n- The task is unrelated to c4 component level: [component name]\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n\n## Overview\n\n- **Name**: [Component name]\n- **Descrip", "cost": { "context_tokens": 1165 } }

c4-component

About