add-provider-doc

Standardize provider documentation with a 5-step workflow for usage, env vars, Docker, and images.

Updated Feb 1, 2026

Search Tags:#templates #documentation #onboarding #docker #environment-variables #provider #usage-docs

Ready to run

npx skills add https://github.com/Chenm4/VoiceChatAssistant --skill add-provider-doc-chenm4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-provider-doc
Source: https://github.com/Chenm4/VoiceChatAssistant/tree/main/lobehub-main/.agents/skills/add-provider-doc
Command: npx skills add https://github.com/Chenm4/VoiceChatAssistant --skill add-provider-doc-chenm4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the provider documentation workflow by guiding teams to create comprehensive usage docs, environment variable details, Docker configurations, and image resources for new AI providers.

Core Features & Use Cases

Structured templates for EN and CN usage docs, env var specs, and deployment notes.
Step-by-step workflow covering usage docs, environment variables, Docker files, .env updates, and image resources.
Use Case: When adding a provider like OpenAI or Anthropic, this skill ensures all required docs and configurations are consistently created.

Quick Start

Use the add-provider-doc skill to begin documenting a new provider by following the 5-step workflow in SKILL.md.

Frequently Asked Questions about add-provider-doc

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

FAQPage Schema

How do I standardize AI provider onboarding documentation across multiple teams?▼

Standardize provider documentation onboarding by applying a reproducible 5-step workflow that enforces consistent file templates for usage docs, environment variables, and Docker configurations. This ensures all teams follow the same structural standards when adding new AI providers.

What steps are required to create usage docs and environment variable specs for a new AI provider?▼

Creating usage docs and environment variable specs follows a 5-step workflow covering EN and CN usage sections, environment variable details, Docker file updates, .env modifications, and image resource generation. Each step enforces frontmatter presence and consistent templates.

Does this documentation workflow support both English and Chinese usage sections?▼

Yes, the documentation workflow supports both English and Chinese usage sections by providing structured templates for each language. This ensures comprehensive bilingual provider documentation is consistently generated across all onboarding tasks.

Can I use these templates to manage Docker configurations and .env updates for new providers?▼

Yes, these templates specifically guide Docker configuration updates and .env file modifications as part of the provider onboarding process. The workflow standardizes these deployment files alongside usage documentation to ensure reproducible provider setups.

What is the best way to ensure frontmatter is present in all provider documentation files?▼

The best way to ensure frontmatter presence is using a standardized workflow that automatically enforces frontmatter requirements across all generated documentation files. This validation happens during the template-driven creation of usage docs, environment variable specs, and Docker configurations.

When do I need to use a standardized provider documentation workflow?▼

You need a standardized provider documentation workflow when your team manages multiple AI providers and requires consistent usage docs, environment variable specs, and Docker configurations. This becomes essential when onboarding providers like OpenAI or Anthropic to maintain documentation quality and reproducibility.