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.
301-vitest - Skill - OpenSmartRoute
Skillv1.0.0
301-vitest
Create unit tests using Vitest and React Testing Library for component testing.
Instruction file imported from YoannDrx/mycryptopilot (.cursor/rules/prompts/301-vitest.mdc). Copyright stays with the author.
Context
Create unit tests in the /__tests__ folder at the project root.
Use only the root-level /__tests__ folder for all test files.
Iterate on tests and components until pnpm test:ci <file-name> passes successfully.
React Tests
import { setup } from "../test/setup";import { screen, waitFor } from "@testing-library/react";describe("ComponentName", () => { it("should do...", async () => { const { user } = setup(<DialogManagerWrapper />); // Use `screen` for element retreiving // Use `user` to interact with the page })})
Use it
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 301-vitest 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.
