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.

verify-flow - Skill - OpenSmartRoute

Name: verify-flow
Author: muratcakmak

Imported from muratcakmak/Shipwright (skills/verify-flow/SKILL.md). Install upstream with npx skills add muratcakmak/Shipwright --skill verify-flow. Copyright stays with the author.

Verify Flow

Verify a multi-screen flow by recording it in the iOS Simulator.

Flow: $ARGUMENTS

MANDATORY PREPARATION

Read Shipwright Context from CLAUDE.md for navigation structure and bundle ID
Understand the flow — which screens are involved, in what order, and what interactions trigger transitions
Read the screen source files to understand expected behavior at each step

VERIFICATION PROTOCOL

Step 1: Boot & Launch

Boot the simulator and launch the app
Navigate to the starting point of the flow

Step 2: Start Recording

Use mcp__ios-simulator__record_video to start recording the flow

Step 3: Execute Flow Steps

For each step in the flow:

Screenshot — Capture the current screen state
Describe — Get the accessibility tree to verify correct elements are present
Interact — Tap, type, or swipe to advance to the next step
Wait — Allow transitions to complete (animations, loading states)
Screenshot — Capture the result of the interaction

Document each step:

Step 1: [Screen Name]
- Elements present: [key elements from accessibility tree]
- Action: [what interaction was performed]
- Expected result: [what should happen]
- Actual result: [what did happen]
- Screenshot: [captured]

Step 4: Stop Recording

Use mcp__ios-simulator__stop_recording to save the video

Step 5: Flow Analysis

Transition Quality

Were transitions smooth (no jank or stuttering)?
Did navigation animations use the correct iOS pattern (push from right, modal from bottom)?
Were there any flash of blank/white screens between transitions?

Data Persistence

Did data entered on one screen appear correctly on the next?
Did selections persist through the flow?
Was form state preserved when navigating back?

State Consistency

Were loading states shown when data was being fetched?
Did error states appear when expected?
Were all UI elements updated after state changes?

Back Navigation

Does pressing back return to the previous screen in correct state?
Is the back gesture (swipe from left edge) working?
On modals, does the dismiss gesture work?

Step 6: Generate Report

## Flow Verification Report: [Flow Name]

**Device:** [simulator device]
**Date:** [date]
**Video:** [video file path]

### Flow Steps
| Step | Screen | Action | Result | Status |
|---|---|---|---|---|
| 1 | [name] | [action] | [result] | PASS/FAIL |
| 2 | ... | ... | ... | ... |

### Transition Quality: [PASS/FAIL]
- [details on any transition issues]

### Data Persistence: [PASS/FAIL]
- [details on data flow between screens]

### Back Navigation: [PASS/FAIL]
- [details on back navigation behavior]

### Issues Found
1. [Severity: HIGH/MEDIUM/LOW] — [description + suggested fix]

### Overall: [PASS/NEEDS WORK/FAIL]

CHECKLIST

Simulator booted and app launched
Video recording started
Each flow step captured with screenshot + accessibility tree
All transitions verified for smoothness
Data persistence checked across screens
Back navigation tested
Video recording saved
Report generated

Install verify-flow 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": "muratcakmak-shipwright-verify-flow", "kind": "skill", "name": "verify-flow", "description": "Verify a multi-screen flow in the iOS Simulator. Records video, captures screenshots at each step, verifies transitions and data persistence across screens. Use after implementing navigation flows or animations.", "publisher": "muratcakmak", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Verify a multi-screen flow in the iOS Simulator. Records video, captures screenshots at each step, verifies transitions and data persistence across screens. Use after implementing navigation flows or animations." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/muratcakmak/Shipwright", "path": "skills/verify-flow/SKILL.md", "ref": "b1ab83155278b8ae61cc814c128247e71d9a720d", "url": "https://github.com/muratcakmak/Shipwright/blob/b1ab83155278b8ae61cc814c128247e71d9a720d/skills/verify-flow/SKILL.md", "key": "muratcakmak/Shipwright/skills/verify-flow/SKILL.md" }, "allowed_tools": [ "mcp__ios-simulator__get_booted_sim_id", "mcp__ios-simulator__open_simulator", "mcp__ios-simulator__launch_app", "mcp__ios-simulator__screenshot", "mcp__ios-simulator__ui_describe_all", "mcp__ios-simulator__ui_tap", "mcp__ios-simulator__ui_type", "mcp__ios-simulator__ui_swipe", "mcp__ios-simulator__record_video", "mcp__ios-simulator__stop_recording", "Bash", "Read", "Glob", "Grep", "Agent" ] }, "instructions": "# Verify Flow\n\nVerify a multi-screen flow by recording it in the iOS Simulator.\n\n**Flow:** $ARGUMENTS\n\n## MANDATORY PREPARATION\n\n1. **Read Shipwright Context** from CLAUDE.md for navigation structure and bundle ID\n2. **Understand the flow** — which screens are involved, in what order, and what interactions trigger transitions\n3. **Read the screen source files** to understand expected behavior at each step\n\n## VERIFICATION PROTOCOL\n\n### Step 1: Boot & Launch\n1. Boot the simulator and launch the app\n2. Navigate to the starting point of the flow\n\n### Step 2: Start Recording\n```\nUse mcp__ios-simul", "cost": { "context_tokens": 795 } }

verify-flow

About

Verify Flow

MANDATORY PREPARATION

VERIFICATION PROTOCOL

Step 1: Boot & Launch

Step 2: Start Recording

Step 3: Execute Flow Steps

Step 4: Stop Recording

Step 5: Flow Analysis

Transition Quality

Data Persistence

State Consistency

Back Navigation

Step 6: Generate Report

CHECKLIST

Install verify-flow 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