Exported functions in state/lib/openrouter.ts. .md file to compare - side-by-side diff against openrouter
openrouter
description: "Triggers on prompt mention of 'openrouter'."
What it does for you
Lets your assistant pick the best AI model for each task.
What it produces
A recent result, so you can see the kind of work it returns.
loading…
How to get it
These run inside the Snappy workspace. Want this working in your business? I set skills like this up with you, in one focused week.
For developers how this skill is built, graded, and how it runs
at a glance- the short version
what's inside - the parts that make up a skill 3/4 present
A skill is just a few plain-text files. Only the main one is required. The rest are optional, added as the work needs them. This is what the skill is made of; how it runs is just below.
state/skills/openrouter/SKILL.md
present
state/lib/openrouter.ts
present
state/bin/openrouter/
not present
state/skills/openrouter/AGENTS.md
present
how it's graded - what counts as a good run 4 criteria · 2 deterministic · 2 judge
Each row is one thing a good run has to get right. deterministic means a quick check decides, pass or fail. judge means the AI reads the result and rates it. Grading each piece on its own (instead of one overall score) shows exactly where a run fell short, so the fix is obvious.
how it runs - the shared frame every skill uses 5/5 present
Every skill runs the same way. One part does the work, a separate part checks it, and a short loader hands the AI exactly what it needs for the job. Anything this skill doesn't use shows a one-line note saying why, on purpose, not by accident.
state/log/pending-eval.ndjson - NEVER hardcode an API key — use env("OPENROUTER_API_KEY") from state/lib/env.ts or env("KEY") throws
- Prefer state/lib/dispatch.ts for cheap-labor grunt work — dispatch.ts is the canonical PID-loop dispatch path and logs to state/log/dispatches.ndjson for cost/latency audit. Reach for openrouter directly only when you specifically need the multi-vendor fallback chain.
- Every dispatch logs one ndjson line — do not bypass the audit log
what it has learned - fixes written back in over time sample
When a run hits something this skill didn't handle, the fix gets written back into the skill so it doesn't happen again. FIXED means it was corrected on the spot. LOGGED means it's queued for a bigger rewrite. Either way, the skill gets a little better and never makes the same mistake twice.
- Loading feedback rows…
how the work flows- who makes it, who checks it
import from `state/lib/openrouter.ts` — `chat()`, `chatWithFallback()
SKILL.md- the skill, written out in plain English
openrouter
OpenRouter multi-vendor LLM gateway for all snappy-* skills.
Ported from kernel snappy-openrouter in Phase 0.5. See state/lib/openrouter.ts for the full API surface.
Steps
chat()- seestate/lib/openrouter.tschatWithFallback()- seestate/lib/openrouter.ts
Eval
Actor: the exported functions in state/lib/openrouter.ts. Auditor: none wired yet - eval is manual (Robert review). File a state/log/pending-eval.ndjson row on each run.
Score convention:
| Outcome | Score |
|---|---|
| Pass on first try | 1.0 |
| Failed first, auto-fix applied, re-check passed | 0.5 |
| Still failing or unrecoverable | 0.0 |
Gotchas
via the Phase 0.5 driver. Only these rewrites were applied: already in state/lib/)
realpathSync(process.argv[1])CLI guard wrapped in try/catch
- See the kernel SKILL.md for the original long-form guidance if you need it
(read-only reference at the kernel path above).
Graduation
This skill is prose. Graduate by defining a deterministic auditor and flipping eval: auto.
Rubric
criteria:
- name: chat_function_exists
kind: deterministic
check: "The 'chat' function is exported from 'state/lib/openrouter.ts'."
- name: chat_with_fallback_exists
kind: deterministic
check: "The 'chatWithFallback' function is exported from 'state/lib/openrouter.ts'."
- name: chat_returns_valid_response
kind: judge
check: "The output of the 'chat' function for a given input is a semantically coherent and relevant response from OpenRouter."
- name: chat_with_fallback_attempts_fallback
kind: judge
check: "When a primary model fails, the 'chatWithFallback' function demonstrably attempts to use a fallback model, producing a response if successful."AGENTS.md- what the AI loads when this skill comes up
openrouter - loader
Per-turn rules for the openrouter skill. Full reference: state/skills/openrouter/SKILL.md. Do not skip these.
Critical Rules
- NEVER hardcode an API key - use
env("OPENROUTER_API_KEY")fromstate/lib/env.tsorenv("KEY")throws - Prefer
state/lib/dispatch.tsfor cheap-labor grunt work -dispatch.tsis the canonical PID-loop dispatch path and logs tostate/log/dispatches.ndjsonfor cost/latency audit. Reach foropenrouterdirectly only when you specifically need the multi-vendor fallback chain. - Every dispatch logs one ndjson line - do not bypass the audit log
Commands
| ui dashboard | state/skills/openrouter/resources/ui.openui | |invoke: import from state/lib/openrouter.ts - chat(), chatWithFallback() |preferred for grunt work: state/lib/dispatch.ts (haiku/sonnet/gemini/llama/qwen/deepseek) |eval log: state/log/pending-eval.ndjson (manual review until shape gate added) |cost audit: state/log/dispatches.ndjson
OpenUI Resource
- Skill-owned OpenUI Lang resource:
state/skills/openrouter/resources/ui.openui. Read it before rendering or editing this skill's generated component surface. - Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
- System resources compose OpenUI primitives and inherit SnappyChat tokens. Use
ui_contract: brandedin SKILL.md only for deliberate platform or client visuals.
Known Pitfalls
- Phase 0.5 port from
snappy-openrouter- mechanical, no hard-won rules in the page - "Use cheap models for mechanical/verifiable work, keep judgment on the orchestrator" - program.md cheap-labor dispatch rule applies
- During interactive work with Robert, Opus drafts directly - reserve dispatch for background/bulk jobs
Self-Test
An agent reading this should correctly:
- [ ] Prefer
state/lib/dispatch.tsover rawopenrouterfor routine cheap-labor calls? - [ ] Pull the API key via
env("OPENROUTER_API_KEY")rather than reading the cache file directly? - [ ] Skip openrouter dispatch when in interactive Robert-in-room work?
Self-report
If this loader fell short, append a line:
echo "[$(date -u +%FT%TZ)] openrouter: <what was missing>" >> state/log/loader-feedback.log
<!-- kernel-ok: historical attribution for the PID-loader pattern. -->
Self-correcting loader (PID feedback)
This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.
Before you finish, do two things:
1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.
- Default action: edit this file. Surgical. Add the missing line, table
row, or code example where it belongs. No restructuring.
- Only
LOGGEDis allowed when: the fix needs >10 lines, spans multiple
files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.
- "I didn't have time" / "it's minor" / "the next agent will figure it out"
are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.
- Concrete example of a valid P-fix: discover
agent-browser screenshot
takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.
- The goal: the next agent never has to leave the loader.
2. Log the result.
echo "[$(date -u +%FT%TZ)] openrouter: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log
FIXED= you patched this loader inline (P-fix).LOGGED= too large for inline; the PostToolUse enqueue + Stop-hook drain
will rewrite the loader from scratch on next session-end.
Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.
api.ts- the code it can call
#!/usr/bin/env npx tsx
/**
* snappy-openrouter/api.ts -- OpenRouter multi-vendor LLM gateway for all snappy-* skills.
*
* Uses OPENROUTER_API_KEY from snappy-settings/.env.cache.
* OpenAI-compatible API at https://openrouter.ai/api/v1.
*
* Usage:
* npx tsx api.ts chat "Explain quantum tunneling"
* npx tsx api.ts chat "Summarize this" --model anthropic/claude-3.5-sonnet
*
* Or import as module:
* import { chat, chatWithFallback } from "./openrouter.ts";
*/
import { env } from "./env.ts";
import { realpathSync } from "fs";
const BASE = "https://openrouter.ai/api/v1";
const DEFAULT_MODEL = "anthropic/claude-3.5-sonnet";
interface ChatOptions {
model?: string;
systemPrompt?: string;
temperature?: number;
maxTokens?: number;
}
async function openrouter(path: string, body: Record<string, unknown>): Promise<unknown> {
const res = await fetch(`${BASE}${path}`, {
method: "POST",
headers: {
Authorization: `Bearer ${env("OPENROUTER_API_KEY")}`,
"Content-Type": "application/json",
"HTTP-Referer": "https://snappy.ai",
"X-Title": "Snappy",
},
body: JSON.stringify(body),
});
if (!res.ok) {
const err = await res.text();
throw new Error(`OpenRouter failed (${res.status}): ${err}`);
}
return res.json();
}
function buildMessages(prompt: string, systemPrompt?: string) {
const messages: { role: string; content: string }[] = [];
if (systemPrompt) messages.push({ role: "system", content: systemPrompt });
messages.push({ role: "user", content: prompt });
return messages;
}
// --- Public API ---
export async function chat(prompt: string, opts: ChatOptions = {}): Promise<{ text: string; model: string; raw: unknown }> {
const model = opts.model || DEFAULT_MODEL;
const data = await openrouter("/chat/completions", {
model,
messages: buildMessages(prompt, opts.systemPrompt),
...(opts.temperature != null ? { temperature: opts.temperature } : {}),
...(opts.maxTokens ? { max_tokens: opts.maxTokens } : {}),
}) as any;
const text = data.choices?.[0]?.message?.content || "";
const usedModel = data.model || model;
return { text, model: usedModel, raw: data };
}
export async function chatWithFallback(prompt: string, models: string[], opts: Omit<ChatOptions, "model"> = {}): Promise<{ text: string; model: string; raw: unknown }> {
const data = await openrouter("/chat/completions", {
models,
messages: buildMessages(prompt, opts.systemPrompt),
...(opts.temperature != null ? { temperature: opts.temperature } : {}),
...(opts.maxTokens ? { max_tokens: opts.maxTokens } : {}),
route: "fallback",
}) as any;
const text = data.choices?.[0]?.message?.content || "";
const usedModel = data.model || models[0];
return { text, model: usedModel, raw: data };
}
// --- CLI ---
if ((() => { try { return import.meta.url === `file://${realpathSync(process.argv[1])}`; } catch { return false; } })()) {
(async () => {
const [, , cmd, ...args] = process.argv;
switch (cmd) {
case "chat": {
const prompt = args.filter(a => !a.startsWith("--")).join(" ");
const modelIdx = args.indexOf("--model");
const model = modelIdx >= 0 ? args[modelIdx + 1] : undefined;
if (!prompt) { console.error("Usage: api.ts chat <prompt> [--model <model>]"); process.exit(1); }
const { text, model: used } = await chat(prompt, { model });
console.log(`[${used}]`);
console.log(text);
break;
}
case "fallback": {
const prompt = args.filter(a => !a.startsWith("--")).join(" ");
const modelsIdx = args.indexOf("--models");
const models = modelsIdx >= 0 ? args[modelsIdx + 1].split(",") : ["anthropic/claude-3.5-sonnet", "openai/gpt-4o", "deepseek/deepseek-chat"];
if (!prompt) { console.error("Usage: api.ts fallback <prompt> [--models <a,b,c>]"); process.exit(1); }
const { text, model: used } = await chatWithFallback(prompt, models);
console.log(`[${used}]`);
console.log(text);
break;
}
default:
console.log("Usage: npx tsx api.ts [chat|fallback] ...");
}
})();
}
scripts- helper scripts it can run
prose-only skill - 1 inline code block live in SKILL.md above (no state/bin/ sidecar yet).
how we check it- the checks, plus the last 10 runs
| timestamp | verb | score | primary_issue | artifact |
|---|---|---|---|---|
| 2026-04-25 04:11Z | - | 1.00 | - | - |
| 2026-04-21 15:59Z | - | 1.00 | - | - |
| 2026-04-21 15:56Z | - | 1.00 | - | - |
| 2026-04-21 03:53Z | - | 1.00 | - | - |
| 2026-04-25 04:11Z | - | 1.00 | - | - |
| 2026-04-21 15:59Z | - | 1.00 | - | - |
| 2026-04-21 15:56Z | - | 1.00 | - | - |
| 2026-04-21 03:53Z | - | 1.00 | - | - |
| 2026-04-25 04:11Z | - | 1.00 | - | - |
| 2026-04-21 15:59Z | - | 1.00 | - | - |