finding-llm-gateway-migration-candidates

Finds and ranks callers ready to migrate from the Python LLM gateway to the Go gateway.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill finding-llm-gateway-migration-candidates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-llm-gateway-migration-candidates
Source: https://github.com/PostHog/posthog-foss/tree/main/.agents/skills/finding-llm-gateway-migration-candidates
Command: npx skills add https://github.com/PostHog/posthog-foss --skill finding-llm-gateway-migration-candidates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams migrating from PostHog's Python services/llm-gateway to the Go ai-gateway need to know which callers can move safely and in what order. This Skill audits production callers, checks each against the gateway parity record, and returns an evidence-backed shortlist without modifying any code.

Core Features & Use Cases

  • Caller Discovery: Searches code and deployment wiring for LLM_GATEWAY_URL, gateway client helpers, and product-slug URLs, then traces each hit to its real production entry point.
  • Contract Inventory: Records each candidate's credential source, billing owner, model and API shape, attribution, retry behavior, and deployment boundaries.
  • Readiness Classification: Labels each caller as Ready, Verify, Blocked, or In progress based on the parity record and Go implementation evidence.
  • Use Case: When asked "what should we migrate to the Go gateway next?", run this Skill to get a ranked table of candidates with required work and evidence gaps.

Quick Start

Ask the assistant to find and rank the next low-risk LLM gateway migration candidates across the PostHog repositories.

Frequently Asked Questions about finding-llm-gateway-migration-candidates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which callers still use the Python LLM gateway?

Search for LLM_GATEWAY_URL, LLM_GATEWAY_API_KEY, get_llm_client, and product-slug URLs across default branches, then trace each result to its production entry point. Exclude tests, dead code, and callers already configured for Go.

How do I decide which LLM gateway caller to migrate first?

Prioritize callers with no blocked contracts, a shared Go-capable builder or stock SDK, a Go-supported model and API shape, and a narrow deployment boundary. Lower the rank for broad shared-process switches or unverified billing changes.

Does a missing phs_ credential block a gateway migration?

No, a missing phs_ credential is deployment work, not a parity blocker. Once the paying team is known, create a project secret with llm_gateway:read scope and fund that team wallet during the migration.

Can a caller-supplied team_id control billing in the Go gateway?

No, the Go gateway debits the credential's team wallet regardless of caller-supplied team_id or ai_product properties. Those properties preserve reporting attribution but cannot select which wallet is charged.

What makes a caller blocked from migrating to the Go gateway?

A caller is blocked when migration would lose a required auth, policy, billing, provider, API shape, or attribution contract. Verify the missing contract against the parity record and current Go implementation before classifying.