add-provider-doc

You can automate AI provider documentation by generating usage guides, environment-variable references, and Docker configurations in a structured workflow. This process enforces frontmatter metadata and validates compliance, consolidating assets into a repeatable onboarding system for new services.

Maintaining environment variable references and Docker configurations requires a structured documentation workflow that captures metadata for safety checks. This ensures no real API keys are included and organizes configurations alongside required images, scripts, and references for consistent quality.

Documenting new AI providers across English and Chinese requires a coordinated workflow that generates bilingual usage docs, environment-variable references, and Docker configurations. This ensures consistent asset preparation and documentation quality across both languages.

Yes, the provider documentation workflow supports optional directories including scripts, references, and assets. This structure allows teams to organize sample configurations and required images while maintaining structured frontmatter with name and description for metadata discovery.

Preventing real API keys in AI provider documentation requires compliance checks that validate project conventions. This skill enforces safety checks during the documentation workflow to ensure no actual API keys are committed alongside environment-variable references and Docker configurations.

Before onboarding documentation for a new AI provider, you need structured frontmatter with name and description, plus optional directories for scripts, references, and assets. This establishes the metadata foundation for discovery and prepares configurations for environment variables and Docker.