Answers from the documentation; checking which model is on duty
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.
Imported from ssrjkk/claude-skills (.claude/skills/networking/tls-ssl-troubleshooting/SKILL.md). Install upstream with npx skills add ssrjkk/claude-skills --skill tls-ssl-troubleshooting. Copyright stays with the author.
TLS/SSL Troubleshooting
Troubleshooting with TLS/SSL. diagnostics.
Quick Start
TLS/SSL Troubleshooting
See TLS/SSL docs
When to Use
diagnostics
debug
solving
Step-by-Step
Set up TLS/SSL
Configure Troubleshooting
Implement features
Test and verify
Deploy and monitor
Dependencies
No external dependencies required: No external dependencies
Examples
TLS/SSL Troubleshooting
See TLS/SSL documentation
Resources
Best practices and guidelines
Industry standards
Validation
tls-ssl --version
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 slotcurl-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 tls-ssl-troubleshooting 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.
