Loading...
Loading...
Found 1,211 Skills
Answer ZenMux questions by reading the latest official docs. Use for product features, APIs, integration, pricing, models/providers, routing, fallback, streaming, multimodal, structured output, tool calling, reasoning, prompt caching, image/video generation, web search, long context, observability, logs, cost tracking, subscriptions, PAYG, invoices, FAQ, privacy, terms, compliance, and tool guides for Claude Code, Cursor, Cline, Codex, Gemini CLI, opencode, Cherry Studio, Obsidian, Sider, Open-WebUI, Dify, and GitHub Copilot. Trigger on "ZenMux docs", "ZenMux API", "how to use ZenMux", "models", "pricing", "ZenMux 怎么用", "文档", "快速开始", "API 参考", "模型路由", "供应商路由", "订阅", "按量计费", "接入", "配置". Also use when ZenMux is the project context and the user asks about LLM API aggregation, model routing, or provider fallback.
Inspect LLM torch profiler traces at forward-pass, layer, and kernel level. Use when you need layer timings, anchor-kernel boundaries, representative kernel flows, or Perfetto time ranges.
Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.
Build structured hierarchical memory systems for LLM agents using GAM (General Agentic Memory) with support for text, video, and agent trajectories
Router skill for LLMQuant risk workflows. Use when the user needs fear scoring, VIX regime, hedge design, or research health checks.
Router skill for LLMQuant prediction-market workflows. Use when the user needs event odds, settlement criteria, probability gaps, cross-market pricing, or prediction-market arbitrage review.
Deploys and optimizes AI/ML inference workloads on GKE, using GPUs, TPUs, and model servers. Use when deploying GKE inference servers, configuring GKE GPU resources for inference, or deploying LLMs on GKE. Don't use for generic batch jobs or HPC task queues (use gke-batch-hpc instead).
This skill should be used when the user asks to "optimize prompts", "design prompt templates", "evaluate LLM outputs", "build agentic systems", "implement RAG", "create few-shot examples", "analyze token usage", or "design AI workflows". Use for prompt engineering patterns, LLM evaluation frameworks, agent architectures, and structured output design.
Production-grade fault tolerance for distributed systems. Use when implementing circuit breakers, retry with exponential backoff, bulkhead isolation patterns, or building resilience into LLM API integrations.
Consult an advisory council of three AI personas — Cato (skeptic), Ada (optimist), Marcus (pragmatist) — backed by different frontier LLM agents (Gemini, Claude, Codex). Each persona runs as a separate agent process with full repo context and returns independent feedback. Use when the user says "/council", asks for a second opinion, wants feedback on code changes, needs a premortem, wants to pressure-test a decision, or asks "what do you think about this approach?" Claude may also proactively suggest consulting the council before major architectural decisions, risky deploys, or ambiguous trade-offs (but should ask for user approval first).
Integrate Databuddy analytics into applications using the SDK or REST API. Use when implementing analytics tracking, feature flags, custom events, Web Vitals, error tracking, LLM observability, or querying analytics data programmatically.
Epistemic verification framework for AI-generated assertions. Requires evidence before acting on LLM claims about code behavior, system state, API responses, or factual statements. Use when an AI agent makes claims that will drive decisions, before acting on research results, or when an agent asserts something is true without showing evidence.