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/iot/aws-iot-dashboards/SKILL.md). Install upstream with npx skills add ssrjkk/claude-skills --skill aws-iot-dashboards. Copyright stays with the author.
AWS IoT Dashboards
Dashboards with AWS IoT. dashboards.
Quick Start
# AWS IoT Dashboards# See AWS IoT docs
When to Use
Deploying on AWS IoT
dashboards
visualization
Step-by-Step
Sign up / configure: # Install AWS IoT
Set up AWS IoT
Configure Dashboards
Implement features
Dependencies
AWS IoT account
Runtime environment
Examples
# AWS IoT Dashboards# See AWS IoT documentation
Resources
AWS IoT documentation
API reference
Validation
Verify: aws-iot --version
Check dashboard / logs
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 aws-iot-dashboards 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.
