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.

test-scenarios - Skill - OpenSmartRoute

Name: test-scenarios
Author: phuryn

Imported from phuryn/pm-skills (pm-execution/skills/test-scenarios/SKILL.md) via skills.sh. Install upstream with npx skills add phuryn/pm-skills --skill test-scenarios. Copyright stays with the author.

Test Scenarios

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.

Use when: Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.

Arguments:

$PRODUCT: The product or system name
$USER_STORY: The user story to test (title and acceptance criteria)
$CONTEXT: Additional testing context or constraints

Step-by-Step Process

Review the user story and acceptance criteria
Define test objectives - What specific behavior to validate
Establish starting conditions - System state, data setup, configurations
Identify user roles - Who performs the test actions
Create test steps - Break down interactions step-by-step
Define expected outcomes - Observable results after each step
Consider edge cases - Invalid inputs, boundary conditions
Output detailed test scenarios - Ready for QA execution

Scenario Template

Test Scenario: [Clear scenario name]

Test Objective: [What this test validates]

Starting Conditions:

[System state required]
[Data or configuration needed]
[User setup or permissions]

User Role: [Who performs the test]

Test Steps:

[First action and its expected result]
[Second action and observable outcome]
[Third action and system behavior]
[Completion action and final state]

Expected Outcomes:

[Observable result 1]
[Observable result 2]
[Observable result 3]

Example Test Scenario

Test Scenario: View Recently Viewed Products on Product Page

Test Objective: Verify that the 'Recently viewed' section displays correctly and excludes the current product.

Starting Conditions:

User is logged in or has browser history enabled
User has viewed at least 2 products in the current session
User is now on a product page different from previously viewed items

User Role: Online Shopper

Test Steps:

Navigate to any product page → Section should appear at bottom with previously viewed items
Scroll to bottom of page → "Recently viewed" section is visible with product cards
Verify product thumbnails → Images, titles, and prices are displayed correctly
Check current product → Current product is NOT in the recently viewed list
Click on a product card → User navigates to the corresponding product page

Expected Outcomes:

Recently viewed section appears only after viewing at least 1 prior product
Section displays 4-8 product cards with complete information
Current product is excluded from the list
Each card shows "Viewed X minutes/hours ago" timestamp
Clicking cards navigates to correct product pages
Performance: Section loads within 2 seconds

Output Deliverables

Comprehensive test scenarios for each acceptance criterion
Clear test objectives aligned with user story intent
Detailed step-by-step test actions
Observable expected outcomes after each step
Edge case and error scenario coverage
Ready for QA team execution and documentation

Install test-scenarios 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.

{ "ocm": "1", "id": "phuryn-pm-skills-test-scenarios", "kind": "skill", "name": "test-scenarios", "description": "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.", "publisher": "phuryn", "version": "1.0.0", "capabilities": { "domains": [ "creative", "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/phuryn/pm-skills", "path": "pm-execution/skills/test-scenarios/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/phuryn/pm-skills/test-scenarios", "key": "phuryn/pm-skills/pm-execution/skills/test-scenarios/SKILL.md" } }, "instructions": "# Test Scenarios\n\nCreate comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.\n\n**Use when:** Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.\n\n**Arguments:**\n- `$PRODUCT`: The product or system name\n- `$USER_STORY`: The user story to test (title and acceptance criteria)\n- `$CONTEXT`: Additional testing context or constraints\n\n## Step-by-Step Process\n\n1. **Review the user story** and acceptance criteria\n2. **Define test objec", "cost": { "context_tokens": 786 } }

test-scenarios

About

Test Scenarios

Step-by-Step Process

Scenario Template

Example Test Scenario

Output Deliverables

Install test-scenarios 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