How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

build-deck - Prompt - OpenSmartRoute

Name: build-deck
Author: cmfunderburk

Prompt file imported from cmfunderburk/knowledge-base-srs (.claude/commands/build-deck.md). Fill in {{Front}}, {{FrontSide}}, {{Back}} before use. Copyright stays with the author.

Build Anki Deck from Source Material

Build an Anki .apkg deck from source material (textbook chapter, article, PDF, notes) using genanki. Two note types: Enhanced Cloze (interactive reveal) and Basic (Q&A).

Inputs

The user provides:

Source material (file path, pasted text, or URL)
Deck name (Anki :: hierarchy, e.g., CFA::Reading 1)
Optionally: existing notes/summaries to start from

Phase 1: Extract and Classify

Read the source material thoroughly. Identify card-worthy knowledge — facts, formulas, definitions, reasoning, distinctions. Classify each piece:

Enhanced Cloze — when testing recall of components within a structure:

Formulas and equations
Decompositions (X = A + B + C)
Enumerations and lists
Definitions with key terms to blank

Basic Q&A — when the knowledge is a reasoning link:

"Why X?" / "When to use Y?" / "What distinguishes A from B?"
Conceptual explanations where the question framing matters
Comparisons and trade-offs

Heuristic: nouns/components → cloze, verbs/reasoning → Q&A.

Present the full card set to the user organized by section, with cloze content showing {{c1::...}} markers and Q&A showing Q/A pairs. Get approval before building.

Phase 2: Card Content Rules

Enhanced Cloze constraints

All clozes use {{c1::}} — not c1/c2/c3. Enhanced Cloze handles multiple c1 blanks per card, revealing them one at a time interactively.
LaTeX/MathJax constraint: Each {{c1::...}} that contains LaTeX MUST hold a complete \(...\) expression. You CANNOT put cloze deletions inside a LaTeX formula — the addon replaces clozes with HTML elements which breaks MathJax parsing.
- WRONG: \(R = \frac{ {{c1::P_1}} - {{c1::P_0}} }{ {{c1::P_0}} }\)
- RIGHT: Holding period return: {{c1::\(R = \frac{P_1 - P_0 + I_1}{P_0}\)}}
- RIGHT: \(r =\) {{c1::real risk-free rate}} + {{c1::inflation premium}} (LaTeX is a complete standalone expression outside clozes)
When a formula has multiple terms worth testing individually, but they can't be separated without breaking LaTeX, wrap the whole formula as a single cloze. Add a text label prefix (e.g., "Holding period return:") so the card has visible context when the formula is hidden.

LaTeX formatting

Use \(...\) delimiters (MathJax inline math)
Never use \text{...} inside a cloze — the closing } collides with the cloze }}, breaking Anki's parser. Use escaped spaces instead: inflation\ premium not \text{inflation premium}.
\text{...} is fine in LaTeX that is NOT inside a cloze deletion.
Anki renders via MathJax — standard LaTeX math commands work

Compression principles

Every word costs time across hundreds of reps — be telegraphic
Merge redundant bullets from the source
Kill vague "choice depends on..." bullets — make them concrete Q&A cards instead
Add text labels to formula clozes for context

Phase 3: Build Export Script

Create a standalone script at scripts/<deck_name>/export_apkg.py following the established pattern.

Critical: Model IDs must match installed Anki note types

The genanki model IDs MUST match the IDs Anki assigned to the installed note types. Using arbitrary IDs creates duplicate note types (e.g., "Enhanced Cloze 2.1 v2+") and cards won't render correctly.

To find the real IDs, read from the Anki collection database (Anki must be closed):

import sqlite3
db = sqlite3.connect(Path.home() / ".local/share/Anki2/User 1/collection.anki2")
rows = db.execute("SELECT id, name FROM notetypes").fetchall()
for r in rows:
    print(f"ID: {r[0]}, Name: {r[1]}")

Current known IDs (verify these still match before using):

Enhanced Cloze 2.1 v2: 1775602039195
Basic: 1691317181386

Enhanced Cloze templates must come from the addon

The export script must read the actual front/back/CSS templates from the installed Enhanced Cloze addon directory. Placeholder templates will override the addon's rich HTML/CSS/JS on import, breaking interactive cloze behavior.

ADDON_NOTE_TYPE_DIR = Path.home() / ".local/share/Anki2/addons21/1990296174/note_type"

