Menu
Add documentation for a new AI provider — usage docs, env vars, Docker config, image resources.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | add-provider-doc |
| description | Add documentation for a new AI provider — usage docs, env vars, Docker config, image resources. |
| disable-model-invocation | true |
| argument-hint | [provider-name] |
Complete workflow for adding documentation for a new AI provider.
docs/usage/providers/{provider-name}.mdx (English)docs/usage/providers/{provider-name}.zh-CN.mdx (Chinese)Reference: docs/usage/providers/fal.mdx
docs/self-hosting/environment-variables/model-provider.mdx (EN)docs/self-hosting/environment-variables/model-provider.zh-CN.mdx (CN)### `{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`
Update all Dockerfiles at the end of ENV section:
DockerfileDockerfile.databaseDockerfile.pglite# {New Provider}
{PROVIDER}_API_KEY="" {PROVIDER}_MODEL_LIST=""
### {Provider Name} ###
# {PROVIDER}_API_KEY={prefix}-xxxxxxxx
hub-apac-1.lobeobjects.spaceBot-channel end-to-end verification for LobeHub — drives the real native chat apps (Discord / Slack / Telegram / WeChat / Lark / QQ / iMessage) via osascript or the iMessage bridge, on macOS. Extends the generic agent-testing skill for bot surfaces. Triggers on 'test bot', 'bot test', 'test in discord', 'test in telegram', 'test in slack', 'test in wechat', 'test in weixin', 'test in lark', 'test in feishu', 'test in qq'.
Agentic end-to-end testing for any project: backend verification via the project CLI, frontend verification via agent-browser (web), and desktop verification via CDP (Electron). Drives the real surface, captures visually confirmed evidence, and publishes a structured report to the LobeHub verify platform. Triggers on 'cli test', 'test with cli', 'verify with cli', 'backend test with cli', 'local test', 'test in electron', 'test desktop', 'manual test', 'test report', or any local end-to-end verification task.
Audit a page / surface against the Designing Interfaces pattern language + the ux skill checklists, then land findings. Three layers — static (code), visual (screenshots), dynamic (automated user journey + perf). Use to run a repeatable, standards-based UX review of one screen.
LobeHub Drizzle ORM schema and query style. Use for pgTable schemas, indexes, joins, inferred types, db.select/db.query, schema fields, foreign keys, junction tables, or postgres query patterns.
Turn a vague product ask ("this page feels wrong", "we need a team view") into a grounded, shippable design by establishing business semantics and the user task before proposing a surface. Use when scoping a new surface, redesigning an existing one, or deciding what a feature should be. Not for auditing a built screen (ux-audit) or choosing visual details (ux).
Add server-side environment variables that control default values for user settings.