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.
git-sync - Skill - OpenSmartRoute
Skillv1.0.0
git-sync
Automatically syncs local workspace changes to the remote GitHub repository. Use after significant changes or periodically.
Imported from zangxin75/openclaw-skills (git-sync/SKILL.md). Install upstream with npx skills add zangxin75/openclaw-skills --skill git-sync. Copyright stays with the author.
Git Sync Skill
Automatically syncs local workspace changes to the remote GitHub repository.
Designed to be called by PCEC cycles or after significant changes.
Tools
git_sync
Commit and push changes.
message (optional): Commit message. Defaults to "Auto-sync: Routine evolution update".
Safety
Uses .gitignore and pre-commit hooks (ADL-compliant) to prevent secret leakage.
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 git-sync 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.
