원클릭으로 Manus에서 모든 스킬 실행

phaseo-gateway

스타6

포크3

업데이트2026년 7월 9일 16:12

Implement and migrate AI integrations to Phaseo Gateway via OpenAI-compatible REST, the official TypeScript SDK (@phaseo/sdk), Python SDK (phaseo), and Vercel AI SDK provider (@phaseo/ai-sdk-provider). Use when wiring new API calls, replacing OpenAI/Anthropic/OpenRouter/Vercel Gateway base URLs, adding app attribution headers, selecting model IDs, or troubleshooting auth/routing/response-shape issues.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

phaseoteam

phaseoteam/Phaseo

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Phaseo Gateway

Use this skill to make high-confidence Phaseo integration changes with minimal diff size.

Workflow

Identify integration surface before editing:

OpenAI-compatible REST calls
OpenAI SDK / Anthropic SDK pointed at Phaseo
Official Phaseo SDK (TS/Python)
Vercel AI SDK provider (@phaseo/ai-sdk-provider)

Select the minimal migration path:

Keep existing SDK and only swap baseURL + API key when possible.
Move to official Phaseo SDK only when explicit capability gaps or ergonomics need it.

Apply standard Phaseo request contract:

Base URL: https://api.phaseo.app
Auth header: Authorization: Bearer <PHASEO_API_KEY>
Optional attribution headers: x-title and http-referer
Discover model IDs from GET /v1/models rather than hard-coding stale IDs

Validate quickly:

GET /v1/health for gateway reachability
GET /v1/models for model availability/capabilities
One smoke generation request on the target endpoint

Harden before finishing:

Move keys into env vars if found inline.
Keep API keys out of commits, logs, screenshots, and client-side bundles.
Add retries/backoff for 429 and 5xx responses.

Integration Playbooks

OpenAI-compatible REST: read references/rest.md
TypeScript SDK: read references/sdk-typescript.md
Python SDK: read references/sdk-python.md
Migration patterns (OpenAI, Anthropic, OpenRouter, Vercel AI Gateway): read references/migrations.md

Execution Rules

Prefer minimal and reversible changes.
Preserve response shapes expected by callers unless explicitly requested to refactor.
If model IDs differ between platforms, map through /v1/models and keep compatibility aliases where needed.
If the user asks for best-effort migration, prioritize working endpoint and auth first, then feature parity.

이 저장소의 다른 Skills

같은 저장소

phaseo

phaseoteam/Phaseo

Use Phaseo when you need one API for multiple AI providers, stable model discovery, routing controls, pricing visibility, async jobs, or agent-ready gateway workflows.

2026-07-266

phaseo-cli

phaseoteam/Phaseo

Operate and troubleshoot Phaseo through the official `phaseo` CLI. Use when installing or updating the CLI, authenticating with browser or device OAuth, managing API keys/workspaces/presets/guardrails, inspecting credits and analytics, investigating gateway requests by request ID, or automating Phaseo control-plane work with structured JSON output.

2026-07-146

openrouter-to-phaseo-migration

phaseoteam/Phaseo

End-to-end migration guide for moving an existing OpenRouter integration to Phaseo Gateway. Use when repositories contain openrouter.ai endpoints, sk-or-v1 keys, OPENROUTER_API_KEY env vars, provider-prefixed model IDs, or OpenRouter-specific headers and the user wants a full migration with implementation, validation, and safe rollout.

2026-07-096

phaseo-agent-sdk-typescript

phaseoteam/Phaseo

Build agentic applications with the TypeScript Agent SDK (`@phaseo/agent-sdk`) on top of Phaseo Gateway. Use when repositories need local tool loops, resumable runs from app-owned state, or a gateway-backed agent client through `@phaseo/sdk`.

2026-07-096

phaseo-async-webhooks

phaseoteam/Phaseo

Build Phaseo async video, batch, and webhook integrations correctly. Use when repositories need long-running job creation, polling, websocket lifecycle helpers, standardized webhook payload handling, or operational recovery for async media and batch workflows.

2026-07-096

phaseo-changelog

phaseoteam/Phaseo

Write and maintain Phaseo changelog pages in the required house style. Use when updating `apps/docs/v1/changelog.mdx`, `product-changelog.mdx`, `sdk-changelog.mdx`, or `data-changelog.mdx`, especially when entries need to be rebuilt from merged pull requests, release metadata, and model-release records.

2026-07-096

name

phaseo-gateway

description

Phaseo Gateway

Use this skill to make high-confidence Phaseo integration changes with minimal diff size.

Workflow

Identify integration surface before editing:

OpenAI-compatible REST calls
OpenAI SDK / Anthropic SDK pointed at Phaseo
Official Phaseo SDK (TS/Python)
Vercel AI SDK provider (@phaseo/ai-sdk-provider)

Select the minimal migration path:

Keep existing SDK and only swap baseURL + API key when possible.
Move to official Phaseo SDK only when explicit capability gaps or ergonomics need it.

Apply standard Phaseo request contract:

Base URL: https://api.phaseo.app
Auth header: Authorization: Bearer <PHASEO_API_KEY>
Optional attribution headers: x-title and http-referer
Discover model IDs from GET /v1/models rather than hard-coding stale IDs

Validate quickly:

GET /v1/health for gateway reachability
GET /v1/models for model availability/capabilities
One smoke generation request on the target endpoint

Harden before finishing:

Move keys into env vars if found inline.
Keep API keys out of commits, logs, screenshots, and client-side bundles.
Add retries/backoff for 429 and 5xx responses.

Integration Playbooks

OpenAI-compatible REST: read references/rest.md
TypeScript SDK: read references/sdk-typescript.md
Python SDK: read references/sdk-python.md
Migration patterns (OpenAI, Anthropic, OpenRouter, Vercel AI Gateway): read references/migrations.md

Execution Rules

Prefer minimal and reversible changes.
Preserve response shapes expected by callers unless explicitly requested to refactor.
If model IDs differ between platforms, map through /v1/models and keep compatibility aliases where needed.
If the user asks for best-effort migration, prioritize working endpoint and auth first, then feature parity.