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.
investigate-first - Skill - OpenSmartRoute
Skillv1.0.0
investigate-first
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
Imported from yselimygt/skiller (09-is-akisi-otomasyon/investigate-first/SKILL.md). Install upstream with npx skills add yselimygt/skiller --skill investigate-first. Copyright stays with the author.
Investigate first
Gather evidence before changing product code.
Separate observed symptom from inferred cause.
Trace inputs, state transitions, ownership boundaries, and failure output.
Rank hypotheses by evidence and cheap falsification value.
Do not edit until one credible mechanism explains evidence.
Stop exploration when evidence is sufficient to name cause or exact blocker.
Report cause and proof. Make no fix unless task authorizes implementation.
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 investigate-first 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.
