add-provider-doc
The add-provider-doc Claude Code skill provides a structured workflow for documenting a new AI provider integration in LobeHub. Use it when adding support for a new provider to ensure consistent documentation across usage guides, environment variable references, Docker configurations, and image assets in both English and Chinese, while maintaining security by excluding real API credentials.
git clone --depth 1 https://github.com/lobehub/lobehub /tmp/add-provider-doc && cp -r /tmp/add-provider-doc/.agents/skills/add-provider-doc ~/.claude/skills/add-provider-docSKILL.md
# Adding New AI Provider Documentation
Complete workflow for adding documentation for a new AI provider.
## Overview
1. Create usage documentation (EN + CN)
2. Add environment variable documentation (EN + CN)
3. Update Docker configuration files
4. Update .env.example
5. Prepare image resources
## Step 1: Create Provider Usage Documentation
### Required Files
- `docs/usage/providers/{provider-name}.mdx` (English)
- `docs/usage/providers/{provider-name}.zh-CN.mdx` (Chinese)
### Key Requirements
- 5-6 screenshots showing the process
- Cover image for the provider
- Real registration and dashboard URLs
- Pricing information callout
- **Never include real API keys** - use placeholders
Reference: `docs/usage/providers/fal.mdx`
## Step 2: Update Environment Variables Documentation
### Files to Update
- `docs/self-hosting/environment-variables/model-provider.mdx` (EN)
- `docs/self-hosting/environment-variables/model-provider.zh-CN.mdx` (CN)
### Content Format
```markdown
### `{PROVIDER}_API_KEY`
- Type: Required
- Description: API key from {Provider Name}
- Example: `{api-key-format}`
### `{PROVIDER}_MODEL_LIST`
- Type: Optional
- Description: Control model list. Use `+` to add, `-` to hide
- Example: `-all,+model-1,+model-2=Display Name`
```
## Step 3: Update Docker Files
Update all Dockerfiles at the **end** of ENV section:
- `Dockerfile`
- `Dockerfile.database`
- `Dockerfile.pglite`
```dockerfile
# {New Provider}
{PROVIDER}_API_KEY="" {PROVIDER}_MODEL_LIST=""
```
## Step 4: Update .env.example
```bash
### {Provider Name} ###
# {PROVIDER}_API_KEY={prefix}-xxxxxxxx
```
## Step 5: Image Resources
- Cover image
- 3-4 API dashboard screenshots
- 2-3 LobeHub configuration screenshots
- Host on LobeHub CDN: `hub-apac-1.lobeobjects.space`
## Checklist
- [ ] EN + CN usage docs
- [ ] EN + CN env var docs
- [ ] All 3 Dockerfiles updated
- [ ] .env.example updated
- [ ] All images prepared
- [ ] No real API keys in docsAdd server-side environment variables that control default values for user settings.
Agent runtime lifecycle hooks. Use for before/after tool or step hooks, tool mocks, human intervention, sub-agent calls, context compression, evals, tracing, callAgent, or lifecycle events.
Build or extend LobeHub Agent Signal pipelines. Use for signal sources, signal/action types, policies, middleware, workflow handoff, dedupe, scope behavior, or observability.
Agent tracing CLI for execution snapshots. Use for agent-tracing, traces, snapshots, LLM call inspection, context engine data, agent step analysis, or execution debugging.
Build LobeHub builtin tool packages. Use when adding agent-callable tools, manifests, executors, runtimes, inspectors, renders, placeholders, streaming, interventions, portals, or tool registries.
Build multi-platform chat bots with the chat SDK. Use for Slack, Teams, Google Chat, Discord, GitHub, Linear bots, webhooks, mentions, slash commands, cards, modals, or streaming responses.
>
LobeHub CLI (@lobehub/cli) development guide — commands, subcommands, architecture.