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.
meeting-prep-notion - Skill - OpenSmartRoute
Skillv1.0.0
meeting-prep-notion
Manage Rocky's Notion meeting prep database and idempotent prep-page upserts.
Imported from zabrodsk/Codexapp (skills/meeting-prep-notion/SKILL.md). Install upstream with npx skills add zabrodsk/Codexapp --skill meeting-prep-notion. Copyright stays with the author.
Meeting Prep Notion
Use this skill when Rocky stores a meeting prep artifact in Notion.
Database: Rocky Meeting Prep.
Required properties:
Title
Meeting date
Meeting key
Calendar event ref
Status
Context confidence
People / companies
Source refs
Dusan notes
Brief
Questions
Open loops
Discord status
Last sent at
Message hash
Updated date
Upsert by Meeting key. Creating/updating prep notes requires explicit live
mode. This skill must not mutate Rocky's personal task database except through
separate task-spine command paths.
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 meeting-prep-notion 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.
