add-provider-doc

Automate AI provider documentation workflows from usage guides to Docker configurations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations struggle to consistently document new AI providers across usage docs, environment variables, Docker configurations, and image assets.

Core Features & Use Cases

  • Create usage documentation for new providers (EN + CN)
  • Add environment variable and Docker configuration guidance
  • Prepare image resources and versioned templates for onboarding

Quick Start

Create documentation bundles for a new provider by combining usage, environment, Docker, and image assets into a ready-to-publish package.

Frequently Asked Questions about add-provider-doc

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

FAQPage Schema
How do I automate AI provider documentation workflows for Docker and environment variables?

Automating AI provider documentation workflows generates consistent usage guides, environment variable references, and Docker configurations. It combines structured content sections, reproducible templates, and image assets into a ready-to-publish package for onboarding new providers.

What is included in a standard AI provider documentation bundle for team onboarding?

A standard AI provider documentation bundle includes bilingual usage guides, environment variable setup instructions, and Docker configuration notes. It meets frontmatter metadata requirements and prepares versioned image resource templates to ensure reproducible onboarding for new providers.

How do I maintain consistency across AI provider docs, assets, and deployment notes?

Maintaining consistency across AI provider docs applies structured content sections and reproducible asset templates. By automating the end-to-end workflow from usage guides to Docker configurations, teams enforce uniform frontmatter metadata and deployment notes across all new providers.

Does this documentation workflow support bilingual content for new AI providers?

Yes, the documentation workflow supports bilingual content by generating usage documentation for new providers in both English and Chinese. It integrates environment variables, Docker configurations, and image assets while maintaining consistent frontmatter metadata across both languages.

Can I use these templates to prepare Docker configurations and image resources for provider onboarding?

Yes, you can use these templates to prepare Docker configurations, environment variable guidance, and image resources for provider onboarding. The workflow combines these assets with usage documentation into a structured, versioned package ready for immediate deployment and publishing.

What are the limitations of using automated templates for AI provider documentation?

Automated templates for AI provider documentation focus specifically on usage guides, environment variables, and Docker configurations. They may not cover highly custom deployment architectures outside standard Docker environments, limiting flexibility for providers requiring specialized infrastructure or non-standard image asset workflows.