provider-api
Universal hosted-provider API adapter guide. Use the skill-router provider-api CLI for compatible project/task/file/webhook/agent APIs, with explicit endpoint and key configuration instead of provider-specific defaults.
来源信息
- 仓库
- onfire7777/universal-ai-skills-library
- 最近来源活动
- 2026年6月18日 10:46
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 16
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- provider-api
- description
- Universal hosted-provider API adapter guide. Use the skill-router provider-api CLI for compatible project/task/file/webhook/agent APIs, with explicit endpoint and key configuration instead of provider-specific defaults.
# Provider API
Use this skill when a workflow needs to call a hosted project provider through the universal `skill-router provider-api` CLI. The adapter is intentionally neutral: it does not assume any provider endpoint, API key name, or hosted UI.
## CLI Contract
Set an endpoint and key explicitly before making API calls:
```bash
export SKILL_ROUTER_API_BASE="https://provider.example/v2"
export SKILL_ROUTER_API_KEY="..."
skill-router provider-api tasks list
```
You can also pass the endpoint per command:
```bash
skill-router provider-api --api-base "https://provider.example/v2" projects list
```
## Supported Surfaces
The CLI exposes common hosted-provider surfaces:
- `tasks` for task lifecycle calls
- `projects` for reusable project context
- `files` for provider-managed file references
- `webhooks` for callback configuration
- `agents` for provider-hosted agent records
- `connectors`, `skills`, `usage`, and `websites` when the provider supports them
## Provider-Specific Docs
For exact request schemas, authentication headers, rate limits, or provider-only behavior, load the explicit provider skill or documentation for that platform. Do not hard-code provider endpoints into universal setup, install, doctor, or router defaults.
在 GitHub 查看