def _read_addon_templates():
    front = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_Front_Side.html").read_text()
    back = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_Back_Side.html").read_text()
    css = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_CSS.css").read_text()
    return front, back, css

Script structure

# Models
cloze_model = genanki.Model(
    CLOZE_MODEL_ID,                    # from Anki DB
    "Enhanced Cloze 2.1 v2",           # must match installed name
    fields=[Content, Note, Mnemonics, Extra, Cloze99],
    templates=[{"name": "Enhanced Cloze", "qfmt": front_html, "afmt": back_html}],
    css=css,
    model_type=genanki.Model.CLOZE,
)

basic_model = genanki.Model(
    BASIC_MODEL_ID,                    # from Anki DB
    "Basic",                           # must match installed name
    fields=[Front, Back],
    templates=[{"name": "Card 1", "qfmt": "{{Front}}", "afmt": "{{FrontSide}}<hr id=answer>{{Back}}"}],
)

# Card data — hardcoded tuples
CLOZE_CARDS = [("card_id", "content with {{c1::...}}", ["tag"]), ...]
QA_CARDS = [("card_id", "front", "back", ["tag"]), ...]

# Stable GUIDs via SHA-256 for safe re-import
def stable_guid(card_id): return hashlib.sha256(card_id.encode()).hexdigest()[:10]

Output

Script: scripts/<name>/export_apkg.py
Output: scripts/<name>/<name>.apkg (gitignored)
Run: uv run python scripts/<name>/export_apkg.py

Phase 4: Verify

After generating the .apkg, ask the user to:

Close Anki (if model IDs need checking)
Import the .apkg
Spot-check: Enhanced Cloze styling (colored brackets, interactive reveal), MathJax rendering, Q&A front/back, tags

If cards don't render correctly, the most common issues are:

Wrong model ID → duplicate note types created
Placeholder templates → no Enhanced Cloze styling
Cloze inside LaTeX → MathJax broken

Reference: Existing export scripts

Pattern examples in this repo:

scripts/cfa_reading1/export_apkg.py — Enhanced Cloze + Basic, LaTeX
scripts/govt_spending/export_apkg.py — Enhanced Cloze Type-In, SVG charts
scripts/german_vocab/export_apkg.py — custom bidirectional model

