Agent skill

OmniRoute Cloud Sync

by diegosouzapw in diegosouzapw/OmniRoute

Synchronizes OmniRoute settings and provider connections to or from cloud storage, and manages cloud worker credentials and remote backup targets.

MITAuto-check passedBackend & APIs

Install OmniRoute Cloud Sync

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omni-sync-cloud .claude/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .claude/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omni-sync-cloud .agents/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .agents/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omni-sync-cloud .cursor/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .cursor/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/diegosouzapw/OmniRoute.git --path skills/omni-sync-cloud

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omni-sync-cloud .gemini/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .gemini/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omni-sync-cloud .github/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .github/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install diegosouzapw/OmniRoute omni-sync-cloud --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omni-sync-cloud .opencode/skills/omni-sync-cloud && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omni-sync-cloud" agent skill from https://github.com/diegosouzapw/OmniRoute/tree/release%2Fv3.8.52/skills/omni-sync-cloud into .opencode/skills/omni-sync-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omni-sync-cloud", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omni-sync-cloud
GitHub stars: 74k
Token cost: ~789 tokens
SKILL.md length: 136 words
Files: 1
Skills in repo: 50
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Synchronizes OmniRoute settings and provider connections to or from cloud storage, and manages cloud worker credentials and remote backup targets.

Backing up an OmniRoute configuration to cloud storage
SKILL.md covers Overview, Authentication, Endpoints and Payloads
Calls curl; needs OMNIROUTE_TOKEN and REQUIRE_API_KEY
Restoring provider connections on a second machine

What it does

Endpoints for moving an OmniRoute setup between machines and a cloud worker. You can authenticate with the cloud worker, update its credentials, initialize sync, trigger a sync and fetch a sync bundle, and sync tokens can be listed and created.

The cloud worker can also resolve a model request on your behalf, and cloud model aliases can be read and updated. The description additionally mentions remote backup targets. Requests use a Bearer token or session cookie, and a full OpenAPI spec is available from the server.

When your agent uses it

Backing up an OmniRoute configuration to cloud storage
Restoring provider connections on a second machine
Rotating cloud worker credentials
Managing cloud model aliases

Example prompts

“Initialize cloud sync for my OmniRoute instance.”
“Sync my OmniRoute settings to the cloud worker.”
“Update the cloud worker credentials on this gateway.”

Requirements

A running OmniRoute instance
A Bearer token or session cookie

What it can do on your machine

Read from SKILL.md and the folder at commit 8ad6b1c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- OMNIROUTE_TOKEN
- REQUIRE_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OmniRoute Cloud Sync loads about 789 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 136 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~789

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from diegosouzapw/OmniRoute at commit 8ad6b1c, republished under its MIT licence (© diegosouzapw). 136 words, ~789 tokens.

Download SKILL.mdSave it as .claude/skills/omni-sync-cloud/SKILL.md (or your agent's skills folder).

name: omni-sync-cloud
description: Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.

<!-- 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 https://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 https://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 https://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 https://localhost:20128/api/cloud/models/alias \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/cloud/models/alias

Update cloud model alias

bash

curl -X PUT https://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 https://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 https://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 https://localhost:20128/api/sync/bundle \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/sync/tokens

GET sync › tokens

bash

curl https://localhost:20128/api/sync/tokens \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/sync/tokens

POST sync › tokens

bash

curl -X POST https://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 https://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.

Files

Just SKILL.md in skills/omni-sync-cloud of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit 8ad6b1c

Compare with similar skills

OmniRoute Cloud Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OmniRoute Cloud Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
OmniRoute Cloud Sync this skilldiegosouzapw/OmniRoute	74k	—	~789	Automated safety check: Pass	MIT	today
Atlassian Adminborghei/Claude-Skills	874	—	~1.4k	Automated safety check: Pass	MIT	today
Raindrop APIintellectronica/agent-skills	295	—	~4.2k	Automated safety check: Pass	CC0-1.0	5 mo ago
Order LifecycleJoelLewis/finance_skills	205	—	~7.7k	Automated safety check: Pass	MIT	2 mo ago
Better Auth Best Practiceslatitude-dev/latitude-llm	4.7k	7 repos	~1.6k	Automated safety check: Pass	MIT	yesterday
Tanstack Start Best PracticesDeckardGer/tanstack-agent-skills	222	—	~1k	Automated safety check: Pass	MIT	28 days ago

Similar skills

Atlassian Admin
borghei/Claude-Skills
Administer the Atlassian suite (Jira/Confluence): user provisioning, groups, SSO/SAML, permissions, security policies, marketplace apps, backups, and org-wide governance.
874 GitHub stars~1.4k tokensUpdated today
Backend & APIsAuto-check passed
Raindrop API
intellectronica/agent-skills
This skill provides comprehensive instructions for interacting with the Raindrop.io bookmarks service via its REST API using curl and jq.
295 GitHub stars~4.2k tokensUpdated 5 mo ago
Backend & APIsAuto-check passed
Order Lifecycle
JoelLewis/finance_skills
Guide the design and implementation of order lifecycle management in trading systems.
205 GitHub stars~7.7k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
4.7k GitHub starsUsed in 7 repos~1.6k tokens
Backend & APIsAuto-check passed
Tanstack Start Best Practices
DeckardGer/tanstack-agent-skills
TanStack Start best practices for full-stack React applications.
222 GitHub stars~1k tokensUpdated 28 days ago
Backend & APIsAuto-check passed
Cb Security Hardening
BlkLeg/CircuitBreaker
Enforces Circuit Breaker security hardening conventions across backend, frontend, Docker, and nginx.
201 GitHub stars~2.1k tokensUpdated yesterday
Backend & APIsAuto-check passed

Questions about OmniRoute Cloud Sync

What does OmniRoute Cloud Sync do?

Synchronizes OmniRoute settings and provider connections to or from cloud storage, and manages cloud worker credentials and remote backup targets. Endpoints for moving an OmniRoute setup between machines and a cloud worker. You can authenticate with the cloud worker, update its credentials, initialize sync, trigger a sync and fetch a sync bundle, and sync tokens can be listed and created.

When should I use OmniRoute Cloud Sync?

OmniRoute Cloud Sync fits situations like: backing up an OmniRoute configuration to cloud storage; restoring provider connections on a second machine; rotating cloud worker credentials; managing cloud model aliases.

How do I install OmniRoute Cloud Sync in Claude Code?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a claude-code`. Or copy the skill folder (skills/omni-sync-cloud in diegosouzapw/OmniRoute) into .claude/skills/omni-sync-cloud in your project. Claude Code loads it when a task matches its description.

How do I install OmniRoute Cloud Sync in Codex?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a codex`. Or copy the skill folder (skills/omni-sync-cloud in diegosouzapw/OmniRoute) into .agents/skills/omni-sync-cloud in your project. Codex loads it when a task matches its description.

Can I use OmniRoute Cloud Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/OmniRoute --skill omni-sync-cloud -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omni-sync-cloud, .gemini/skills/omni-sync-cloud, .github/skills/omni-sync-cloud and .opencode/skills/omni-sync-cloud in your project.

What does OmniRoute Cloud Sync need to run?

Going by SKILL.md and its folder, OmniRoute Cloud Sync needs the command-line tools its instructions call (curl) and credentials named OMNIROUTE_TOKEN and REQUIRE_API_KEY. Our summary lists: A running OmniRoute instance; A Bearer token or session cookie.

Does OmniRoute Cloud Sync access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is OmniRoute Cloud Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OmniRoute Cloud Sync use?

OmniRoute Cloud Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OmniRoute Cloud Sync use?

About 789 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OmniRoute Cloud Sync?

Skills that share tags, products or a category with OmniRoute Cloud Sync: Atlassian Admin (borghei/Claude-Skills, 874 stars), Raindrop API (intellectronica/agent-skills, 295 stars), Order Lifecycle (JoelLewis/finance_skills, 205 stars) and Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OmniRoute Cloud Sync?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 73,701 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 6, 2026.

Source: diegosouzapw/OmniRoute on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install OmniRoute Cloud Sync

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Overview

Authentication

Endpoints

POST /api/cloud/auth

PUT /api/cloud/credentials/update

POST /api/cloud/model/resolve

GET /api/cloud/models/alias

PUT /api/cloud/models/alias

POST /api/sync/cloud

POST /api/sync/initialize

GET /api/sync/bundle

GET /api/sync/tokens

POST /api/sync/tokens

DELETE /api/sync/tokens/{id}

Payloads

Files

Compare with similar skills

Similar skills

More from diegosouzapw/OmniRoute

Related

Questions about OmniRoute Cloud Sync