add-provider-doc

Standardize bilingual documentation and Docker deployment onboarding for a new AI provider.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill add-provider-doc-duwenji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-provider-doc
Source: https://github.com/duwenji/generative-ai-oss-tutorials/tree/main/sandbox/lobe-chat/.agents/skills/add-provider-doc
Command: npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill add-provider-doc-duwenji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding a new AI provider to a self-hosted chat/app often stalls on scattered requirements—usage docs, environment variables, Docker configuration, and image assets—creating inconsistent onboarding and deployment issues.

Core Features & Use Cases

  • Bilingual provider documentation: Create complete usage docs in English and Chinese, including real registration and dashboard URL references plus pricing callouts (without exposing secrets).
  • Environment-variable documentation: Define provider-specific API key and model list variables with clear types, descriptions, and example formats.
  • Deployment configuration updates: Update Dockerfiles (end of ENV section) and refresh .env.example so the new provider can be configured safely and consistently.
  • Image resource preparation: Produce and upload the required cover and screenshot set for provider listing and LobeHub configuration.

Quick Start

Ask your team to run the full provider documentation checklist for a chosen provider-name, ensuring EN+CN docs, environment variables docs, all three Dockerfiles, .env.example, and required images are updated without including any real API keys.

Frequently Asked Questions about add-provider-doc

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

FAQPage Schema
How do I add a new AI provider to a self-hosted LobeChat environment?

Adding a new AI provider requires standardizing end-to-end documentation for usage pages, environment variables, Docker configuration, and UI assets. This ensures consistent onboarding and deployment within your self-hosted LobeChat environment.

What environment variable configuration is needed for a new AI provider?

Environment variable configuration involves defining provider-specific API keys and model lists with clear types, descriptions, and example formats. You must also synchronize Docker ENV updates and refresh the .env.example file for safe deployment.

Does adding a provider require bilingual documentation?

Yes, adding a provider requires bilingual documentation in both English and Chinese. The docs must include real registration and dashboard URL references, along with pricing callouts, while ensuring no real API keys are exposed.

What's the best way to prepare image assets for a LobeHub provider listing?

The best way to prepare image assets is to produce and upload the required cover and screenshot set specifically for the provider listing. This packaging ensures the new AI provider meets the LobeHub UI configuration requirements.

Can I include real API keys in the provider documentation and .env.example?

No, you must avoid including any real API keys in the documentation, Dockerfiles, or .env.example files. The configuration should only provide example formats and clear descriptions to ensure safe and consistent deployment setup.

When do I need to update Dockerfiles for AI provider integration?

You need to update Dockerfiles for AI provider integration when adding new environment variables, specifically appending them at the end of the ENV section. This synchronizes the deployment configuration with the new provider's requirements.