Install build-deck and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Build Anki Deck from Source Material Build an Anki .apkg deck from source material (textbook chapter, article, PDF, notes) using genanki. Two note types: Enhanced Cloze (interactive reveal) and Basic (Q&A). ## Inputs The user provides: - Source material (file path, pasted text, or URL) - Deck name (Anki `::` hierarchy, e.g., `CFA::Reading 1`) - Optionally: existing notes/summaries to start from ## Phase 1: Extract and Classify Read the source material thoroughly. Identify card-worthy knowledge — facts, formulas, definitions, reasoning, distinctions. Classify each piece: **Enhanced Cloze** — when testing recall of components within a structure: - Formulas and equations - Decompositions (X = A + B + C) - Enumerations and lists - Definitions with key terms to blank **Basic Q&A** — when the knowledge is a reasoning link: - "Why X?" / "When to use Y?" / "What distinguishes A from B?" - Conceptual explanations where the question framing matters - Comparisons and trade-offs **Heuristic:** nouns/components → cloze, verbs/reasoning → Q&A. Present the full card set to the user organized by section, with cloze content showing `{{c1::...}}` markers and Q&A showing Q/A pairs. Get approval before building. ## Phase 2: Card Content Rules ### Enhanced Cloze constraints - **All clozes use `{{c1::}}`** — not c1/c2/c3. Enhanced Cloze handles multiple c1 blanks per card, revealing them one at a time interactively. - **LaTeX/MathJax constraint:** Each `{{c1::...}}` that contains LaTeX MUST hold a complete `\(...\)` expression. You CANNOT put cloze deletions inside a LaTeX formula — the addon replaces clozes with HTML elements which breaks MathJax parsing. - WRONG: `\(R = \frac{ {{c1::P_1}} - {{c1::P_0}} }{ {{c1::P_0}} }\)` - RIGHT: `Holding period return: {{c1::\(R = \frac{P_1 - P_0 + I_1}{P_0}\)}}` - RIGHT: `\(r =\) {{c1::real risk-free rate}} + {{c1::inflation premium}}` (LaTeX is a complete standalone expression outside clozes) - When a formula has multiple terms worth testing individually, but they can't be separated without breaking LaTeX, wrap the whole formula as a single cloze. Add a text label prefix (e.g., "Holding period return:") so the card has visible context when the formula is hidden. ### LaTeX formatting - Use `\(...\)` delimiters (MathJax inline math) - **Never use `\text{...}` inside a cloze** — the closing `}` collides with the cloze `}}`, breaking Anki's parser. Use escaped spaces instead: `inflation\ premium` not `\text{inflation premium}`. - `\text{...}` is fine in LaTeX that is NOT inside a cloze deletion. - Anki renders via MathJax — standard LaTeX math commands work ### Compression principles - Every word costs time across hundreds of reps — be telegraphic - Merge redundant bullets from the source - Kill vague "choice depends on..." bullets — make them concrete Q&A cards instead - Add text labels to formula clozes for context ## Phase 3: Build Export Script Create a standalone script at `scripts/<deck_name>/export_apkg.py` following the established pattern. ### Critical: Model IDs must match installed Anki note types The genanki model IDs MUST match the IDs Anki assigned to the installed note types. Using arbitrary IDs creates duplicate note types (e.g., "Enhanced Cloze 2.1 v2+") and cards won't render correctly. To find the real IDs, read from the Anki collection database (Anki must be closed): ```python import sqlite3 db = sqlite3.connect(Path.home() / ".local/share/Anki2/User 1/collection.anki2") rows = db.execute("SELECT id, name FROM notetypes").fetchall() for r in rows: print(f"ID: {r[0]}, Name: {r[1]}") ``` Current known IDs (verify these still match before using): - Enhanced Cloze 2.1 v2: `1775602039195` - Basic: `1691317181386` ### Enhanced Cloze templates must come from the addon The export script must read the actual front/back/CSS templates from the installed Enhanced Cloze addon directory. Placeholder templates will override the addon's rich HTML/CSS/JS on import, breaking interactive cloze behavior. ```python ADDON_NOTE_TYPE_DIR = Path.home() / ".local/share/Anki2/addons21/1990296174/note_type" def _read_addon_templates(): front = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_Front_Side.html").read_text() back = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_Back_Side.html").read_text() css = (ADDON_NOTE_TYPE_DIR / "Enhanced_Cloze_CSS.css").read_text() return front, back, css ``` ### Script structure ```python # Models cloze_model = genanki.Model( CLOZE_MODEL_ID, # from Anki DB "Enhanced Cloze 2.1 v2", # must match installed name fields=[Content, Note, Mnemonics, Extra, Cloze99], templates=[{"name": "Enhanced Cloze", "qfmt": front_html, "afmt": back_html}], css=css, model_type=genanki.Model.CLOZE, ) basic_model = genanki.Model( BASIC_MODEL_ID, # from Anki DB "Basic", # must match installed name fields=[Front, Back], templates=[{"name": "Card 1", "qfmt": "{{Front}}", "afmt": "{{FrontSide}}<hr id=answer>{{Back}}"}], ) # Card data — hardcoded tuples CLOZE_CARDS = [("card_id", "content with {{c1::...}}", ["tag"]), ...] QA_CARDS = [("card_id", "front", "back", ["tag"]), ...] # Stable GUIDs via SHA-256 for safe re-import def stable_guid(card_id): return hashlib.sha256(card_id.encode()).hexdigest()[:10] ``` ### Tags Use hierarchical tags: `DeckPrefix::ReadingOrChapter::Section` (e.g., `CFA::R1::1.2`). ### Output - Script: `scripts/<name>/export_apkg.py` - Output: `scripts/<name>/<name>.apkg` (gitignored) - Run: `uv run python scripts/<name>/export_apkg.py` ## Phase 4: Verify After generating the .apkg, ask the user to: 1. Close Anki (if model IDs need checking) 2. Import the .apkg 3. Spot-check: Enhanced Cloze styling (colored brackets, interactive reveal), MathJax rendering, Q&A front/back, tags If cards don't render correctly, the most common issues are: - Wrong model ID → duplicate note types created - Placeholder templates → no Enhanced Cloze styling - Cloze inside LaTeX → MathJax broken ## Reference: Existing export scripts Pattern examples in this repo: - `scripts/cfa_reading1/export_apkg.py` — Enhanced Cloze + Basic, LaTeX - `scripts/govt_spending/export_apkg.py` — Enhanced Cloze Type-In, SVG charts - `scripts/german_vocab/export_apkg.py` — custom bidirectional model

