yeet — ai-gateway AI-Stats, community, ai-gateway, ide skills, database, python, typescript

v1.0.0

이 스킬 정보

Open-source, OpenAI-compatible AI gateway with health-aware routing, failover, and live telemetry (cost, latency, errors). Built for production.

# Core Topics

AI-Stats AI-Stats
[4]
[3]
Updated: 4/7/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 1/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Review Score
1/11
Quality Score
23
Canonical Locale
en
Detected Body Locale
en

Open-source, OpenAI-compatible AI gateway with health-aware routing, failover, and live telemetry (cost, latency, errors). Built for production.

이 스킬을 사용하는 이유

Open-source, OpenAI-compatible AI gateway with health-aware routing, failover, and live telemetry (cost, latency, errors). Built for production.

최적의 용도

Suitable for operator workflows that need explicit guardrails before installation and execution.

실행 가능한 사용 사례 for yeet

! 보안 및 제한 사항

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The page lacks a strong recommendation layer.
  • - The page lacks concrete use-case guidance.
  • - The page lacks explicit limitations or caution signals.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is yeet?

Open-source, OpenAI-compatible AI gateway with health-aware routing, failover, and live telemetry (cost, latency, errors). Built for production.

How do I install yeet?

Run the command: npx killer-skills add AI-Stats/AI-Stats/yeet. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

Which IDEs are compatible with yeet?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add AI-Stats/AI-Stats/yeet. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use yeet immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

yeet

Install yeet, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Prerequisites

  • Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
  • Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

  • Branch: {description} on a fresh branch from origin/main (or repo default branch), unless the user explicitly says to keep using the current branch.
  • Commit: Prefer Conventional Commits (type(scope): summary) when possible.
    • Examples: fix(data): restore venice provider model export, chore(data): refresh generated provider model mappings
    • If scope is unclear, use type: summary (e.g. chore: refresh provider model data)
  • PR title: {description} summarizing the full diff.

Branch safety checks

  • Detect default branch: git remote show origin (or fallback main).
  • Detect current branch and open PR state:
    • current=$(git branch --show-current)
    • gh pr list --head "$current" --state open --json number
  • If current is not the default branch and there is no open PR for it, do not continue on that branch by default.
  • In that case, create a fresh branch from default, then continue:
    • git fetch origin
    • git checkout -b "{description}" origin/{default}
  • Never reuse a stale branch tied to closed/merged work unless the user explicitly asks to.

Workflow

  • Start on a fresh branch from the default branch unless the user explicitly requests the current branch.
  • Confirm status, then stage everything: git status -sb then git add -A.
  • Commit using a Conventional Commit message when possible; if not possible, use a terse descriptive message:
    • Preferred: git commit -m "fix(scope): short summary"
    • Fallback: git commit -m "{description}"
  • Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
  • Push with tracking: git push -u origin $(git branch --show-current)
  • If git push fails due to auth errors, fix authentication/credentials first, then retry the push.
  • Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
  • Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
  • PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

관련 스킬

Looking for an alternative to yeet or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자