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.
everloom-state - Skill - OpenSmartRoute
Skillv1.0.0
everloom-state
Files under `.everloom/` are operational project state, not decorative documentation.
Instruction file imported from Cowlsly/everloom-universal (.github/instructions/everloom-state.instructions.md). Copyright stays with the author.
Durable Everloom state instructions
Files under .everloom/ are operational project state, not decorative documentation.
When editing them:
preserve established objective, constraints, identifiers, decisions, and verification evidence unless fresh repository evidence justifies a change;
never erase unresolved blockers merely to simplify the file;
distinguish implementation from verification;
keep task states consistent with the ledger;
record material changed assumptions in DISCOVERIES.md;
update RESUME.md so a fresh worker can resume without chat history;
do not store secrets, credentials, tokens, private keys, or sensitive runtime values.
Do not mark work complete without objective evidence.
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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