{ "prompt": "# Build Anki Deck from Source Material\n\nBuild an Anki .apkg deck from source material (textbook chapter, article, PDF, notes) using genanki. Two note types: Enhanced Cloze (interactive reveal) and Basic (Q&A).\n\n## Inputs\n\nThe user provides:\n- Source material (file path, pasted text, or URL)\n- Deck name (Anki `::` hierarchy, e.g., `CFA::Reading 1`)\n- Optionally: existing notes/summaries to start from\n\n## Phase 1: Extract and Classify\n\nRead the source material thoroughly. Identify card-worthy knowledge — facts, formulas, definitions, reasoning, distinctions. Classify each piece:\n\n**Enhanced Cloze** — when testing recall of components within a structure:\n- Formulas and equations\n- Decompositions (X = A + B + C)\n- Enumerations and lists\n- Definitions with key terms to blank\n\n**Basic Q&A** — when the knowledge is a reasoning link:\n- \"Why X?\" / \"When to use Y?\" / \"What distinguishes A from B?\"\n- Conceptual explanations where the question framing matters\n- Comparisons and trade-offs\n\n**Heuristic:** nouns/components → cloze, verbs/reasoning → Q&A.\n\nPresent the full card set to the user organized by section, with cloze content showing `{{c1::...}}` markers and Q&A showing Q/A pairs. Get approval before building.\n\n## Phase 2: Card Content Rules\n\n### Enhanced Cloze constraints\n- **All clozes use `{{c1::}}`** — not c1/c2/c3. Enhanced Cloze handles multiple c1 blanks per card, revealing them one at a time interactively.\n- **LaTeX/MathJax constraint:** Each `{{c1::...}}` that contains LaTeX MUST hold a complete `\\(...\\)` expression. You CANNOT put cloze deletions inside a LaTeX formula — the addon replaces clozes with HTML elements which breaks MathJax parsing.\n - WRONG: `\\(R = \\frac{ {{c1::P_1}} - {{c1::P_0}} }{ {{c1::P_0}} }\\)`\n - RIGHT: `Holding period return: {{c1::\\(R = \\frac{P_1 - P_0 + I_1}{P_0}\\)}}`\n - RIGHT: `\\(r =\\) {{c1::real risk-free rate}} + {{c1::inflation premium}}` (LaTeX is a complete standalone expression outside clozes)\n- When a formula has multiple terms worth testing individually, but they can't be separated without breaking LaTeX, wrap the whole formula as a single cloze. Add a text label prefix (e.g., \"Holding period return:\") so the card has visible context when the formula is hidden.\n\n### LaTeX formatting\n- Use `\\(...\\)` delimiters (MathJax inline math)\n- **Never use `\\text{...}` inside a cloze** — the closing `}` collides with the cloze `}}`, breaking Anki's parser. Use escaped spaces instead: `inflation\\ premium` not `\\text{inflation premium}`.\n- `\\text{...}` is fine in LaTeX that is NOT inside a cloze deletion.\n- Anki renders via MathJax — standard LaTeX math commands work\n\n### Compression principles\n- Every word costs time across hundreds of reps — be telegraphic\n- Merge redundant bullets from the source\n- Kill vague \"choice depends on...\" bullets — make them concrete Q&A cards instead\n- Add text labels to formula clozes for context\n\n## Phase 3: Build Export Script\n\nCreate a standalone script at `scripts/<deck_name>/export_apkg.py` following the established pattern.\n\n### Critical: Model IDs must match installed Anki note types\n\nThe genanki model IDs MUST match the IDs Anki assigned to the installed note types. Using arbitrary IDs creates duplicate note types (e.g., \"Enhanced Cloze 2.1 v2+\") and cards won't render correctly.\n\nTo find the real IDs, read from the Anki collection database (Anki must be closed):\n\n```python\nimport sqlite3\ndb = sqlite3.connect(Path.home() / \".local/share/Anki2/User 1/collection.anki2\")\nrows = db.execute(\"SELECT id, name FROM notetypes\").fetchall()\nfor r in rows:\n print(f\"ID: {r[0]}, Name: {r[1]}\")\n```\n\nCurrent known IDs (verify these still match before using):\n- Enhanced Cloze 2.1 v2: `1775602039195`\n- Basic: `1691317181386`\n\n### Enhanced Cloze templates must come from the addon\n\nThe export script must read the actual front/back/CSS templates from the installed Enhanced Cloze addon directory. Placeholder templates will override the addon's rich HTML/CSS/JS on import, breaking interactive cloze behavior.\n\n```python\nADDON_NOTE_TYPE_DIR = Path.home() / \".local/share/Anki2/addons21/1990296174/note_type\"\n\ndef _read_addon_templates():\n front = (ADDON_NOTE_TYPE_DIR / \"Enhanced_Cloze_Front_Side.html\").read_text()\n back = (ADDON_NOTE_TYPE_DIR / \"Enhanced_Cloze_Back_Side.html\").read_text()\n css = (ADDON_NOTE_TYPE_DIR / \"Enhanced_Cloze_CSS.css\").read_text()\n return front, back, css\n```\n\n### Script structure\n\n```python\n# Models\ncloze_model = genanki.Model(\n CLOZE_MODEL_ID, # from Anki DB\n \"Enhanced Cloze 2.1 v2\", # must match installed name\n fields=[Content, Note, Mnemonics, Extra, Cloze99],\n templates=[{\"name\": \"Enhanced Cloze\", \"qfmt\": front_html, \"afmt\": back_html}],\n css=css,\n model_type=genanki.Model.CLOZE,\n)\n\nbasic_model = genanki.Model(\n BASIC_MODEL_ID, # from Anki DB\n \"Basic\", # must match installed name\n fields=[Front, Back],\n templates=[{\"name\": \"Card 1\", \"qfmt\": \"{{Front}}\", \"afmt\": \"{{FrontSide}}<hr id=answer>{{Back}}\"}],\n)\n\n# Card data — hardcoded tuples\nCLOZE_CARDS = [(\"card_id\", \"content with {{c1::...}}\", [\"tag\"]), ...]\nQA_CARDS = [(\"card_id\", \"front\", \"back\", [\"tag\"]), ...]\n\n# Stable GUIDs via SHA-256 for safe re-import\ndef stable_guid(card_id): return hashlib.sha256(card_id.encode()).hexdigest()[:10]\n```\n\n### Tags\nUse hierarchical tags: `DeckPrefix::ReadingOrChapter::Section` (e.g., `CFA::R1::1.2`).\n\n### Output\n- Script: `scripts/<name>/export_apkg.py`\n- Output: `scripts/<name>/<name>.apkg` (gitignored)\n- Run: `uv run python scripts/<name>/export_apkg.py`\n\n## Phase 4: Verify\n\nAfter generating the .apkg, ask the user to:\n1. Close Anki (if model IDs need checking)\n2. Import the .apkg\n3. Spot-check: Enhanced Cloze styling (colored brackets, interactive reveal), MathJax rendering, Q&A front/back, tags\n\nIf cards don't render correctly, the most common issues are:\n- Wrong model ID → duplicate note types created\n- Placeholder templates → no Enhanced Cloze styling\n- Cloze inside LaTeX → MathJax broken\n\n## Reference: Existing export scripts\n\nPattern examples in this repo:\n- `scripts/cfa_reading1/export_apkg.py` — Enhanced Cloze + Basic, LaTeX\n- `scripts/govt_spending/export_apkg.py` — Enhanced Cloze Type-In, SVG charts\n- `scripts/german_vocab/export_apkg.py` — custom bidirectional model", "variables": [ "Front", "FrontSide", "Back" ], "notes": "Build an Anki .apkg deck from source material (textbook chapter, article, PDF, notes) using genanki. Two note types: Enhanced Cloze (interactive reveal) and Basic (Q&A).", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/cmfunderburk/knowledge-base-srs", "path": ".claude/commands/build-deck.md", "ref": "e5ace8b6f8060c288e76a042b0f47ce48cc8c019", "url": "https://github.com/cmfunderburk/knowledge-base-srs/blob/e5ace8b6f8060c288e76a042b0f47ce48cc8c019/.claude/commands/build-deck.md", "key": "cmfunderburk/knowledge-base-srs/.claude/commands/build-deck.md" } } }

build-deck

About

Build Anki Deck from Source Material

Inputs

Phase 1: Extract and Classify

Phase 2: Card Content Rules

Enhanced Cloze constraints

LaTeX formatting

Compression principles

Phase 3: Build Export Script

Critical: Model IDs must match installed Anki note types

Enhanced Cloze templates must come from the addon

Script structure

Tags

Output

Phase 4: Verify

Reference: Existing export scripts

Install build-deck and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews