Omni Sync Cloud
Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Sync Cloud when an AI agent needs a reusable SKILL.md workflow for this job: Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.
When not to use it
Skip Omni Sync Cloud when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-sync-cloud # Save SKILL.md to ~/.claude/skills/omni-sync-cloud/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-sync-cloud/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-sync-cloud/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Sync Cloud skill for this task: Use Omni Sync Cloud when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.
## Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.
## Endpoints
### POST /api/cloud/auth
Authenticate with cloud worker
Authenticates with the OmniRoute cloud worker for remote access.
```bash curl -X POST http://localhost:20128/api/cloud/auth \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### PUT /api/cloud/credentials/update
Update cloud worker credentials
```bash curl -X PUT http://localhost:20128/api/cloud/credentials/update \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/cloud/model/resolve
Resolve model via cloud
Resolves a model request through the cloud worker.
```bash curl -X POST http://localhost:20128/api/cloud/model/resolve \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/cloud/models/alias
Get cloud model aliases
```bash curl http://localhost:20128/api/cloud/models/alias \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### PUT /api/cloud/models/alias
Update cloud model alias
```bash curl -X PUT http://localhost:20128/api/cloud/models/alias \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/sync/cloud
Sync with cloud
```bash curl -X POST http://localhost:20128/api/sync/cloud \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/sync/initialize
Initialize cloud sync
```bash curl -X POST http://localhost:20128/api/sync/initialize \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/sync/bundle
GET sync › bundle
```bash curl http://localhost:20128/api/sync/bundle \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/sync/tokens
GET sync › tokens
```bash curl http://localhost:20128/api/sync/tokens \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/sync/tokens
POST sync › tokens
```bash curl -X POST http://localhost:20128/api/sync/tokens \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### DELETE /api/sync/tokens/{id}
DELETE sync › tokens › <id>
```bash curl -X DELETE http://localhost:20128/api/sync/tokens/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
Intended uses
- Use Omni Sync Cloud when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.