add-provider-doc

Automate adding AI provider documentation with usage, environment variables, and Docker configs.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mabdulrauf/wazone-back --skill add-provider-doc-mabdulrauf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-provider-doc
Source: https://github.com/mabdulrauf/wazone-back/tree/main/.agents/skills/add-provider-doc
Command: npx skills add https://github.com/mabdulrauf/wazone-back --skill add-provider-doc-mabdulrauf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable workflow for documenting new AI providers, including usage docs, environment-variable guidance, Docker configurations, and image assets, ensuring consistent, shareable provider documentation.

Core Features & Use Cases

  • Create EN + CN usage documentation for a provider.
  • Add environment-variable documentation and Docker config updates.
  • Prepare image resources and update .env.example for deployment.
  • Reuse and reference existing provider templates (e.g., fal.mdx) to maintain consistency across providers.

Quick Start

Follow the outlined steps to add a new AI provider's documentation, including usage docs, environment variables, Docker configurations, and image resources.

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 for Docker and environment variables?

Automating AI provider documentation streamlines adding usage docs, environment variables, and Docker configs. This skill handles the end-to-end workflow, preparing image resources and updating .env.example files for deployment.

What is the best way to create bilingual EN and CN usage docs for a new AI provider?

Creating bilingual EN and CN usage docs is automated by defining provider guidelines within a properly formatted SKILL.md frontmatter. The skill generates both language versions while referencing existing templates like fal.mdx for consistency.

Do I need a specific format to add new provider docs using this workflow?

Adding provider docs requires a properly formatted SKILL.md frontmatter containing the provider name and description. This structured input acts as the starting point for generating environment-variable guidance and Docker configurations.

How does referencing existing provider templates improve documentation workflows?

Referencing existing provider templates like fal.mdx improves documentation workflows by maintaining structural consistency across different AI providers. This ensures standardized environment-variable documentation and Docker configurations are generated reliably.

Can I update .env.example and prepare image assets for provider deployment automatically?

Updating .env.example and preparing image assets for deployment is fully automated by the skill. It integrates these steps into a repeatable workflow, ensuring all necessary environment variables and visual resources are ready for sharing.

Are there limitations when reusing templates to add environment-variable documentation?

Limitations exist if the initial SKILL.md frontmatter lacks the required name and description fields. Without this properly formatted input, the automated workflow cannot accurately generate the corresponding environment-variable guidance and Docker configurations.