ericrisco/rsc-harness / skills/llm-pipeline
llm-pipeline
UnverifiedUse when wiring several LLM calls into a production flow: typed contracts between steps, a router/gateway so 429s, timeouts and outages fail over instead of taking you down, and cost control via caching, model tiers and abort caps. NOT single-prompt wording (that is `prompt-engineering`), NOT a model-driven tool loop (that is `building-agents`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.8 KB |
| evals/README.md | markdown | 881 B |
| evals/cases.yaml | config | 3.4 KB |
| references/caching-layers.md | markdown | 3.0 KB |
| references/litellm-router.md | markdown | 3.9 KB |
| scripts/verify.shexecutable | script | 6.5 KB |
evals/cases.yaml
View on GitHubskill: llm-pipeline
should_trigger:
- prompt: "Chain three LLM calls: extract entities, then summarize, then classify — and make it not fall over."
why: "Canonical multi-step orchestration with data flowing between steps plus a reliability requirement — the core of this skill."
- prompt: "We keep getting random 429s and timeouts from OpenAI and it takes our feature down. Add fallbacks."
why: "Reliability layer: router fallback, retries, circuit-breaking around provider failures."
- prompt: "Put a gateway in front of OpenAI and Claude so we can swap models and load-balance."
why: "LLM gateway/router (LiteLLM) is the central tool of the skill."
- prompt: "Our LLM bill tripled — we call the model fresh on every request even for repeats."
why: "Non-obvious: framed as a cost problem, but the real fix is caching + tier routing, which are this skill's controls (not pure accounting)."
- prompt: "Necessito encadenar crides a l'LLM amb fallback i cachejar les respostes."
why: "Catalan phrasing for chaining + fallback + caching — exactly this skill, in another language."
- prompt: "Route easy requests to Haiku and only escalate to Opus when confidence is low."
why: "Model-tier routing, cheap-first with escalation, is the standard cost lever here."
should_not_trigger:
- prompt: "Help me write a better system prompt and few-shot examples for this classification task."
route_to: prompt-engineering
why: "This is prompt wording, not the orchestration around prompts."
- prompt: "Make this single call return JSON matching my Pydantic schema."
route_to: structured-extraction
why: "One schema-bound call, not a chain — this skill uses structured output as a contract but does not own single extraction."
- prompt: "Chunk my docs, embed them, and retrieve relevant context for the prompt."
route_to: rag
why: "Building a retriever is retrieval, not call-chaining; a pipeline may call a retriever as a step but does not build it."
- prompt: "Build an agent that decides which tools to call to book travel."
route_to: building-agents
why: "An autonomous decision loop where the model picks its next step — not a fixed DAG you designed."
- prompt: "Build me a dashboard attributing our monthly AI spend per team."
route_to: cost-tracking
why: "Spend ledger and reporting, not the pipeline controls (tiers, caching, abort caps) this skill owns."
capability:
- scenario: "Design a production pipeline that classifies an inbound support ticket, then drafts a reply, behind a router with fallback, with caching and a per-request cost cap."
must_include:
- "Typed/structured-output contract between the classify step and the draft step (validated at the seam)"
- "Explicit timeout on every LLM call (30-60s)"
- "Bounded retries with exponential backoff + jitter, never an unbounded loop"
- "Router with a fallback model, and mention of content_policy / context_window fallback buckets"
- "Prefix cache enabled (stable prefix first); semantic cache only if safe with a strong embedder + tuned threshold"
- "Model-tier routing cheap-first (e.g. Haiku then escalate), and a per-request budget cap that ABORTS"
- "Per-step observability fields: model, tokens, cost, latency_ms, cache_hit, fallback_used, retry_count"
- "Note that schema-valid does not mean correct; defer quality measurement to agent-eval"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |