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.

ssq - Prompt - OpenSmartRoute

Name: ssq
Author: Barqly

Prompt file imported from Barqly/barqly-vault (.claude/commands/ssq.md). Copyright stays with the author.

Quick Session Summary - Current Issue

Create a quick, focused summary of the immediate problem/discussion for review or handoff.

Instructions

Create a concise summary file with the following specifications:

Filename Format: ssq{DD}{MM}.{n}.md where:
- DD = day of month (01-31)
- MM = month (01-12)
- n = counter (1, 2, 3...) for multiple quick summaries in a day
Location: Save in ./handoff/ folder (create if it doesn't exist)
Purpose: This is for getting a second opinion, handing off a problem, or quickly documenting a specific issue

Template

# Quick Session Summary - [Issue Title]
**Date:** [Current timestamp]
**File:** ssq{DD}{MM}.{n}.md
**Purpose:** Quick handoff/review

## 🎯 Current Goal
[What we're trying to achieve right now - be specific]

## ❌ The Problem
[The specific issue/error we're facing]

## 🔍 What We've Tried
1. [Attempt 1] 
   → Result: [What happened]
2. [Attempt 2] 
   → Result: [What happened]
3. [Attempt 3] 
   → Result: [What happened]

## 💻 Current Code/Error

[Relevant code snippet or exact error message]


## 🤔 Claude's Current Approach
[What Claude is currently suggesting or trying to do]

## ⚠️ Concerns/Blockers
- [Any red flags with the current approach]
- [What's preventing progress]
- [Potential risks identified]

## 💭 Need Input On
- [ ] Is this approach correct?
- [ ] Are there better alternatives?
- [ ] Am I missing something obvious?
- [ ] [Specific question needing answer]

## 📁 Key Files Involved
- [Only list the immediately relevant files]
- [Include file paths relative to project root]

Execution

When creating the quick summary:

Focus ONLY on the current active problem
Keep it under 100 lines total
Be specific about what input/help is needed
Include the exact error message or problematic code
Make it easy for someone else to understand the issue quickly
Don't include historical context unless directly relevant to the current problem

After creating, show the file path and remind that this can be shared for review.

Install ssq 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.

# Quick Session Summary - Current Issue Create a quick, focused summary of the immediate problem/discussion for review or handoff. ## Instructions Create a concise summary file with the following specifications: 1. **Filename Format**: `ssq{DD}{MM}.{n}.md` where: - DD = day of month (01-31) - MM = month (01-12) - n = counter (1, 2, 3...) for multiple quick summaries in a day 2. **Location**: Save in `./handoff/` folder (create if it doesn't exist) 3. **Purpose**: This is for getting a second opinion, handing off a problem, or quickly documenting a specific issue ## Template ```markdown # Quick Session Summary - [Issue Title] **Date:** [Current timestamp] **File:** ssq{DD}{MM}.{n}.md **Purpose:** Quick handoff/review ## 🎯 Current Goal [What we're trying to achieve right now - be specific] ## ❌ The Problem [The specific issue/error we're facing] ## 🔍 What We've Tried 1. [Attempt 1] → Result: [What happened] 2. [Attempt 2] → Result: [What happened] 3. [Attempt 3] → Result: [What happened] ## 💻 Current Code/Error ``` [Relevant code snippet or exact error message] ``` ## 🤔 Claude's Current Approach [What Claude is currently suggesting or trying to do] ## ⚠️ Concerns/Blockers - [Any red flags with the current approach] - [What's preventing progress] - [Potential risks identified] ## 💭 Need Input On - [ ] Is this approach correct? - [ ] Are there better alternatives? - [ ] Am I missing something obvious? - [ ] [Specific question needing answer] ## 📁 Key Files Involved - [Only list the immediately relevant files] - [Include file paths relative to project root] ``` ## Execution When creating the quick summary: 1. Focus ONLY on the current active problem 2. Keep it under 100 lines total 3. Be specific about what input/help is needed 4. Include the exact error message or problematic code 5. Make it easy for someone else to understand the issue quickly 6. Don't include historical context unless directly relevant to the current problem After creating, show the file path and remind that this can be shared for review.

{ "prompt": "# Quick Session Summary - Current Issue\n\nCreate a quick, focused summary of the immediate problem/discussion for review or handoff.\n\n## Instructions\n\nCreate a concise summary file with the following specifications:\n\n1. **Filename Format**: `ssq{DD}{MM}.{n}.md` where:\n - DD = day of month (01-31)\n - MM = month (01-12)\n - n = counter (1, 2, 3...) for multiple quick summaries in a day\n\n2. **Location**: Save in `./handoff/` folder (create if it doesn't exist)\n\n3. **Purpose**: This is for getting a second opinion, handing off a problem, or quickly documenting a specific issue\n\n## Template\n\n```markdown\n# Quick Session Summary - [Issue Title]\n**Date:** [Current timestamp]\n**File:** ssq{DD}{MM}.{n}.md\n**Purpose:** Quick handoff/review\n\n## 🎯 Current Goal\n[What we're trying to achieve right now - be specific]\n\n## ❌ The Problem\n[The specific issue/error we're facing]\n\n## 🔍 What We've Tried\n1. [Attempt 1] \n → Result: [What happened]\n2. [Attempt 2] \n → Result: [What happened]\n3. [Attempt 3] \n → Result: [What happened]\n\n## 💻 Current Code/Error\n```\n[Relevant code snippet or exact error message]\n```\n\n## 🤔 Claude's Current Approach\n[What Claude is currently suggesting or trying to do]\n\n## ⚠️ Concerns/Blockers\n- [Any red flags with the current approach]\n- [What's preventing progress]\n- [Potential risks identified]\n\n## 💭 Need Input On\n- [ ] Is this approach correct?\n- [ ] Are there better alternatives?\n- [ ] Am I missing something obvious?\n- [ ] [Specific question needing answer]\n\n## 📁 Key Files Involved\n- [Only list the immediately relevant files]\n- [Include file paths relative to project root]\n```\n\n## Execution\n\nWhen creating the quick summary:\n1. Focus ONLY on the current active problem\n2. Keep it under 100 lines total\n3. Be specific about what input/help is needed\n4. Include the exact error message or problematic code\n5. Make it easy for someone else to understand the issue quickly\n6. Don't include historical context unless directly relevant to the current problem\n\nAfter creating, show the file path and remind that this can be shared for review.", "variables": [], "notes": "Create a quick, focused summary of the immediate problem/discussion for review or handoff.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/Barqly/barqly-vault", "path": ".claude/commands/ssq.md", "ref": "1d9c89d1a05b906dbc574c5df57a68390f63dbde", "url": "https://github.com/Barqly/barqly-vault/blob/1d9c89d1a05b906dbc574c5df57a68390f63dbde/.claude/commands/ssq.md", "key": "Barqly/barqly-vault/.claude/commands/ssq.md" } } }

ssq

About

Quick Session Summary - Current Issue

Instructions

Template

Execution

Install ssq 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