add-provider-doc

Create complete provider documentation packages with usage guides, environment variables, and Docker configuration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/razgulay/my-lobe-chat --skill add-provider-doc-razgulay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-provider-doc
Source: https://github.com/razgulay/my-lobe-chat/tree/main/.agents/skills/add-provider-doc
Command: npx skills add https://github.com/razgulay/my-lobe-chat --skill add-provider-doc-razgulay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through creating comprehensive AI provider documentation, covering usage docs, environment variables, Docker configuration, and image resources.

Core Features & Use Cases

  • Structured documentation workflow: Ensures EN/CN usage docs, env var docs, Docker configs, and image assets are consistently prepared.
  • Artifact readiness: Validates all required files and references before publishing to LobeHub CDN.
  • Use Case: When onboarding a new AI provider (e.g., OpenAI, Anthropic), this Skill provides a repeatable template and checklist to generate complete docs quickly.

Quick Start

Follow the provider docs workflow to add a new provider's documentation package, including usage docs, environment variable docs, Docker configs, example .env, and cover images.

Frequently Asked Questions about add-provider-doc

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

FAQPage Schema
How do I create complete AI provider documentation for a new model integration?

To create AI provider documentation, you need a structured workflow that generates usage guides, environment variable configs, Docker files, and image assets. This process enforces a consistent file layout and validates all required references before publishing.

What files are required for onboarding a new AI provider to LobeHub?

Onboarding a new AI provider requires EN and CN usage docs, environment variable documentation, Docker configuration files, example .env files, and cover image assets to produce a ready-to-publish documentation package.

How do I generate bilingual usage guides for AI providers?

Generating bilingual usage guides involves using a repeatable template that outputs both EN and CN documentation files. This ensures international users have access to standardized environment variable and usage instructions.

What is the best way to validate provider documentation before publishing to a CDN?

Validating provider documentation before publishing to a CDN requires checking a structured file layout for all required files and references. This artifact readiness step ensures no missing environment variables or image assets.

Can I use this documentation workflow for any AI provider integration?

Yes, you can use this workflow for any AI provider integration, such as OpenAI or Anthropic. It provides a repeatable checklist to quickly generate complete environment variables, Docker configs, and usage docs.

Why does my AI provider documentation package fail the publishing check?

Your provider documentation package fails publishing checks if it lacks required files like EN/CN usage docs, environment variable configs, Docker configurations, or image assets. The validation enforces a strict file layout before producing artifacts.