add-provider-doc

Create bilingual provider documentation with environment variables and Docker configurations.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Nick777-Pixel/mychat7 --skill add-provider-doc-nick777-pixel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-provider-doc
Source: https://github.com/Nick777-Pixel/mychat7/tree/main/.agents/skills/add-provider-doc
Command: npx skills add https://github.com/Nick777-Pixel/mychat7 --skill add-provider-doc-nick777-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable workflow to document new AI providers, covering usage docs, environment variables, Docker configurations, and image resources to ensure consistency and completeness.

Core Features & Use Cases

  • Usage Documentation: EN + CN provider usage docs.
  • Environment Variables & Docker: Env var documentation and Docker configuration updates.
  • Assets & Maintenance: Prepare image resources and update deployment assets (e.g., .env.example).

Quick Start

Create EN and CN usage docs, update environment variable docs, update Docker configurations, and prepare image resources for the new provider.

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 bilingual documentation for a new AI provider?

To create bilingual documentation for a new AI provider, use a structured workflow template that generates both English and Chinese usage docs, ensuring consistent output and easier future maintenance across languages.

What's the best way to document environment variables and Docker configurations for AI services?

Documenting environment variables and Docker configurations for AI services is best handled by enforcing a step-by-step process that updates deployment assets like .env.example alongside Docker integration notes for complete coverage.

How does a structured documentation workflow improve provider integration maintenance?

A structured documentation workflow improves provider integration maintenance by enforcing a repeatable template for usage docs, environment variables, and Docker notes, which keeps all technical assets consistent and easy to update.

Do I need to prepare image resources separately when adding new provider docs?

You do not need to prepare image resources separately, as the provider documentation workflow includes asset preparation steps to gather necessary images and update deployment assets simultaneously with the docs.

Can I use this documentation workflow to update existing .env.example files?

Yes, you can use this documentation workflow to update existing .env.example files, as the process explicitly covers environment variable documentation and updates to deployment assets for new AI providers.