Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
swiftui-autotest-skill - Skill - OpenSmartRoute
Skillv1.0.0
swiftui-autotest-skill
AI-powered visual testing and accessibility setup for iOS/SwiftUI apps. Build, launch in Simulator, test with computer use, detect crashes, analyze memory leaks, and add accessibility identifiers — al
Imported from yusufkaran/swiftui-autotest-skill (SKILL.md). Install upstream with npx skills add yusufkaran/swiftui-autotest-skill. Copyright stays with the author.
SwiftUI Autotest Skill
Automated visual testing and accessibility identifier generation for iOS/SwiftUI applications using Claude Code's computer use.
Included Skills
ios-test — Build, launch in Simulator, visually test with computer use, crash log analysis, state testing (empty/error/loading), performance analysis (RAM/memory leaks)
add-accessibility — Scan SwiftUI views and add missing accessibility identifiers using {screen}-{type}-{name} convention, flag Dynamic Type issues
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install swiftui-autotest-skill 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.
